Sansa E200 Bricked by Recovery Mode

[travisty]

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.

[Bagder]

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?

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.

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.

[travisty]

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?

[Bagder]

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.

[travisty]

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!

[tarant]

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?  

Sorry, but I haven't a better idea yet.  

[travisty]

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.

[Bagder]

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?

[travisty]

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.

[Bagder]

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

[travisty]

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.

[Brambo]

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

[fldash]

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?

[Bagder]

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.

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.

[fldash]

I finally got it detected in Windows:

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