Support and General Use > Hardware

Sansa e250 USB doesn't connect even in recovery mode. (SOLVED: Bad Hardware)

<< < (2/3) > >>

Chronon:
Generally you want to work at the simplest level possible.  Since your recovery mode doesn't work properly, it seems that you should first try to load a fresh bootloader while in Manufacturing Mode. 

funman:

--- Quote from: lark1313 on March 10, 2010, 04:45:15 PM ---I can still boot into the original firmware, so that means the bootloader's OK (right?), but then I can't load any more music - so I'm stuck (and I'd rather be using RB anyway)

--- End quote ---

Right, bootloader's OK.

You still have the µSD slot to load music though?

Chronon:
This sudden loss of functionality in Rockbox, recovery mode and the original firmware makes me suspect some sort of hardware failure, actually.  You might be stuck with the OF and only accessing new music from uSD cards.

lark1313:

--- Quote from: Chronon on March 10, 2010, 05:41:59 PM ---This sudden loss of functionality in Rockbox, recovery mode and the original firmware makes me suspect some sort of hardware failure, actually.  You might be stuck with the OF and only accessing new music from uSD cards.

--- End quote ---
That was my initial suspicion as well. However, the USB hardware can connect as evidenced by the dmesg output. So unless there's different levels of hardware breakage (is that possible in this HW?) I was thinking that the hardware was OK - only the driver (or it's location) was messed up. (hmm-memory failure where USB driver is located?).
But that bulk write error (see e200tool output) didn't look warm and fuzzy.

Anyway, I do have the uSD for music loading (one of the several reasons for using RB to begin with), I'd just rather fix the problem than workaround it, if at all possible.

thanks,
Steve

Chronon:
Right. If e200tool can't connect to the device while in manufacturing mode then there's not too much hope for recovery, I think.

One thing to try: Open up the Sansa and make sure that the daughter board containing the internal memory is properly seated.  It's a long shot, but flaky connection could cause strange behavior (like write errors, for example).  Good luck.

Navigation

[0] Message Index

[#] Next page

[*] Previous page