Rockbox Technical Forums

Third Party => Repairing and Upgrading Rockbox Capable Players => Topic started by: A_BIRDY on January 26, 2007, 12:39:40 AM

Title: Sansa E200 Bricked by Recovery Mode
Post by: A_BIRDY on January 26, 2007, 12:39:40 AM
When using recovery mode to roll back the crappy new firmware with the pp5022.mi4 file, I accidentally dragged a random .bin file into the 16mbFORMAT folder (or whatever it's called) and disconnected the player.
Now the Sansa will not return to Recovery mode at all. I suspect this was the obvious result of flashing the ROM with a random .bin, but maybe there is a way to get past the ridiculous amount of problems this has caused the player. There might be a way to connect with the player's flash ROM without going into any sort of mode at all, but I'm not sure if there is.

Any news from the Sansa dev about rewriting the ROM on a totally bricked unit?

Thanks for any help, and godspeed.

...I want my saaaaansa baaaack...

Actually, I think this is the wrong section for my post... I'ma go find out where to put my question... Sorry!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on January 26, 2007, 03:02:25 AM
The only known way to fix this, apart from sending it to Sandisk, is to build the e200tool (builds and runs on Linux only so far) and use the "manufacturing mode".

Although I don't think we have seen a single soul actually having pulled this through for real.

You can be the first!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: A_BIRDY on January 27, 2007, 12:09:43 AM
I feel so privileged, thanks for the quick reply. I think I have a copy of Ubuntu around here somewhere.
Again, sorry if this was the wrong forum, but I'm a total nub here.

Your message makes it seem a little difficult; what exactly does this process entail?
Would I have to know anything special about the device in order for the machine to recognize it or does Manufacturing Mode automatically assume the Sansa has no firmware of any sort and thus cannot "consciously" connect to the computer?

Basically, can I do it without t3h h4xx skeelz or not?

Thanks again! I appreciate your guys' work!

EDIT: Looked over the process for Manufacturer Mode, and I think that's what the player is stuck in at all times. If anybody has ever gotten into Manufacturer Mode, could you describe it to me? My player's screen does not ever light up and the wheel is lit constantly and immediately when on.  The player is actually recognized as "USB Device" on a Windows machine.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: dan_a on January 27, 2007, 05:01:32 AM
That sounds like manufacturing mode to me.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: A_BIRDY on January 27, 2007, 04:46:01 PM
Hooray! It's Manufacturing Mode! Whooo!

Wait, I just remembered that I bricked my sansa.
Oh, well.

Onward to the Ubuntu!

Thanks again!

Finally figured out I was in the right forum anyway. Whoo!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on January 27, 2007, 05:58:15 PM
Also note that Zefie in the c200 thread did recover his Sansa using the manufacturing mode and e200tool...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: A_BIRDY on January 28, 2007, 04:38:16 AM
Hey Badger, you said e200tool only builds on linux... If it's source code, then can't I use Cygwin or something to compile it?
Just checking... Mebbey I are stoopid.

I'm probably going to email zefie at some point since he was wondering about the differences between the c200 and the e200 (and maybe kinda because he knows how to unbrick a c200).

Cheers!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on January 28, 2007, 06:33:14 AM
Quote
you said e200tool only builds on linux... If it's source code, then can't I use Cygwin or something to compile it?

Why ask me, when you can just try it?

I only know of people failing to get e200tool working on cygwin though, not due to compiling but probably due to libusb and stuff not working in the same way or possibly due to other bugs or so. But feel free to prove me wrong.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: zivan56 on January 29, 2007, 12:21:49 AM
It does compile perfectly under cygwin.  You just need to install the libusb package.  I have tested it, and it does appear to work (don't want to try anything to brick my sansa though).
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Ab on January 30, 2007, 03:48:38 PM
for A_BIRDY
could you fix the sansa in the recovery mode?

how do I get e200tool to work with the sansa in the recovery mode?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: dan_a on January 30, 2007, 04:32:00 PM
how do I get e200tool to work with the sansa in the recovery mode?
If you can get to recovery mode, you don't need e200tool!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: A_BIRDY on January 30, 2007, 09:53:41 PM
Alright, here's how things stand:

VMware is running Debian (with X 'cuz I like KDE).

I've got E200Tool compiled and running.

When I connect the Sansa, it's recognized by VMware as "PortalPlayer USB Device."

When I try to run ./e200tool recover pribootloader.rom or BL_SD_boardSupportSD.rom,
E200Tool cannot find the device 0781:0720.

I'm probably screwed at this point because that might mean the sansa isn't in manufacturing mode at all.
Again, the player will not boot, will not enter recovery mode, never turns on the back light, and just keeps the scroll wheel lit. Turning it off takes ~15 seconds.

If I try to connect the player without holding any buttons, it won't be recognized. If I hold any button when it's off and then connect the cable, regardless of hold switch position,  the player is recognized as "Portal blah blah..."

I should send it to SanDisk at this point... What do you think?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on January 31, 2007, 02:59:21 AM
Congratulations, you have advanced to the final level of this game. The prebootloader USB mode, that exists before the Manufacturing mode. This probably happens due to a corrupted i2c rom.

Let me stress that nobody has been there before and that the following advice may work or may harm your device or whatever, we just don't know enough and of course you proceed on your own without any warranties.

I've uploaded e200tool 0.0.6 fresh from MrH, with an added ability to recognize the player while in this mode. Just redownload the source zip.

if e200tool does work and nothing else helps, you could try to fix the i2c rom by uploading the dump of MrH's i2c bootrom:

http://daniel.haxx.se/sansa/e200tool/i2c.bin

Good luck!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: hallgreng on February 01, 2007, 02:17:01 AM
Hi there,
long-time lurker, first time poster.

Anyway, I seem to have busted my sansa (e270) in the same way. I did the stupid thing and fsck.vfat'd both partitions and then unplugged it.

It wont go into recovery mode, isnt discovered by e200tool, fits the same symptoms as Birdy's sansa, and achieves the same results (sans the PortalPlayer message) when following what he has done in this thread.

I'm also happy to see if this will work, but the problem is that I am unable (compile-time errors) to build e200tool from source in linux (debian unstable and stable both tried) w/respective usblib-devs) and had to use the insufficient win32 port (0.0.4a).

If someone could provide a static binary of 0.0.6 or some assistance (through PMs or another thread to keep this one uncluttered) to get e200tool to build for me, I would be glad to be another guinea pig.

Thanks for the hard work!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 01, 2007, 04:24:22 AM
1. On my debian systems I can build the tool fine with "libusb-0.1-4" and "libusb-dev" installed. You may want the Makefile I wrote for it, provided here: http://daniel.haxx.se/sansa/e200tool/Makefile

2. I have a e200tool binary built for Debian unstable available here:
 http://daniel.haxx.se/sansa/e200tool/e200tool
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: hallgreng on February 01, 2007, 12:12:10 PM
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.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 01, 2007, 03:58:05 PM
Quote
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!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: bob on February 01, 2007, 04:09:12 PM
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
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 01, 2007, 04:30:52 PM
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.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: hallgreng on February 01, 2007, 11:23:19 PM
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.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 02, 2007, 03:00:51 AM
Quote
My sansa is back from the dead thanks to you and your e200tool app.

All the glory goes to MrH for this.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: A_BIRDY on February 04, 2007, 07:29:01 PM
@ 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!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: A_BIRDY on February 05, 2007, 02:33:50 AM
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...)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 05, 2007, 06:37:54 AM
Okay, brand new page with some basic e200tool instructions:

http://daniel.haxx.se/sansa/e200tool.html
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: afshin3k3 on February 06, 2007, 04:48:55 PM

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?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 06, 2007, 05:40:31 PM
Quote
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?

Quote
Did anyone fix his device with Manufacturing Mode?

Yes
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: afshin3k3 on February 07, 2007, 04:32:13 PM
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

Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 07, 2007, 04:36:52 PM
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?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: afshin3k3 on February 07, 2007, 06:20:55 PM
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.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 08, 2007, 04:37:29 AM
Quote
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'
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: afshin3k3 on February 09, 2007, 08:37:09 AM

would you mind telling me how I can find out that in windows XP?(USB vendor and device ID)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 09, 2007, 09:20:53 AM
I personally cannot as I have no idea.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bibo on February 16, 2007, 01:47:43 PM
I have same problem. How can i find device ID? Because player is in manufactory mod, but e200tool can´t find it. Pls help.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: saratoga on February 16, 2007, 02:02:56 PM
Theres a device id field in the device manager entry for each USB device in Windows.  You could try that, though I have no idea if its the correct number.

Failing that, I'd try google.  There must be USB wire sniffers and debuggers.  One of them could give you the ID.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: afshin3k3 on February 17, 2007, 02:09:36 PM
Hi there

At last I decided to use linux,& it worked (I tried it on both Suse 10 & Knoppix 4) . It could find the device in the "init" step, but I couldn't go furthur. I don't what should I do after , I supposed I had to use the "write"
command to write the BLSD....rom & PP5022.mi4 files , but I don't know the address  and file size. (I write the address  and file size of those files but it didn't wrok)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 17, 2007, 03:53:52 PM
I think you want the 'recover' command.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: afshin3k3 on February 17, 2007, 04:49:48 PM
I'm not sure wich command i have to use,
For using "recover" command I have to recover i2c.bin or BL_SD_boardSupportSD.rom or any other file?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 17, 2007, 05:38:01 PM
Quote
For using "recover" command I have to recover i2c.bin or BL_SD_boardSupportSD.rom or any other file?

Since you're using manufacturing mode, and the recover command implies it, you should use the bootloader. The .rom file.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: illa on February 21, 2007, 01:53:58 AM
hey party people..  I have a similar problem.

i formatted the 16mb partition in recovery mode then drag and dropped a bin file onto the drive letter, since then, when ever the device turns on, there is only a blue light circle and nothing on the screen.

following the advice is this forum, I got e200tools ruunning in fedora 5.  if i hold down the center button, connect via usb, I beleive I am in manufacturing mode.  Once in manufacturing mode, here is the output of my terminal window:

[root@smtp e200]# ./e200tool recover BL_SD_boardSupportSD.rom
e200tool v0.0.6-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (3460 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!
[root@smtp e200]#

does this appear correct?  after this if i unplug the usb cable, it resets and gives me an error saying device is key locked since hold is still on, if i remove hold black screen and blue light.  my other option is to hold down rec while linux is writing the file, and I reboot into recovery mode, once im there I see the 16gb partition, i tried copying various files here but none of them seem to work.

After this happens the only way I can get into recovery mode is to go into manufacturing mode, use e200tools, hold down record as it recovers then I can boot into it...

I tried using e200tools on 2 windows machines so I could use the sandisk updater, but only the os detects the device not the e200 app..

Im staring at this 16mb partition now.. any ideas?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 21, 2007, 04:06:21 AM
This is explained in:

http://www.rockbox.org/twiki/bin/view/Main/SansaE200TroubleShooting
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: illa on February 21, 2007, 08:59:21 PM
Thanks...

A word of caution  
Only copy .mi4 files to the recovery partition.
Do not format this 16MB drive
Do not copy anything except one .mi4 file to the recovery partition. This might turn your shiny toy into a paperweight!
Do not copy .rom files to that partition unless you know exactly what you are doing. Again: You might brick your player!
Do not try anything else unless you have to. Again: You might brick your player!

Wow... I'm 5 for 5
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: illa on February 21, 2007, 09:36:32 PM
one of the no no's I did was formatting the 16meg partition.  I did this on a Windows XP machine through Windows explorer...  Is it possible the reason the firmware wont reload correctly in recovery mode is because my partitions are ruined?

I have a e260...
hmm...

[root@smtp e200]# dmesg | grep "Sansa"
  Vendor: SanDisk   Model: Sansa e250        Rev:

-then my partitons
[root@smtp e200]# fdisk /dev/sdb

Command (m for help): p

Disk /dev/sdb: 16 MB, 16777728 bytes
1 heads, 33 sectors/track, 993 cylinders
Units = cylinders of 33 * 512 = 16896 bytes

This doesn't look like a partition table
Probably you selected the wrong device.

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   ?    23579877    58171077   570754815+  72  Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(357, 116, 40) logical=(23579876, 0, 1)
Partition 1 has different physical/logical endings:
     phys=(357, 32, 45) logical=(58171076, 0, 31)
Partition 1 does not end on cylinder boundary.
/dev/sdb2   ?     5111804    63779327   968014120   65  Novell Netware 386
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(288, 115, 43) logical=(5111803, 0, 24)
Partition 2 has different physical/logical endings:
     phys=(367, 114, 50) logical=(63779326, 0, 4)
Partition 2 does not end on cylinder boundary.
/dev/sdb3   ?    56663075   115330596   968014096   79  Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
     phys=(366, 32, 33) logical=(56663074, 0, 24)
Partition 3 has different physical/logical endings:
     phys=(357, 32, 43) logical=(115330595, 0, 22)
Partition 3 does not end on cylinder boundary.
/dev/sdb4   ?           1   110218985  1818613248    d  Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
     phys=(372, 97, 50) logical=(0, 0, 1)
Partition 4 has different physical/logical endings:
     phys=(0, 10, 0) logical=(110218984, 0, 24)
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order


*****************

This looks dirty compared to what I see on http://daniel.haxx.se/sansa/e200.html
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on February 22, 2007, 03:29:13 AM
If putting back the original mi4 in recovery mode doesn't work, I suggest you go further down the hackery lane and invoke the manufacturing mode and go e200tool to restore the BL and hope that fixes your problem.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: illa on February 22, 2007, 03:48:52 AM
yah i've tried 20-30 times with etools recovery.. different roms, once etools copies it over, hold down rec and tried various mi4's, everytime i unplug usb cable...it says firmware upgrade finishes, restarts to a blackscreen
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Hawks-SOAD on March 02, 2007, 06:07:03 PM
can someone plz make a guide with all the steps to unbrick my sansa im dumb
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 05, 2007, 11:04:57 AM
Hi, may my English is not the best - I'm form Germany.

J have the same problem with my sansa like it is described here, just the blue wheel light.
Recovery mode also did not work. Windows just recognizes that there is something at the USB-Port....

I buyed the player on Ebay as "defect" and i hoped that I could reset it via the recovery mode.
The person I bought it from has only formated the normal space, not the 16mb recovery mode.

I just don't understand how to get the sansa-tool working.

So when I have installed linux, what have I to do next?
My Linux experience seems to be very small (i had Linux on an old computer once a time....)

May you can give me a manual for Idiots? (You have not to descripe that I have to press the power button  :P )

Thx,

Lue  ;)

Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 06, 2007, 08:03:59 AM
Hi, I read the topic again and again.

I gues I have to do it this way:

1)install Linux
2)Download the e200tool.zip
3)Plugin my player (may with center button pressed) and hope that Linux will recognize the player as "portable player..."
4)Start the e200tool (how?)
how I have to go on?

