Sansa E200 Bricked by Recovery Mode

[avba0]

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!!!
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!

[avba0]

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.

[Bagder]

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)?

[avba0]

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.

[Lue]

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

[avba0]

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!

[Lue]

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

[avba0]

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).

[zivan56]

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

[avba0]

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...

[travisty]

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.

[dan_a]

Try running e200tool as root.

[Bagder]

Notice how it detected the unit in PP mode, which means you need to do the i2c rom fix

[travisty]

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?

[Bagder]

How do I upload the i2c rom if I can't access the recovery partition?

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