Thank you!

Lue

€dit:
Hi again. I tried this at several pc's with several linux'es.
At my pc Linux had any problem with my S-Ata drivers- no chance to get that thing booted.

At my fathers Laptop: i downloadet the .zip pluged the sansa in (with Hold mode on and centre button pressed) but nothing happened. Neither the program worker nor the Sansa was recognized in any way.

The Windows version also did not work - at least not at 3 PC's. Everytime it's the same.
Start the program and the Window is open just for a part of a sec. and closes it self....in addition to that the sansa just is recognized as "something at the USB Port"


Help me please!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 08, 2007, 04:27:50 PM
e200tool is a small app. If you run Linux, you need to build it first. You can download and use the windows version if you have libusb for windows installed first.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: avba0 on March 09, 2007, 02:23:09 AM
Hello and sorry for my English...

My player is also broken and i can't access the recovery mode, so I am trying to use e200tool to recover it, but I don't know exactly how to use it.
When I try to run the e200tool the output is:

avba0@avba0-desktop:~/e200$ sudo ./e200tool recover  BL_SD_boardSupportSD.rom
e200tool v0.0.6-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (3460 bytes) ... done!
BL_SD_boardSupportSD.rom: No such file or directory

I don't know which file to recover, and as much as I know, the last firmware upgrade before my sansa broke was with this file and another file (pp5022.mi4)

I use Linux since running it on Windows XP doesn't help at all - The tool doesn't recognize my player.
Please help!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 09, 2007, 05:06:43 AM
e200tool is a small app. If you run Linux, you need to build it first. You can download and use the windows version if you have libusb for windows installed first.


4th Edit:

ah ok...this makes the thing easier...And now i understand the "makefile" (for Linux)

I found the .inf creator and created my Drivers....
and the  Sansa is recognized......but the sansa tool does not work. When I open it, it closes itself! I tried this at 3 different PC's - everytime I open sansatool it closes itself...

Help!? & Thank you
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 09, 2007, 04:32:03 PM
avba0@avba0-desktop:~/e200$ sudo ./e200tool recover  BL_SD_boardSupportSD.rom
e200tool v0.0.6-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (3460 bytes) ... done!
BL_SD_boardSupportSD.rom: No such file or directory

And you really have a BL_SD_boardSupportSD.rom file there?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 09, 2007, 04:32:47 PM
I found the .inf creator and created my Drivers....
and the  Sansa is recognized......but the sansa tool does not work. When I open it, it closes itself! I tried this at 3 different PC's - everytime I open sansatool it closes itself...

I have absolutely no idea what you're talking about.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 10, 2007, 09:12:23 AM
I found the .inf creator and created my Drivers....
and the  Sansa is recognized......but the sansa tool does not work. When I open it, it closes itself! I tried this at 3 different PC's - everytime I open sansatool it closes itself...

I have absolutely no idea what you're talking about.

ok...

when I start the e200tool for Windows with a double klick the programm starts and then it closes itself. I can see the programm window just for a moment...

May you understand my problem now!?

Thanks

Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Febs on March 10, 2007, 09:30:11 AM
You probably need to run it from a command prompt.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 10, 2007, 10:24:00 AM
You probably need to run it from a command prompt.

The same result.......may there is a bug in the actual version?

thx,
Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: avba0 on March 10, 2007, 12:09:49 PM
And you really have a BL_SD_boardSupportSD.rom file there?
Yes, thats the file (I have also try some other names), and even if it is not exist, is there anything else that could help?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 10, 2007, 12:16:05 PM
You probably need to run it from a command prompt.

The same result.......may there is a bug in the actual version?

It still pops up a window that immediately disappears when you run e200tool from a command prompt? What else does it output?

And you have libusb installed as well?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 10, 2007, 12:16:55 PM
And you really have a BL_SD_boardSupportSD.rom file there?
Yes, thats the file (I have also try some other names), and even if it is not exist, is there anything else that could help?

Sure, invoke the same procedure but run e200tool with a debugger to figure out why you can't do this when many others have already successfully done it.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: avba0 on March 10, 2007, 12:44:24 PM
Sure, invoke the same procedure but run e200tool with a debugger to figure out why you can't do this when many others have already successfully done it.
I don't know programming and I really don't know how to use a debugger, specially when I use Linux.

Is there any chance to use "200tool write ..." to unbreak my Sansa?
If is it possible, then how do I use it; and if not, it seems that there is no escape from studying programming and how to debug... :'(
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 10, 2007, 04:04:36 PM
Is there any chance to use "200tool write ..." to unbreak my Sansa?

Yes, I would say it is very likely that e200tool can restore your Sansa. Are you really having that BL file in the same directory that you invoke e200tool in? If so, is there a right issue with it? Again, many others have run this exact command so it is a bit strange that it doesn't work for you. Heck, even using strace on the command would tell why it fails to open/load the BL file.

As a matter of fact, I've also just written this "unbrick" instructions page:

http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: avba0 on March 10, 2007, 04:39:36 PM
Maybe should I run this when I am logged-in as root?  
I already use "sudo", and I have UBUNTU installed on my computer - it doesn't allow me to log in as root...

PS:
"Do Not Email Daniel"
oops...

Edit:
Woohoo!!! ;D
I compiled e200tool again and tried to run it from another directory and everything now works fine - Once again I'm in recovery mode!
Thanks a lot for you and MrH.. And Daniel!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: avba0 on March 10, 2007, 05:49:25 PM
OK new problem:
When I turn on my Sansa the following message appear:
"Load main image failed
Switch to recovery mode"
The boot-loader is now working and i am able to access the recovery mode but when I try to upgrade my player it doesn't help.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 11, 2007, 05:24:19 AM
The boot-loader is now working and i am able to access the recovery mode but when I try to upgrade my player it doesn't help.

You continue to be so short of details it is impossible for us to help.

What exactly do you do when in recovery mode (what files do you put where and what do you call it/them)? What bootloader version did you restore your sansa with (I'm assuming you managed to do that with e200tool)?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: avba0 on March 11, 2007, 09:13:38 AM
You continue to be so short of details it is impossible for us to help.
Sorry...

The bootloader file I used to restore my player with e200tool named "BL_SD_boardSupportSD.rom" (the one with the lil-monsta welcome screen) and that is the file I have used to upgrade my sansa before it suddenly broke.
I copied that file to my computer after e200-hebrew-01.03.01.exe finished downloading it (or exrtacting it, I'm not sure),
and that is the file I copied to the recovery drive when I finally was able to access the recovery mode.

Now I try to use "PP5022.mi4"  in the recovery mode, and after the upgrade is completed and the player restarts that error message appear.

Another thing is, when I use sansa autoupdater to download the original firmware (PP5022.mi4) It says the no update is available at this time.
Do you know where can I find the original boot-loader and the original firmware (1.2.15A I think)?

Edit:
I found the firmware on your website, and now the player is working perfectly.
Thanks for all the help.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 11, 2007, 10:28:22 AM
You probably need to run it from a command prompt.

The same result.......may there is a bug in the actual version?

It still pops up a window that immediately disappears when you run e200tool from a command prompt? What else does it output?

And you have libusb installed as well?

Jes Libusb is installed....
it doesn't output anything it yust closes...if i start it from command prompt or directly -> same result.....

I don't know what I'm doing wrong - I tried it at 3 several computers...

Lue

€dit: After many tries I catched an Screenshot from the programm....
Here it is (http://img379.imageshack.us/img379/6960/e200dh7.th.jpg) (http://img379.imageshack.us/my.php?image=e200dh7.jpg)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: avba0 on March 11, 2007, 06:33:38 PM
I also have 3 computers with WinXP installations in Hebrew and English, and in all of them the e200tool doesn't recognize my sansa (I didn't forget to install libusb).

I think it would be much easier to use the tool from Linux (even from a live cd - the same way I successfuly did) than trying to figure out why it doesn't work on windows XP - it's not that difficult!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 12, 2007, 07:16:51 AM
okay I'll try it under Linux.

But how I have to build the sansa tool there?
May you can give me a short manual?

Thank you,

Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: avba0 on March 12, 2007, 12:19:40 PM
I think that actually you don't have to complie it, you can simply download it from here:
http://daniel.haxx.se/sansa/e200tool/e200tool, and run it (I have tried it, and it works fine under knoppix and ubuntu).
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: zivan56 on March 12, 2007, 02:43:45 PM
If you are using the Windows build, make sure you follow the exact steps to set up libusb-win32:
http://libusb-win32.sourceforge.net/#installation
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: avba0 on March 12, 2007, 04:51:50 PM
I followed all the steps; Corrently I have the filter and the device drivers installed, the test program successfuly recognize my sansa and I can see the details of my player in the test program:
Code: [Select]
bus/device  idVendor/idProduct
bus-0/\\.\libusb0-0001--0x0781-0x0720     0781/0720
- Manufacturer : SanDisk
- Product      : Tango Digital Media Platform
  wTotalLength:         32
  bNumInterfaces:       1
...
...
...

However, when I try to use the tool, it cannot find the device:
Code: [Select]
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!

My player is now fixed (thanks to MrH and Daniel), but I don't want to be depended on linux in the future...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: travisty on March 14, 2007, 12:22:55 AM
Hello,

I fear that I also may bee in deep trouble. I was able to load Rockbox onto my e270 and it was working except for the USB so I decided to flash back to the original firmware. I place a bad file in the recovery mode (hold + record) and now I have a dark screen with the glowing blue ring.

lsusb:
Bus 003 Device 009: ID 0b70:0003 PortalPlayer, Inc.

./e200tool recover BC_SD_boardSupportSD.rom

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 ... found!
Failed to claim the interface (-1, Operation not permitted)

Can someone please help me restore my player. I leave on vacation in 8 days and really need to get this fixed. Thank you.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: dan_a on March 14, 2007, 04:18:13 AM
Try running e200tool as root.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 14, 2007, 05:10:41 AM
Notice how it detected the unit in PP mode, which means you need to do the i2c rom fix
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: travisty on March 14, 2007, 03:02:17 PM
I was able to run the program with sudo but nothing happened.

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 ... found!
Initializing USB stub (3460 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!

How do I upload the i2c rom if I can't access the recovery partition?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 14, 2007, 06:31:42 PM
Quote
How do I upload the i2c rom if I can't access the recovery partition?
http://daniel.haxx.se/sansa/e200tool.html
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: travisty on March 14, 2007, 06:58:16 PM
I ran the script in recovery mode and it looks like it wrote to the device.

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 ... found!
Initializing USB stub (3460 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 at this point I have no idea what to do. The directions say to copy a file to the recovery 'disk'. I don't see that I have to option to copy a file anywhere.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 14, 2007, 07:12:36 PM
Quote
I ran the script in recovery mode

Recovery mode, really?

That implies a working BL so why work so hard to write it if it works?

Quote
The directions say to copy a file to the recovery 'disk'.

What instructions say you "copy a file to the recovery disk" ? I bet it mentions the original mi4 if so. And if you are in recovery mode, you can copy it there.

Quote
I don't see that I have to option to copy a file anywhere.

Recovery mode allows you to mount the sansa and shows a 16MB disk. That's where you can copy the mi4 file to.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: travisty on March 14, 2007, 07:22:09 PM
OK, I'm starting to understand the modes better. I guess I wasn't in recovery mode. I don't have access to  the recovery mode then. It doesn't matter what button combination I press when I plug the player in. I get the same black screen and glowing blue dial.

Even after my last post I'm still getting this on 'lsusb'

Bus 002 Device 011: ID 0b70:0003 PortalPlayer, Inc.

Is there any hope for my case?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 14, 2007, 07:48:23 PM
Quote
Bus 002 Device 011: ID 0b70:0003 PortalPlayer, Inc.

Is there any hope for my case?

Yes, try the i2c rom recovery process, which I mentioned before and I linked to the page describing how its done.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: travisty on March 14, 2007, 09:12:14 PM
I ran the script with the hold key on and I held down the record key when I plugged in the usb. The Script wrote to the device as before but nothing happens after that. This where I'm confused. What should happen next?

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 (3460 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!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: tarant on March 15, 2007, 11:21:42 AM
My problem is completely different: I have installed rockbox on my player and i tried to restore the player with its old firmware.

I can go in recovery mode. But every firmware I load then (also the 1.02.15E what was before) don't work properly. It always crashes (the display freezes and the player reboots) when I choose the usb mode or when I try to play a track etc. Some times (some firmwares) the player is able to connect via MTP mode to the computer.

What can I do that the player works like before. Shall I flush the flash with a random.bin file to go to the manufactoring mode?  ;D

Sorry, but I haven't a better idea yet.  :'(
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: travisty on March 15, 2007, 11:25:47 PM
I did some more investigation work.

Before I run the script I see the device as this via 'lsusb'
Bus 002 Device 006: ID 0b70:0003 PortalPlayer, Inc.

'lsusb' gives the following after the script:
Bus 005 Device 008: ID 6666:e200 Prototype product Vendor ID

There is also a change in the device when I run cat /proc/bus/usb/device

Before script:
Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 11 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=0b70 ProdID=0003 Rev= 0.00
S: Manufacturer=PortalPlayer
S: Product=Tango Digital Media Platform
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 32mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

After script:
T: Bus=05 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 8 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=6666 ProdID=e200 Rev= 0.01
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)

I feel I'm making progress but that could be an illusion. There is still no mounting of the 16mb partition.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 16, 2007, 04:21:59 AM
I feel I'm making progress but that could be an illusion. There is still no mounting of the 16mb partition.

I've still not seen you try the i2c bootrom recovery, did I miss that?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: travisty on March 16, 2007, 12:10:08 PM
I followed the directions on this page.

http://daniel.haxx.se/sansa/e200.html#usbmodes

but my device doesn't show up as anything usefull in dmesg.

[17185705.428000] usb 2-2: new full speed USB device using uhci_hcd and address 29
[17185705.596000] usb 2-2: configuration #1 chosen from 1 choice

So I do not know how I can do the i2c recovery if I can't mount the device.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 16, 2007, 04:55:34 PM
I can see how this thread will never end.

The I2C rom recovery procedure howto is described on this page:

http://daniel.haxx.se/sansa/e200tool.html
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: travisty on March 16, 2007, 06:32:28 PM
I don't mean to drag this out. I assume you are referring to these instructions.
__________________________
 Restoring I2C boot rom on Sansa e200

Since the i2c.bin file is supposed to be written to the i2c ROM and e200tool does not have any i2c support (at least not yet), the proper procedure is

1. Get to the recovery mode

e200tool recover BL_SD_boardSupportSD.rom (hold 'rec')

If you succeed,

2. Copy i2c.bin to the recovery 'disk'

3. Disconnect the player and hope the recovery mode writes the .bin to the i2c rom.

I don't know if it will, but I think it might. If it won't, renaming it to sdbootrom.bin might help.

The i2c.bin is just dumped from MrH's e260. We have no idea if there are different versions of it etc. It may or may not work for others.

SO IT SHOULD BE OBVIOUS THAT WHILE DOING THIS MAY (WITH SOME LUCK) FIX THE I2C ROM, IT MIGHT VERY WELL BRICK THE PLAYER EVEN FURTHER! DO NOT TRY THIS UNLESS NOTHING ELSE WORKS!

If you succeed, the i2c ROM should not be corrected and you should now be able to boot to either 'manufacturing mode', 'recovery mode' or to the actual firmware.
___________________

I think that I fall in to the if you succeed category because I can't follow those steps. There is no mounted portion. I also been on the anythingbutipod forums and they claim I need the I2c support that doesn't exist at this point.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on March 17, 2007, 10:20:56 AM
Hello people,

I've got a big problem  :'(
just like others mentioned before, my sansa e270 doesn't boot anymore, only black screen and the wheel is lit all the time.

I've read everything about how to solve the problem, but I can't manage it to work. This is what I've done:

1. connect the sansa to the computer. The computer only detects the player only when I connect the player WITHOUT the battery... but I'm not sure if that is 100% true...
2. installed the libusb filter driver
3. installed libusb device driver and created a .inf file with the information I got from the testlibusb-win.exe:

bus/device  idVendor/idProduct
bus-0/\\.\libusb0-0001--0x0b70-0x0003     0B70/0003
- Manufacturer : PortalPlayer
- Product      : Tango Digital Media Platform

4. in device manager I updated the driver for my sansa with the just created .inf. The sansa is now listed in device manager as 'Tango Digital Media Platform'.
5 opened cmd.exe and entered "\e200tool init"
then I get:
 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!

6. I also tried linux (kubuntu) but I have 0% linux knowledge so I can't figure out how to try e200tool on linux...

7. What do I do wrong? If you suggest me to try on kubuntu, please give a detailed how-to because I don't know how to load the e200tool program in kubuntu...

I really apreciate all the help!

greets,

Bram
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fldash on March 17, 2007, 11:04:58 AM
Woops, count me as one of the ones having a problem!  I bricked mine somehow; I'm not even sure what model it is.

Taking out the battery revels its a c200, though I thought it was a 250.  Who knows?

I'm running Vista, and a USB Mouse.  I installed the libUSB program but when I do, it disable my USB mouse, and then I can't click refresh on the test application to get any information from it.  It doesn't have any shortcut keys assigned in it and tab doesn't move to the buttons so I can refresh!

It's detected each time as Tango Digital Media Platform in Vista.

I've tried both recovery and manufacturer mode, but it's always detected the same way.  e200tool never detects it either.

Any advice?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 17, 2007, 11:25:04 AM
It's detected each time as Tango Digital Media Platform in Vista.

That's a PPI name so I guess it is then in portal player pre-boot mode.

Quote
I've tried both recovery and manufacturer mode, but it's always detected the same way.  e200tool never detects it either.

Any advice?

Run and use e200tool from Linux.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fldash on March 17, 2007, 11:27:04 AM
I finally got it detected in Windows:

Quote
bus/device  idVendor/idProduct
bus-0/\\.\libusb0-0001--0x0781-0x0720     0781/0720
- Manufacturer : SanDisk
- Product      : Tango Digital Media Platform
  wTotalLength:         32
  bNumInterfaces:       1
  bConfigurationValue:  1
  iConfiguration:       0
  bmAttributes:         e0h
  MaxPower:             16
    bInterfaceNumber:   0
    bAlternateSetting:  0
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         0
      bEndpointAddress: 81h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 01h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0

But it still isn't detecting detected by e200tool, so I guess my only choice is to try linux...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on March 17, 2007, 11:39:42 AM
Can someone please give me a simple description on HOW-TO run e200tool on linux? My pc just can't find my bricked sansa on windows... (see my post above)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 18, 2007, 05:50:02 AM
thanks to Avba0 who gave me this description:
"
Well, I'll tell you what exactly to do in order to compile the tool (using Ubunto linux)...

1)
Get ubuntu 6.10 from here:
http://www.ubuntu.com/pro...how&redirect=download

From your preferred mirror, download this file: "ubuntu-6.10-desktop-i386.iso"

2)
Burn the CD and Boot from it (choose Start or Install)

3)
Connect to the Internet - if you have a router then it shouldn't be a problem (System/Administration/Networking)

4)
Run the package manager from here: System/Administration/Synaptic Package Manager.
Mark the "build-essential"  package from the Development section (it might require installing several other packages) and the "libusb-dev" package (this is not a driver, the driver should be already installed) from the Libraries-Development section (libusb++-dev is not required), and then apply the changes.

5)
After the installation was finished, you can download the source files and the makefile and compile them using "gcc -o e200tool e200tool.c -lusb".
You should use "sudo" when you execute the compiled file from the terminal.
for example:
sudo ./e200tool recover xxxxx.rom

That is how it is being done under the Ubuntu distribution.
It's should be similar in the other distributions, especially on debian based systems."

I tried it with Xubuntu, but there's the only problem that I don't know how to change the directory for the "gcc -o e200tool e200tool.c -lusb". command.

Thanks, Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fldash on March 18, 2007, 12:00:58 PM
Thanks for that walkthrough, unfortunately, I can't get the Ubuntu Live CD to work on any of my computers.  One of them is because it has an Nvidia 8800 GTS, the other because the wireless network card, while detected, refuses to accept the connection.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fldash on March 18, 2007, 11:35:30 PM
Okay, got Ubuntu started, was able to run the recover, I tried both the c200 and e200 roms.  It acted like it was successful and the screen on my player came on and told me the update was complete and it was safe to disconnect.  After disconnecting however, my player still doesn't work...   Any ideas?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 19, 2007, 03:37:31 AM
1. use the .rom that is for your model

2. did you do the i2c bootrom recovery procedure?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 19, 2007, 07:18:40 AM
How I have to modify the command to build the e200tool with the files in the correct folder?

At what a kind of file i have to store the makefile?

Thank you!

Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fldash on March 19, 2007, 08:36:13 AM
1. use the .rom that is for your model

2. did you do the i2c bootrom recovery procedure?

Badger: When I removed my battery, it says I have a c200.  I tried that ROM file which is the pribootLoader.rom, however when using it, I never got the 16M disk after running the recover command.  I did get the 16M disk when using the other ROM, BL_SD_boardSupportSD.rom.

However, I think I was confused.  I didn't know I had to copy the .ROM file to the 16M disk along with the mi4 file.  I thougth using the recover command installed the firmware.

I will try again tonight.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 19, 2007, 08:44:58 AM
Badger: When I removed my battery, it says I have a c200.  I tried that ROM file which is the pribootLoader.rom, however when using it, I never got the 16M disk after running the recover command.  I did get the 16M disk when using the other ROM, BL_SD_boardSupportSD.rom.

However, I think I was confused.  I didn't know I had to copy the .ROM file to the 16M disk along with the mi4 file.  I thougth using the recover command installed the firmware.

I will try again tonight.

1. I'm not Badger

2. Don't try this. The instructions and the i2c rom dump is the for e200 model, and you would very much risk bricking your player if you try this on a c200.

3. Really, if the recover approach (with the c200 bootloader rom) doesn't heal your player, then  we have no known way to repair it. But then again, this forum thread is for and about Rockbox on E200 and you have neither.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on March 19, 2007, 04:12:06 PM
Thanks for all the reactions, I'm a bit further now!  :)

I did everything as told by Lue to do on Ubuntu, but I'm stuck at this point:

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 ... found!
Initializing USB stub (3460 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!

I tried connecting the sansa with every possible key combinations, but every time I'm stuck at this point...
After this line: "Writing 'BL_SD_boardSupportSD.rom' to address 0x10600000"
the device immediately disappears from 'Device Manager' ... very strange I think... it gets stranger now I see that this happens not always but sometimes...

Bagder, you already linked travisty (with the same problem) to the e200tool page, for the i2c recovery instructions... but I read there that the first thing to do is to get in recovery mode.. but how to get there? I think I only get into pre-boot mode....

Does someone know the solution or how to get further?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 20, 2007, 08:59:13 AM
could someone may help me by my problems as well?

Thank you!

Lue  ;)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: JdGordon on March 20, 2007, 08:59:59 AM
WOOT... OK I just brought my sansa back to life and because it was difficult I'll explain what I needed to do.

Firstyl, when it would start copying the .rom across it would fail very quickly after, So I edited e200tool.c line 59 to #define E200_TIMEOUT 100000.

After this you should be able to get into recovery mode. However.. recovery mode was useless for me.. no matter what I copied in nothing would get written.. 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.
You should be in the OF now. DONT TURN OFF or you will have to start again!
Go into settings > usb mode and enable MSP mode. then connect the usb cable...
(youll need linux for the next bit)..
download http://jdgordon.mine.nu:8080/jonno/e200/partitions.tar.gz (its 5mb, and i have a slow connection, so be patient).. tar -zxf should extract the 2 files from it...
then..
dd if= < one of the files from the above tar.gz> of=<20mb partition of the sansa>

unplug, reboot (if it hangs when usb disconnects reset it manually)..
If all goes well the rockbox bootloader should show up. Try going into the OF.. if it doesnt let you, you then need to go into recovery mode and put it on manually...

after all this, reinstall the rockbox bootloader, and dont do the idiotic thing you did to brick it!

good luck :)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 20, 2007, 11:41:38 AM
ok....after many tries i found out that this command seems to work when I wan't to build the e200tool:

gcc -o /home/knoppix/e200tool/e200tool.c -lusb

but! Than comes an error:

/usr/bin/ld: cannot find -lusb
collect2: ld returned 1 exit status


Libusb is already installed....I'm working with Knoppix!

What I have to do?

Help! Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: JdGordon on March 20, 2007, 03:47:02 PM
libsub-dev is needed... althought the knoppix i used had it installed already
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on March 20, 2007, 04:14:25 PM
Again I'm a bit further now...
If I got luck, I get this on my pc screen:

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 ... found!
Initializing USB stub (3460 bytes) ... done!
Writing 'BL_SD_boardSupportSD.rom' to address 0x10600000
Searching for device 6666:e200 ... 9 8 found!
Write at 0x1065feb8
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!

After this, nothing happens and I can't find any  16mb disk....
I both tried Ubuntu and Knoppix but both the same...
Nothing on my sansa screen and no 16mb rescue disk created (at least I can't find the disk)...

Any help on what to try next?
Many, many thanks in advance!

Bram
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: JdGordon on March 20, 2007, 09:13:01 PM
make sure hold is on and hold rec as soo as it starts saying exectuion started! untill you get into recovery mode
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on March 21, 2007, 11:22:22 AM
libsub-dev is needed... althought the knoppix i used had it installed already

And what I have to do? Synaptic says that Libusb-dev is installed!
Are you shure that the command I wrote is right?

Thanks,
Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on March 21, 2007, 04:08:20 PM
make sure hold is on and hold rec as soo as it starts saying exectuion started! untill you get into recovery mode

I tried this, but just nothing happens after ' execution started!' .... whatever I do, nothing happens....

btw, my sansa is already shown in the KInfoCenter as:

VendorID 0x6666
ProductID 0xe200
speed 480 Mbit/s

Does somebody have any clue on what to try next?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Mr. Vage on March 22, 2007, 05:15:40 PM
My e200 was also bricked in recovery mode. I've been looking for a solution to unbricking with no luck. All the instructions I have read say that i should hold down the select button while plugging in the cable, but Windows doesn't see the e200 if i do that. If I hold down the record button while plugging the cable in, then Windows sees that a device has been plugged in and brings up the Found New Hardware wizard. It shows up as an "Unknown USB Device."

When I run the e200tool, I get this:

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!

When I go into device manager, I can clearly see that the address of the e200 is 0b70:0003. I have the libUsb filters intalled. I can't figure out what could be wrong and I don't want to make the problem worse by trying random things.

Could someone please help me with this? Thanks.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 22, 2007, 05:19:06 PM
Quote
When I go into device manager, I can clearly see that the address of the e200 is 0b70:0003.

This indicates you're in the mode we call pre-boot (as those are the PortalPlayer vendor/model IDs) and you can try the i2c boot rom rescue operation.

Do note that very few poeple manage to use e200tool on windows (including skilled Rockbox dudes), so I would really suggest you try e200tool on Linux instead, and then even possibly with the time-out extension previously mentioned by jdgordon.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 22, 2007, 06:24:46 PM
and since it is such a grand day, MrH has just released an updated e200tool with integrated i2c restoring abilities...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on March 23, 2007, 09:48:39 AM
and since it is such a grand day, MrH has just released an updated e200tool with integrated i2c restoring abilities...

GREAT GREAT GREAT!!!!
This new e200tool update FIXED my US sansa e270!!!!!
THANKS Bagder and MrH!!!

For the people that still haven't fixed their sansa here how I did it:

1. boot up knoppix live cd
2. download & install libusb 0.1.12
3. download e200tool source + makefile
4. compile e200tool (gcc -o e200tool e200tool.c -lusb)
5. connect sansa with hold ON and pressed middle button
6. hold REC and command: sudo ./e200tool recover BL_SD_boardSupportSD.rom
7. the only thing to my sansa after the recover command is that its now seen as 6666:e200 instead of 0b70:0003 -> thats what we want! it has to be 6666:e200
8. when your sansa is seen by linux as 6666:e200, hold REC and use sudo ./e200tool i2cprogram i2c.bin
9. the program writes a lot to the sansa, when its ready, disconnect sansa and reboot it.
10. if sansa doesn't boot right, then you have to get into recovery mode: turn sansa off, turn ON hold and hold rec, then connect sansa to PC to get 16MB device. Copy .mi4 file to it and discoonect sansa
11. Sansa should be up and running again!

I still have one question left: on the e200tool-site are two i2c.bin files.... one for US 260 and one for US 280... I've got US 270.. does it matter that I used the US 280 i2c.bin file?

Thanks again!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Mr. Vage on March 23, 2007, 08:20:35 PM
Thank you for your reply Badger. I tried the tool in linux and am getting much better results. My output is now:

e200tool v0.1.4-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 (4272 bytes) ... done!
Writing 'BL_SD_boardSupportSD.rom' to address 0x10600000
Searching for device 6666:e200 ... 9 8 found!
Write at 0x1065feb8
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!

Where do I go from here? Rebooting the player still gives me the blue ring of death. Is there any thing else that needs to be done or am I completely f***ed? I already lost two iPods and I don't want to have to tell my parents that now I bricked my Sansa!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Mr. Vage on March 23, 2007, 08:47:25 PM
I forgot to mention that I have an e270. It seems that no one has dumped the i2c rom for the e270 yet. Badger said that I should reload the i2c rom, so could someone please dump it? I would really appreciate it. Thanks.

Update: I should have read the post right before mine. I'll try using the e280 i2c rom.

Update: Well, thats it. Complete death to my Sansa.  :'( Protocol error (-71) while writing the i2c rom. Oh well, I tried. Does anyone know how much SanDisk would charge for repair?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on March 24, 2007, 10:07:01 AM
Mr Vage, is your sansa not recognised anymore by linux?

I have a US e270 and used the i2c.bin dump of the US e280 and all went well....
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Mr. Vage on March 24, 2007, 01:35:49 PM
No, the device is no longer recognized. Something went wrong during the programming of the i2c rom. Each time i retried, the progress was less and less. It is completely dead.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on March 24, 2007, 04:26:24 PM
No, the device is no longer recognized. Something went wrong during the programming of the i2c rom. Each time i retried, the progress was less and less. It is completely dead.

That REALLY sucks man... but maybe there still is hope.. maybe Bagder or MrH has another genius way of fixing it...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on March 24, 2007, 04:37:12 PM
There's now a e200tool version 0.2.1 available, that does the "i2c program cycle" on the player itself. This version first uploads the desired i2c contents to the IRAM and then using single usb message orders the player to program it.

MrH said this about 0.2.1:

"I have run about ten flawless programming cycles with this version, so it should be relatively safe to use, but as usual, I cannot give any guarantees. If it breaks, the user gets to keep all the pieces."
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fLo on March 25, 2007, 03:30:23 PM
HI, i recently bricked my player too by dropping a bin file in recovery mode...THe player is a e270. Sometimes the player doesnt even turn on when i hold power, let alone be recognized when plugged into the computer. When i do get it to turn on, its a black screen and a blue wheel...i cant get into recovery mode. Help please..

ive read previous posts and im very confused..
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on March 25, 2007, 04:18:38 PM
HI, i recently bricked my player too by dropping a bin file in recovery mode...THe player is a e270. Sometimes the player doesnt even turn on when i hold power, let alone be recognized when plugged into the computer. When i do get it to turn on, its a black screen and a blue wheel...i cant get into recovery mode. Help please..

ive read previous posts and im very confused..

I would like to help (because I recently fixed my sansa with the help of the rockbox people!) but first tell what did you try already? Does linux recognise the player? How is the player recognised in linux? what does the e200tool say?

The sansa won't be allways recognised by linux, just try connecting&disconnecting it 5 times in a row and it will be recognised at least once I think...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fLo on March 25, 2007, 05:00:23 PM
hi! sorry, im really bad with computers,, what is linux??
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fLo on March 25, 2007, 05:16:39 PM
Oh,, I use windows not linux...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fLo on March 25, 2007, 05:24:07 PM
Is there any way to switch from windows to linux, Does it only work for linux?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: chrisjs169 on March 25, 2007, 05:55:35 PM
Well, since you probably don't want to partition your drive and install Linux, you can either:
a) Get a ~700 MB live cd, burn it to a disk, and restart your computer
b) Look here (http://daniel.haxx.se/sansa/e200tool.html)/here (http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick) for information on getting e200tool to work on Windows
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fLo on March 25, 2007, 06:19:10 PM
K i tried toe e200tool,, this is what happened:

Press ENTER to begin recovery of the file on drive C:

Cannot lock the drive.The volume is still in use

C:\e200tool>

Help...? what happened?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: saratoga on March 25, 2007, 06:28:39 PM
Is there any way to switch from windows to linux, Does it only work for linux?

As was said a couple posts above yours:

Quote from: Bagder
Do note that very few poeple manage to use e200tool on windows (including skilled Rockbox dudes), so I would really suggest you try e200tool on Linux instead, and then even possibly with the time-out extension previously mentioned by jdgordon.

So it sounds like you should not use it on Windows.  But more importantly, I think you should take a couple minutes to read this thread and get an idea what you need to do before you jump into this.  If you don't take care, you'll destroy whats left of your player.

Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fLo on March 25, 2007, 06:36:22 PM
i have read it it a couple of times and dont understand some of this,, im not very good with computers..
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: chrisjs169 on March 25, 2007, 06:38:47 PM
Quote
Press ENTER to begin recovery of the file on drive C:

I haven't tried e200tool yet, since I haven't dropped random files in the recovery partition, but doesn't that say it's recovering 'the' file on drive C:, your windows drive?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fLo on March 25, 2007, 06:42:30 PM
yes,, after i press enter it says:

Cannot lock the drive.The volume is still in use
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: chrisjs169 on March 25, 2007, 06:48:35 PM
Like I said, I'm not familiar with e200tool, but it sounds like it's trying to use your hard drive, C:\, vs your Sansa.  But like I said, I'm not entirely sure...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: saratoga on March 25, 2007, 06:52:41 PM
i have read it it a couple of times and dont understand some of this,, im not very good with computers..

Nows a good time to learn.

Also, its helpful that when you ask people to tell you what an error message means, you also post what you did.  In this case, you should probably copy and paste the log from running that command.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fLo on March 25, 2007, 07:30:35 PM
Quote

Press ENTER to begin recovery of the file on drive C:

Cannot lock the drive.The volume is still in use

C:\e200tool>
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: saratoga on March 25, 2007, 08:21:26 PM
Quote

Press ENTER to begin recovery of the file on drive C:

Cannot lock the drive.The volume is still in use

C:\e200tool>

Obviously I meant the complete log.  You already posted that above.  Its not too useful since we have no idea what you actually did.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fLo on March 25, 2007, 10:39:36 PM
http://www.imagehosting.com/show.php/385712_WTF.bmp.html
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: saratoga on March 25, 2007, 10:48:21 PM
http://www.imagehosting.com/show.php/385712_WTF.bmp.html

The recover command is a built into Windows, and operates on hard disks.  Its not related to the e200tool, which is why you were getting an error message no one had ever heard of.

You probably wanted to type:

e200tool (insert_your_options_here)



Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: fLo on March 25, 2007, 11:41:21 PM
I dont really understand what you're saying, sorry english isnt my native language..
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: JdGordon on March 26, 2007, 01:31:28 AM
you need to run " e200tool.exe recover BL_....."
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on March 26, 2007, 04:46:21 AM
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 8)

Where do you get stuck?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: chrisjs169 on March 27, 2007, 07:31:15 PM
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
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Rcholla32 on March 29, 2007, 07:49:55 PM
Wat is Manufaction mode plz write back because i messeed it up by recovey mode
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Rcholla32 on March 29, 2007, 07:53:45 PM
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
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on April 01, 2007, 11:46:05 AM
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
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on April 01, 2007, 05:33:29 PM
So I have to restore the i2c boot rom, or not?

It might very well be so.

Quote
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.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on April 02, 2007, 03:52:38 AM
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
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Brambo on April 06, 2007, 01:07:26 PM
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!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on April 10, 2007, 07:52:17 AM
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....
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: PepeZuniga on April 21, 2007, 08:15:52 PM
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!!! :'(
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: saratoga on April 21, 2007, 08:35:57 PM
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.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: PepeZuniga on April 22, 2007, 12:45:09 AM
Quote
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!

Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on April 22, 2007, 03:45:42 AM
Quote
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?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: PepeZuniga on April 22, 2007, 03:02:23 PM
Quote
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.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: chrisjs169 on April 22, 2007, 03:51:59 PM
Quote
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.


Manufacturing Mode (http://forums.rockbox.org/index.php?topic=8443.msg65826#msg65826) (more here (http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick))
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on April 22, 2007, 05:28:31 PM
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.

That's the PortalPlayer vendor ID which means you are in the "pre-boot" mode and you have a broken i2c rom.

Did you run the e200tool on a Linux system?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on April 24, 2007, 10:20:36 AM
Update

my sansa says


"
main image write failed
time taken="0"
"
when I unplug the sansa after putting the mi4 file in the recovery mode, doesn't matter what a mi4 file i put on it (I tried it with the European and the Am. mi4 file...)

What can I do?

Thanks,

Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: DoZer on April 24, 2007, 03:26:02 PM
Quote
aurora ~ # lsusb
Bus 002 Device 022: ID 0781:0720 SanDisk Corp.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
aurora ~ # ./e200tool recover i2c.bin
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'i2c.bin' to address 0x10600000
Searching for device 6666:e200 ... 9 8 found!
Write at 0x10602000
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!
aurora ~ # lsusb
Bus 002 Device 023: ID 6666:e200 Prototype product Vendor ID
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
aurora ~ # ./e200tool i2cprogram i2c.bin
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Programming i2c rom (address=87) range 0x0000-0x2000 from 'i2c.bin'
Searching for device 6666:e200 ... found!
Set ptr - error (-71, Protocol error)
DMESG after all:
Quote
usb 2-2: new full speed USB device using uhci_hcd and address 21
usb 2-2: new device strings: Mfr=0, Product=0, SerialNumber=0
usb 2-2: uevent
usb 2-2: configuration #1 chosen from 1 choice
usb 2-2: adding 2-2:1.0 (config #1, interface 0)
usb 2-2:1.0: uevent
usbserial_generic 2-2:1.0: usb_probe_interface
usbserial_generic 2-2:1.0: usb_probe_interface - got id
usbtest 2-2:1.0: usb_probe_interface
usbtest 2-2:1.0: usb_probe_interface - got id
drivers/usb/core/inode.c: creating file '021'
#sansa is now connected as 0781:0720
usb 2-2: e200tool timed out on ep0out len=0/0
#upper line after ./e200tool recover i2c.bin
usb 2-2: uhci_result_common: failed with status 440000
usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd e200tool rqt 64 rq 1 len 4 ret -71
usb 2-2: uhci_result_common: failed with status 440000
#upper lines after command: ./e200tool i2cprogram i2c.bin


And what now?

EDIT: working on gentoo @ root. my sansa is after format two partitions.

I can bouy NAND Flash 2GB for my sansa, is it a good idea? is there boot and recovery partition?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: PepeZuniga on April 24, 2007, 06:27:16 PM
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.

That's the PortalPlayer vendor ID which means you are in the "pre-boot" mode and you have a broken i2c rom.

Did you run the e200tool on a Linux system?

Nop, I tried on windows. I will do it on a linux system. Thanks. :D
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on April 25, 2007, 06:07:18 AM
after reading the thread again and again,

I recognized a member called "Illa" (page 2/3), having the same problem like me.

It seems that the previous owner formatted the 16mb recovery mode partition.

Is there any hope for my sansa or is it completely dead?

Thank you.

Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on April 28, 2007, 09:58:52 AM
Maybe there ist anybody alive in this forum?

Ok.
My problem is that it doesn't matter what I write on the recovery mode, it doesn't work.
(After writing the xxx.rom , for details look last posts..)

Fixing the i2c.bin file also does not work because my sansa is not recognized as 6666:e200

What can I do?

Help me please!

Thank you
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: chrisjs169 on April 28, 2007, 01:37:18 PM
Maybe there ist anybody alive in this forum?

Ok.
My problem is that it doesn't matter what I write on the recovery mode, it doesn't work.
(After writing the xxx.rom , for details look last posts..)

Fixing the i2c.bin file also does not work because my sansa is not recognized as 6666:e200

What can I do?

Help me please!

Thank you

I just put a corrupted BL on my sansa in recovery mode to see what'd happen.

Assuming you're using Linux, is the device ID 0781:0720?  If it is, grab a copy of the sansa BL (http://nuclearscripting.com/other/sansafw/BL_SD_BOARDSUPPORTSD.ROM) (check md5sum, below) and firmware (http://nuclearscripting.com/other/sansafw/PP5022.MI4) (check md5sum, below)

MD5sums:
6a10d79a2e13f6b4a7c8243f422e5608  BL_SD_BOARDSUPPORTSD.ROM
d9f946067844e2a24fcbb6cfedb75057  PP5022.MI4
CHECK BOTH MD5SUMS

Save both of them to either the directory where e200tool is, or to whereever.  Run
./e200tool recover BL_SD_BOARDSUPPORTSD.ROM
while holding REC on the sansa. Running that as root may be required.

When it's done, recovery mode should automatically start (provided you held REC)

Place both the BL and firmware on the recovery partition (from what I found, the BL is required, but someone else may want to confirm that).  Make sure you MD5 at least the BL on there, if not the MI4, to prevent having to redo all of this.

Unmount the sansa, wait for it to reboot, and hope it works.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: PepeZuniga on April 29, 2007, 12:53:42 PM
Hi again everybody. I've been experiencing some difficulties. I don't know if you remember the last time my pc only recognized something in the usb port. I tried to use e200tool on windows but it didn't work. So I tried using Knoppix but seem to be a lot for me :( I couldn't make e200tool work on linux, so can any help me to use linux?? Thanks.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on April 29, 2007, 01:20:27 PM
Hi again everybody. I've been experiencing some difficulties. I don't know if you remember the last time my pc only recognized something in the usb port. I tried to use e200tool on windows but it didn't work. So I tried using Knoppix but seem to be a lot for me :( I couldn't make e200tool work on linux, so can any help me to use linux?? Thanks.

Hey;
here's some help:
1. the libusb on Knoppix is another program, you ALSO must dowload libusb from the internet (version 0.1.12) install it by this commands:
one: sudo ./configure
two: sudo make
three: sudo make install

2.
After the installation was finished, you can download the e200 source files and compile them using "gcc -o e200tool e200tool.c -lusb".
You should use "sudo" when you execute the compiled file from the terminal.
for example:
sudo ./e200tool recover xxxxx.rom

to change the directory in Knoppix use cd /home/knoppix/Desktop/e200tool ....

I hope you understand...

Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: PepeZuniga on April 29, 2007, 11:28:16 PM
Hi again, this is me once more. I got this problem I used the e200tool and it seem to work properly but I cant do anything further. What I got is this:

Quote
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 8 found
Write at 0x10602000
Write done
Running from address 0x10600000
Searchinf for device 6666:e200 . . . found
Execution started

But thats it ... There are no new partition or new drive in the desktop. What can I do
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on April 30, 2007, 08:58:44 AM
Hi again, this is me once more. I got this problem I used the e200tool and it seem to work properly but I cant do anything further. What I got is this:

Quote
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 8 found
Write at 0x10602000
Write done
Running from address 0x10600000
Searchinf for device 6666:e200 . . . found
Execution started

But thats it ... There are no new partition or new drive in the desktop. What can I do

Look here:
http://forums.rockbox.org/index.php?topic=8443.msg72797#msg72797

->
Quote
So as soon as it starts copying the rom across disable the hold switch,

This is the way I access the recovery mode...

Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: DoZer on April 30, 2007, 05:08:18 PM
Quick unbrick sansa When e200tool works:
Rules:
1. Fu*k rec button.
2. download http://nuclearscripting.com/other/sansafw/BL_SD_BOARDSUPPORTSD.ROM and http://nuclearscripting.com/other/sansafw/PP5022.MI4
3. Turn off sansa.
4. Turn lock button on.
5. connect usb cable.
6. from root, type: ./e200tool recover BL_SD_BOARDSUPPORTSD.ROM
7. When you can see on the monitor screen text: "writing" put key lock button to off.
8. now you can mount your sansa recovery partition.
9. put there both BL_SD_BOARDSUPPORTSD.ROM and PP5022.MI4.
9. umount sansa partition.
10. disconnect usb cable, and wait until sansa restart.

I will write idiot-proof instruction soon.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: chrisjs169 on May 02, 2007, 09:42:49 PM
Quick unbrick sansa When e200tool works:
Rules:
1. Fu*k rec button.
2. download http://nuclearscripting.com/other/sansafw/BL_SD_BOARDSUPPORTSD.ROM and http://nuclearscripting.com/other/sansafw/PP5022.MI4
3. Turn off sansa.
4. Turn lock button on.
5. connect usb cable.
6. from root, type: ./e200tool recover BL_SD_BOARDSUPPORTSD.ROM
7. When you can see on the monitor screen text: "writing" put key lock button to off.
8. now you can mount your sansa recovery partition.
9. put there both BL_SD_BOARDSUPPORTSD.ROM and PP5022.MI4.
9. umount sansa partition.
10. disconnect usb cable, and wait until sansa restart.

I will write idiot-proof instruction soon.

Well, first off, I find it odd that you're using the links that I posted above, as well as basically rewriting what I wrote (http://forums.rockbox.org/index.php?topic=8443.msg77915#msg77915)

While I don't mind, please make sure you have people verify the downloads, as I don't really want to have someone email me saying that my downloads bricked their player farther.  That server has been somewhat unreliable the past few days, and I want to make sure the full download is completing.  In addition, why exactly did you link to my downloads?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: DoZer on May 03, 2007, 04:40:51 AM
I wrote my post after reading your's. And your post explain me how to makes sansa work, so I decided to write it in a few easy steps. Before reading your post I was recovering my sansa with i2c.bin, and I was convinced that is the way to make it work. Dont be afraid that someone could write to his sansa incompletly firmware. My sansa was after format, so I thing nothing can destroy sansa.

Now i'm writing How to make it step by step, from downloading livecd through flashing sansa, mounting recovery disk and so on...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: brovarian on May 06, 2007, 04:06:41 PM
I've red all topic & found out that there are several different ways of recovering ???, so know I ask you to write ONE the most correct way. I want heard the sound from my Sansa e270, but I can't do anything :'(. Please help me.
P.S. I've Windows XP installed. But if it will be VERY necessary I also can get access to Linux.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Llorean on May 07, 2007, 03:35:42 AM
There is no "most correct way." There are different ways depending on what you've messed up.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: DoZer on May 07, 2007, 05:06:06 PM
Always you can brick your sansa, and make it working from brick. You know what i mean?
Title: Bootloader write failed / Main image write failed
Post by: danymag on May 07, 2007, 10:16:42 PM
First of all a big thanks to you guys for providing this much information and help to everybody.
Now, my problem:

Model: sansa e270 europe (http://epaun.com/e200/1.jpg)
Dumb action : Formated drive & unplugged
Cry for help : Followed the tutorial several times. After dumping both .rom and .mi4 files on the new available partition, unplugged usb cable. When trying to power on, the same blue ring.

After trying this several times, with all bootloader versions (us & eu & c200, btw when using c200 the whole screen was blank) now when I try it I get an error message after unplugging the cable. Even checked the files on nuclearscripting. I checked the CRC most of the times and it seemd ok.

Debug info : screen capture of e200 tool at work (http://epaun.com/e200/2.jpg)
Right after e200tool prints Execution started, this shows up on my sansa : http://epaun.com/e200/3.jpg
Recovery mode starts just fine : http://epaun.com/e200/4.jpg
Hold rec + drop the .rom & .mi4 files
After that hit safely unplug : http://epaun.com/e200/5.jpg
After unplugging the error message appears : http://epaun.com/e200/6.jpg
Then, in shuts down and restarts with the blue ring.

Do you think this is salvageable ? If not I have a friend that's looking for a color screen for his electronics project, I am sure he would be happy with the one on my Sansa but I would rather not give him the satisfaction.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: DoZer on May 08, 2007, 01:18:34 PM
When you see at this screen http://epaun.com/e200/2.jpg "Writing xxxxx" try to turn off lock button.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: danymag on May 08, 2007, 02:22:21 PM
When you see at this screen http://epaun.com/e200/2.jpg "Writing xxxxx" try to turn off lock button.

Thanks for the suggestion DoZer but I was already doing that. Without that, the player complains that it is locked and shuts down. It's the same message I got when the player was working and the key was locked. Note that I did not get this key locked messages during my first attempts to "fix" the player.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: danymag on May 09, 2007, 06:51:20 AM
after reading the thread again and again,

I recognized a member called "Illa" (page 2/3), having the same problem like me.

It seems that the previous owner formatted the 16mb recovery mode partition.

Is there any hope for my sansa or is it completely dead?

Thank you.

Lue

Lue, did you manage to fix your brick after all ? Is it something we are doing wrong ?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on May 13, 2007, 02:52:21 PM
after reading the thread again and again,

I recognized a member called "Illa" (page 2/3), having the same problem like me.

It seems that the previous owner formatted the 16mb recovery mode partition.

Is there any hope for my sansa or is it completely dead?

Thank you.

Lue

Lue, did you manage to fix your brick after all ? Is it something we are doing wrong ?

Until now I didn't..

I hadn't time to try chrisjs169's trick....

Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: afshin3k3 on May 17, 2007, 06:06:51 PM
Hi
First of all I have to thank Bagder, Brambo for their posts. I have fixed my device a month ago. If you have read Brambo's post on page 8 you will find how to make your broken player work again.
Also there is a point when I wanted to rebuild my sansa from manufacturing mode using e200 tool some errors happened like

Programming failed (-71, Protocol error)
*DANGER*, player might not be bootable now! Please retry!

but don't worry your sansa will be bricked when you finish the process.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: afshin3k3 on May 17, 2007, 06:14:27 PM
The log of the console was like this:

INFERNO:~/Sansa 2/e200tool-src # 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 8 found!
Write at 0x106007e0
Control message (-71, Protocol error)
INFERNO:~/Sansa 2/e200tool-src # sudo ./e200tool i2cprogram i2c.bin
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Programming i2c rom (address=87) range 0x0000-0x2000 from 'i2c.bin'
Searching for device 6666:e200 ... found!
Uploading at 0x2000
Uploading done!
Programming, please wait...
Programming failed (-71, Protocol error)
*DANGER*, player might not be bootable now! Please retry!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: dani@rockbox on May 19, 2007, 03:07:37 PM
At first, i want to thank everybody how feets this forum with his experience.

Ok, my problem is, that i got every possible error message, but the last status i get is:
LUN0 locked
LUN0 unlocked
LUN0 locked
LUN0 unlocked
LUN0 locked
LUN0 unlocked
LUN0 locked
LUN0 unlocked
and so on 1000 times

During this i copy the mi4 file to the 16mb driver and remove it safe.
No reaction from the player stil i disconnect. Then he says "uptade refreshed" or so and then he restarts the system. Surprise: Nothing happens, still the blue ring glowes.

Does anybody has a final idea what i could do, else i will send it back on monday.

thanks

ps: sorry for my english, but it's not my first language  ;)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on May 28, 2007, 06:58:22 AM
i have the same problem, but if you look some pages previous, i have a way to access the Recovery Mode, but still there i can't manage it that the sansa writes the mi4 file....

Lue
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: chrisjs169 on May 30, 2007, 10:16:18 PM
@danymag / Lue (?) - what about the chance that the chip can't be written to, but can still be read?  From what I saw, you didn't try e200tool - see if the 'recover' command works (You can use the BL on my site above) and post/pm me the output.  

Quote
*DANGER*, player might not be bootable now! Please retry!
That's partially misleading - it will still turn on, but you may just get the blue ring of death, either from a corrupt I2C or corrupt BL.  

Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Lue on July 16, 2007, 11:17:55 AM
@chrisjs169 doesn't work! I don't know but it says upgrad finished, but then the blue ring still is glowing.

I have the same problem like dani...

[profanity deleted by moderator]
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: A_BIRDY on August 08, 2007, 08:33:09 PM
Holy bejeezums, you guys...

It's been a while ('bout six months?), but I finally got fed up after receiving a:

Programming failed (-71, Protocol error)
*DANGER*, player might not be bootable now! Please retry!

...in my terminal.

I sent the thing back to Sandisk and got a brand-spankin'-new Sansa in two weeks.
Now I'm using MSchneider's build and am very very happy with the results...
I'd like to thank anybody who replied in this thread, and even those who came looking for help, simply for perpetuating the goodness of open-sourcery. I hope everybody's learned a lot about what not to do, and also about what to do when you screw up anyway. As for my original Sansa, I think it's in a better place now.

Of course, that's not the end of this thread...
Good luck with your hardware, everybody!
Title: Re: Bootloader write failed / Main image write failed
Post by: Gravian on August 09, 2007, 01:20:11 AM
First of all a big thanks to you guys for providing this much information and help to everybody.
Now, my problem:

Model: sansa e270 europe (http://epaun.com/e200/1.jpg)
Dumb action : Formated drive & unplugged
Cry for help : Followed the tutorial several times. After dumping both .rom and .mi4 files on the new available partition, unplugged usb cable. When trying to power on, the same blue ring.

After trying this several times, with all bootloader versions (us & eu & c200, btw when using c200 the whole screen was blank) now when I try it I get an error message after unplugging the cable. Even checked the files on nuclearscripting. I checked the CRC most of the times and it seemd ok.

Debug info : screen capture of e200 tool at work (http://epaun.com/e200/2.jpg)
Right after e200tool prints Execution started, this shows up on my sansa : http://epaun.com/e200/3.jpg
Recovery mode starts just fine : http://epaun.com/e200/4.jpg
Hold rec + drop the .rom & .mi4 files
After that hit safely unplug : http://epaun.com/e200/5.jpg
After unplugging the error message appears : http://epaun.com/e200/6.jpg
Then, in shuts down and restarts with the blue ring.

Do you think this is salvageable ? If not I have a friend that's looking for a color screen for his electronics project, I am sure he would be happy with the one on my Sansa but I would rather not give him the satisfaction.

=================================

Ok, here we go:

After several months of shelving my Sansa e250 2gig (regular, not rhapsody) I had just about given up hope on fixing it, but since I had just installed SuSE out of geeky curiosity I decided I would try and give unbricking it another go with e200tool.

Now what had happened was the same as the user above, except a little different, my Sansa was hanging on startup and all the official fixes didn't work so I decided to take a chance and wipe the whole thing clean using OS X, since it can see the hidden partition. The idea was to wipe it clean and fresh install with e200tool and then install rockbox, but when I went to reinstall the files in recovery mode via e200tool they would not write, instead, the exact thing the above user described happened.

*Once in recovery mode via e200tool* Heres what I did, first I made an empty text file called Sansa.fmt, now as everyone should know that formats the player, (mind you it seems a little below the point with the current problem, but I figured since I tried EVERYTHING else) then I copied over the bootloader file and the main rom file like before, selected remove safely from the right click menu and unplugged it.

Now the text was a little different this time and it went by too fast to read, but this time it booted into the sansa screen w/o needing to be plugged into the computer useing e200tool to load the bootloader to RAM, which was a major improvement, but it hung, so I booted into manufacturing mode *and loaded up the recovery mode via e200tool* one more time and just made a file called Sansa.fmt, then selected remove safely and unplugged. After that it booted up just fine!

Now I'm not sure exactly what had happened but I'm GUESSING when you format it with a computer like that you format it in a foreign format that it can't write the files too. One last note, I think you still have to hold down the center button when you plug it in and you still have to hold record when you use e200tool, even if you are stuck in manufacturing mode by default. But either way, it's good practice.

Anyway, post if this helps at all or if you need clarification. I've been seeing this problem on several forums, so I figured that I should give my solution.

Time to install RockBox!

EDIT: Ok, there was a typo, or moreso I forgot to mention something. The changes are in between the *'s. I guess I kinda figured it was obvious what I was doing by what I quoted, but I guess not, sorry.
Title: Re: Bootloader write failed / Main image write failed
Post by: Bagder on August 09, 2007, 03:28:01 AM
so I booted into manufacturing mode one more time and just made a file called Sansa.fmt, then selected remove safely and unplugged. After that it booted up just fine!

This was a typo, right? I don't see how you can create a file like that in manufacture mode...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Gravian on August 09, 2007, 03:46:26 AM
Maybe I got the name of the mode wrong? It's the mode you get when turning it on with the center button down. When it booted up it gave me the blue ring and black screen by default and the flash drive wouldn't mount, like I said, I had to use e200tool to even get into recovery mode because I wiped the 16 meg partition clean. Once I did that it gave the the 16 meg partition and from there I made the file and copied over the firmware like I would any USB flash device. If you JUST make the reformat file when it reboots it gives you a plain white text on black formating message. Although, if it matters at all, I think I may have used 260 firmware instead of 250 as it doesn't recognize the USB in windows, it gives me an error that is cataloged here:

http://www.rockbox.org/twiki/bin/view/Main/SansaE200Port#Rockbox

Unless of coarse all e200 models experience this problem, but I have only found reports for the e260. Luckily music and files can still be loaded up with the original firmware so I'm not really concerned, the only problem will be explaining that you have to boot with |<< held down to load it up to the person I am gifting this to (I personally use an iPod nano 2nd gen, much better sound quality).

Is my case strange or something? I thought it was pretty standard.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on August 09, 2007, 05:04:06 AM
Ah yeah ok.

When you start it in manufacture mode you can load the bootloader to it with e200tool and when that bootloader starts it can go into recovery mode (and then you can put files on its recovery disk), so yeah it gets a little confusing in which mode you're really in then...

As long as it worked for you I'm fine! ;-)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: lokasenna on October 31, 2007, 05:26:12 PM
New idiot that bricked his Sansa  :'(

I put my Sansa into recovery mode so I could restore the original firmware but put in some random bin on accident. Now when I switch on the Sansa the circle lights up and no backlight. My computer doesn't alert me to any usb device being connected. I figure this is a hopeless case because if I can't detect it then they can't communicate. Does anyone have any suggestions for this massive idiot? Or is trying to get Sandisk to replace it my only option?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on October 31, 2007, 05:28:32 PM
lokasenna, use manufacture mode:

http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick#Manufacturing_Mode
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: lokasenna on October 31, 2007, 05:37:14 PM
Manufacture mode is where you hold select while powering it up right? There were a lot of posts so I might have confused myself somewhere. But if it is then I've tried going into manufacture mode but my computer still doesn't detect the Sansa. I used e200tool on linux just in case and the program doesn't detect my Sansa.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on October 31, 2007, 06:02:43 PM
Yes that's the mode (I updated the wiki page right now to include the instructions on how to boot into the mode).

So when you do this, what do you see on the sansa display?

Did you run the e200tool as root?

Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: lokasenna on October 31, 2007, 06:26:44 PM
The backlight doesn't light up no matter what I do and the wheel stays lit as well. Ran e200tool as root as well, lsusb doesn't detect anything which is why I'm guessing sending it to Sandisk is my only option.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: jc57 on October 31, 2007, 09:08:49 PM
When my Sansa e250 was at this point, it helped to be able to remove the back cover and take the battery out to insure a quick and complete reset before trying the manufacture mode.  I also had to try this on two computers and eventually a Ubuntu boot CD to get the computer to see the Sansa on the USB port (lsusb).  So, keep trying, you may get lucky. -- jc
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: aleec on November 09, 2007, 12:19:32 PM
Hi! Sorry for my English.
After i using e200tool it say

root@alex-desktop:/home/alex/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!
bl_sd_boardsupportsd.rom: No such file or directory

root@alex-desktop:/home/alex/e200tool# ./e200tool i2cprogram i2c.bin
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Programming i2c rom (address=87) range 0x0000-0x2000 from 'i2c.bin'
Searching for device 6666:e200 ... 9 8 7 6 5 4 3 2 1 0 not found!
root@alex-desktop:/home/alex/e200tool# lsusb
Bus 003 Device 001: ID 0000:0000  
Bus 004 Device 001: ID 0000:0000  
Bus 005 Device 001: ID 0000:0000  
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 006: ID 0b70:0003 PortalPlayer, Inc.
Bus 001 Device 001: ID 0000:0000  
Who can help me?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: scorche on November 09, 2007, 03:28:39 PM
When you ran "./e200tool recover bl_sd_boardsupportsd.rom", were you in the same directory that you saved bl_sd_boardsupportsd.rom in?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: aleec on November 10, 2007, 02:23:46 AM
Yes because md5sum get me check sum. and i can see it in file browser.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: ItzBACON on December 20, 2007, 07:49:40 PM
Hate to keep dragging out this thread, but I'm still having some issues.

When I first plug my player in under manufacturing mode, lsusb shows it as

Bus 001 Device 021: ID 0b70:0003 PortalPlayer, Inc.

If I attempt to run ./e200tool recover BD_SD_BOARDSUPPORT.rom at this point then it says:

ubuntu@ubuntu:~/Desktop$ ./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!
Failed to claim the interface (-1, Operation not permitted)

If I try and run the i2cprogram from here, it shows me this:

ubuntu@ubuntu:~/Desktop$ ./e200tool i2cprogram i2c.bin
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Programming i2c rom (address=87) range 0x0000-0x2000 from 'i2c.bin'
Searching for device 6666:e200 ... 9 8 7 6 5 4 3 2 1 0 not found!
ubuntu@ubuntu:~/Desktop$


I've gotten it to tell me the whole "Failed to claim the interface (-1, Operation not permitted) using the i2cprogram command too, just can't remember how I did it at the moment. Been messing with this thing for a while now, and I'm getting tired.

So is there something I'm missing here? Am I not doing something right? I've read this thread and a few others about a hundred times and I still can't seem to get my player to respond the way it's supposed to. Any help would be greatly appreciated.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: JdGordon on December 20, 2007, 08:08:14 PM
run the command as sudo
$ sudo ./e200tool recover BL_SD_BOARDSUPPORTSD.ROM
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: ItzBACON on December 20, 2007, 08:46:09 PM
Ok, ran it as sudo, got this:

ubuntu@ubuntu:~/Desktop$ 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 8 found!
Write at 0x10660198
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!
ubuntu@ubuntu:~/Desktop$

After it does that, I tried the i2cprogram again with the i2c-e280.bin file and got this:

ubuntu@ubuntu:~/Desktop$ ./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 ... found!
Failed to claim the interface (-1, Operation not permitted)
ubuntu@ubuntu:~/Desktop$

If I run it as sudo, I get:

ubuntu@ubuntu:~/Desktop$ sudo ./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 ... found!
Set ptr - error (-71, Protocol error)
ubuntu@ubuntu:~/Desktop$

What next?

Also, thanks in advance for your all the help.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: ItzBACON on December 20, 2007, 08:47:05 PM
Oh, reason I run the i2cprogram command after recover is because nothing happens. Still the same blank screen and blue wheel.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: JdGordon on December 20, 2007, 08:47:40 PM
what EXACTLY are you trying to do?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: ItzBACON on December 20, 2007, 09:42:21 PM
Trying to unbrick it.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: JdGordon on December 20, 2007, 09:53:46 PM
usually when someone makes a point to emphasize a word its important... the fact that the emphasised word was "exactly" I can understand that you may have been confused, so I'll try again...


what is the actual problem your having? saying its bricked isnt helpful.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: ItzBACON on December 21, 2007, 06:10:52 AM
I can't get it to go into recovery mode. When I run the recover command with the boardsupport.rom it still stays in manufacturing mode, or so I'm guessing. I'm ASSUMING that it's in pre-boot mode, but since I'm still new at this I could be wrong. But the fact that it's not showing up as 0781:0720 and only as a "PortalPlayer, Inc." on 0b70:0003 or as "Prototype product vendor ID" on 6666:e200 makes me assume that it's not working the way it should. I've tried loading the i2c on it but I just get the "Failed to claim the interface (-1, Operation not permitted)" error. I waited as long as possible to post about it hoping that I could figure it out, but I'm pretty much out of ideas.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: zajacattack on December 21, 2007, 11:41:57 AM
Yes, it is in pre-boot mode. You need to run "sudo ./e200tool init" (without quotes) and then run "sudo ./e200tool i2cprogram i2c-e280.bin" (without quotes) you cannot get into recovery mode without first repairing the i2c rom.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: ItzBACON on December 21, 2007, 05:27:17 PM
Awesome guys, got it working again. I guess I was just doing some steps out of sequence or something, but after I did what you said zajacattack, it was able to recognize it as a Sansa again or so lsusb said. After that it wasn't too difficult to get it back going. Again, thanks guys, I REALLY appreciate all your help and what all you guys have done to figure this stuff out.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: aLexx on December 22, 2007, 10:56:23 AM
I supposed I got a new serious Problem. I really missed it up when I deleted (sic) the partitions with fdisk! Now the e250 hängs as by everybody: nothing on the screen and only the circle is lighted up.
I am running ubuntu 64bit and compiled the e200tool by myself (I also tried the binary, but same result). I followed all the solutions in the thread until today but I always get the same mistake:
I try to connect in Manufactory Mode and lsusb give back:
Bus 002 Device 009: ID 0781:0720 SanDisk Corp.
When I do "./e200tool recover BL_SD_BOARDSUPPORTSD.ROM" I get
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 0x1060279f
Control message (-71, Protocol error)
and the lsusb give: Bus 005 Device 019: ID 6666:e200 Prototype product Vendor ID

I then tried: "./e200tool init" and I get: e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
But when I do: "./e200tool i2cprogram i2c.bin"
I get:e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Programming i2c rom (address=87) range 0x0000-0x2000 from 'i2c.bin'
Searching for device 6666:e200 ... found!
Uploading at 0x2000
Uploading done!
Programming, please wait...
Programming failed (-71, Protocol error)
*DANGER*, player might not be bootable now! Please retry!

Does anybody knows how to solve this Problem, or what does "Programming failed (-71, Protocol error)" means???
Thx in advance
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: aLexx on December 23, 2007, 02:30:49 PM
Thanks to ALL the people with their problems and suggestions!!!! After an unsleepy night and thinking of giving up... I got a light and succedded in unbrick my  SANSA-e250.
This is the REAL Bible to unbrick the SANSA: http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick
Thanks again to all, who contributed to it!

Only one thing was driving me crazy: I was trying the whole with ubuntu amd64 (no problem with the system), but I stop getting "Programming failed (-71, Protocol error)" only when under the BIOS switched the USB Ports to USB1.1!
With USB2.0 I never succeded in wrinting the whole BL_SD_BOARDSUPPORTSD.ROM, but as soon as I tried with USB1.1 I had no programming problems at all.
Another important thing for those who deleted the partions (like I did), you NEED to copy also sansa.fmt to the recovery partition thogether with the *.mi4 and the *.rom files.

Thanks again!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Eisbaer on March 02, 2008, 03:17:52 PM
I've a big problem since today:

My Sansa e260 won't start any more. The animated boot screen appears and disappears again, then the scroll wheel turns blue and the display stays black and nothing happens any more.

It is possible to get into the recovery mode, but there is no effect when plugging in the usb cable - my computer doesn't recognize any usb-device.

I also tried to unbrick my Sansa in the manufacturer mode in Ubuntu. Here is the terminal log:

----part 1-----
ubuntu@ubuntu:~$ 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 7 6 5 4 3 2 1 0 not found!
----part 2-----
ubuntu@ubuntu:~$ sudo ./e200tool i2cprogram i2c-e260.bin
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Programming i2c rom (address=87) range 0x0000-0x2000 from 'i2c-e260.bin'
Searching for device 6666:e200 ... 9 8 7 6 5 4 3 2 1 0 not found!
-----part 3-----
ubuntu@ubuntu:~$ sudo ./e200tool init
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
-------------------
Anyone has further ideas or can help me in any way?

Thanks in advance!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: zajacattack on March 02, 2008, 03:20:00 PM
A couple of things:
1) For part one, did you make sure you held record while that command executed? Have you tried doing it again?
2) As for the next parts, you have to run ./e200tool init BEFORE you run ./e200tool i2cprogram
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Eisbaer on March 02, 2008, 03:25:14 PM
A couple of things:
1) For part one, did you make sure you held record while that command executed? Have you tried doing it again?
2) As for the next parts, you have to run ./e200tool init BEFORE you run ./e200tool i2cprogram

1) yes I tried with and without pressing record- no difference (I tried several times)

2) when I use the init command first, ic2 doesn't find my Sansa anymore... :-(
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: zajacattack on March 02, 2008, 03:27:00 PM
Have you tried programming the i2c rom WITHOUT running ./e200tool recover BL_SD_boardSupportSD.rom first?

Do you have a different USB port and/or computer that you could try using?
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Eisbaer on March 03, 2008, 01:08:34 AM
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  :'(

Thanks for your efforts anyway!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: qtip on April 01, 2008, 03:35:24 PM
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 ??
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Abdullah85 on April 10, 2008, 07:31:08 AM
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
Quote
[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
Quote
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 :
Quote
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

Quote
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 :)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: gevaerts on April 10, 2008, 09:43:23 AM
You need root rights for e200tool, so use sudo (also for lsusb)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Abdullah85 on April 10, 2008, 05:56:38 PM
same problem I get this
Quote
[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
Quote
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
Quote
[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
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: zajacattack on April 10, 2008, 06:13:10 PM
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
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Abdullah85 on April 11, 2008, 05:53:13 AM
WOoOoOoOoW

I got it baaaaaaack thanks  ;D

I really want to kiss you right now  ;D


thanks again and again
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: cheesecake on May 04, 2008, 06:08:50 AM
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.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Epholl on June 24, 2008, 11:39:49 AM
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.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Mystious on July 03, 2008, 02:46:02 AM
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!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Epholl on August 25, 2008, 06:29:42 AM
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.

Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: gevaerts on August 25, 2008, 08:34:46 AM
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...
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: virtuoso015 on August 25, 2008, 08:50:15 AM
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 :)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on August 25, 2008, 10:48:08 AM
The unbrick wiki page explains how to get back, use the manufacture mode and e200tool.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: virtuoso015 on August 25, 2008, 10:56:41 AM
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 :)
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Bagder on August 26, 2008, 04:18:28 AM
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!
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: virtuoso015 on August 26, 2008, 09:35:34 AM
Sure thing!!!  I have attached the required package (e2tplus-dev), along with the patch for e200tool-src (e2tplus.patch). Please feel free to provide comments on the code or any other thing for that matter. Thanks.

I would like to point out these threads which seem to be having a similar problem too
http://www.anythingbutipod.com/forum/showthread.php?t=26569
http://www.anythingbutipod.com/forum/showthread.php?t=28688
http://www.anythingbutipod.com/forum/showthread.php?t=26866
http://www.anythingbutipod.com/forum/showthread.php?t=23729
http://www.anythingbutipod.com/forum/showthread.php?t=19454


P.S: rename*.bin to *.zip.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: Epholl on August 27, 2008, 12:08:31 PM
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...

I havent done anything different, than the unbricking tutorials say about the 16MB memory. Since getting the firmware in again did not help the player, the problem was elsewhere.

If you think I just jumped into the 16MB driwe and deleted everything I saw, then you are wrong.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: dfb on June 17, 2009, 03:58:15 AM
One more way to solve the blue ring of death: remove the cover from your Sansa and push down on the little rubber thing above the battery. The flash module might have come dislodged. See: http://forums.rockbox.org/index.php?topic=21908.msg151537#msg151537

I had the blue ring of death and tried to follow the procedures provided in this thread. Unfortunately, my player was never recognized by the three computers I tried it on. 'sudo lsusb' always came up empty and 'sleep 10 && dmesg |tail' never brought up any usb related items. Pushing on the little rubber thing fixed it.

btw: I'm posting this in case someone else, like me makes it into this thread with a similar issue.
Title: Re: Sansa E200 Bricked by Recovery Mode
Post by: dj_depp on December 18, 2010, 07:39:31 PM
[SOLVED]  :o

hi! I`m from Ukraine (RUS lang)

I HAD SAME SITUATION.     I sheet my self when i "bricked" or "killed" my Sansa e250 by putting i2c.bin in recovery mode ! --- do not do this!

GREAT NEWS!  i was able to HEAL my Sansa using WINDOWS! i used Windows7 (before this i read all infomation, all forums ect.)

1. U need e200tool for Windows
2. U need libusb (libusb.sys, libusb.dll, libusb_x64.sys, libusb_x64.dll)
3. U need 0781-0720.inf and 0666-E200.inf (it was in my e200tool folder)
4. U need your F**ked-up sansa without battery

What to do:
1. Connect your player to PC (it should be recognised as tango digital media platform)
2. manually install driver for player 0781-0720.inf  NOTICE: all files ( 0781-0720.inf and 0666-E200.inf libusb.sys, libusb.dll, libusb_x64.sys, libusb_x64.dll MUST be in one folder.  After that your device should became "Standart USB storge"
3. RUN e200tool (in mine case: Run-->cmd-->
Code: [Select]
cd c:\sansa\e200tool)
4. in cmd type:
Code: [Select]
e200tool recover BL_....rom5.
Code: [Select]
e200tool init (it should chane your device to "USB storage")
6.
Code: [Select]
e200tool i2cprogram i2c.binafter that your device should became alive and you will get access to recovery mode.
7. copy your .ROm and .MI4 files to 16MB drive and CONNECT BATTERY! and only after that remove cable.
_______________________________________________________
BE PATIENT , i`ve tryed this 7 hours! and i had a million ERRORS, timeout errors and ect. (tip: some times before to connect player to PC i pushed SELECT button - it shoul put player in manufacture mode)

IF you are dumbass i can halp U in Skype nickname: por1ng or icq: 338064738
---------------------------------------------------------
[solved]BUT NOW I HAVE NEW PROBLEM:
my player do not recognise internal memory (4GB). (only Micro-SD card)


Solution:
1. create .txt file and rename it to sansa.fmt
2. copy sansa.fmt to player in recovery mode
3. remove cable (it will format player in 3-4 minuts)
-------------------------------------------------------------------------------------


Post Merge: December 18, 2010, 07:54:37 PM
One more way to solve the blue ring of death: remove the cover from your Sansa and push down on the little rubber thing above the battery. The flash module might have come dislodged. See: http://forums.rockbox.org/index.php?topic=21908.msg151537#msg151537

I had the blue ring of death and tried to follow the procedures provided in this thread. Unfortunately, my player was never recognized by the three computers I tried it on. 'sudo lsusb' always came up empty and 'sleep 10 && dmesg |tail' never brought up any usb related items. Pushing on the little rubber thing fixed it.

btw: I'm posting this in case someone else, like me makes it into this thread with a similar issue.

THIS IS NOT A BUTTON! THIS IS A PEACE OF PLASTIC THAT COVERS MEMORY! Yuo just pluged your memory module on it`s place.

Post Merge: December 18, 2010, 07:56:57 PM
I would like to point out these threads which seem to be having a similar problem too
http://www.anythingbutipod.com/forum/showthread.php?t=26569
http://www.anythingbutipod.com/forum/showthread.php?t=28688
http://www.anythingbutipod.com/forum/showthread.php?t=26866
http://www.anythingbutipod.com/forum/showthread.php?t=23729
http://www.anythingbutipod.com/forum/showthread.php?t=19454
if you are registered there and have time U may copy my post to that forum. Hope it will help.