Sandisk Sansa e200 v2

[Llorean]

The whole point of Recovery Mode is that it's there if you've done something distinctly not safe and need to undo it. So no, there really wouldn't be a safe way of testing it. Even if there was, all it'd confirm is something like "well, there's a recovery mode as long as I don't damage the existing USB mode."

[fed]

I asked Sansa and this is what I got:

----------
There is no recovery mode on e280 v.2 player. We can use forced MSC mode instead (to format the device or to update firmware).

For that:

1. Turn off your player and disconnect from the computer.
2. Flip the hold switch located on the top of the player so the orange color marking is showing.
3. Hold down the rewind button (Rewind Key on your Control Wheel), while holding it, connect your player.
4. When your device is recognized by the PC - release the button.
-----------

I am now asking if this will work even if the firmware gets messed up.

[newflesh]

If there's only one partition, and the only "protection" of the firmware is the hidden files that show up in forced MSC... wouldn't that make it too easy to brick by someone formatting the player from their system? I'm not sure SanDisk would allow that possibility if there was no means of recovery. Not that I ask anyone to do it, but I'd risk a format to try my hypothesis if I had one.

I also noticed the announced Sansa Fuze players, and I'm guessing when someone pulls one apart it will turn out that it has the same guts as the e200 v2. Explains the change of hardware, which otherwise wouldn't have made much sense so soon before it's (supposedly) going out of production due to replacement.

[eXomaniac]

mhh i could try to delete the files and then reload a firmware to it...

i just got a new player so perhaps i could take it back ...in worst case

[jesterpb]

Hello all,

I noticed this on Sandisk's site today:

Sansa Connect Recovery Tool
http://www.sandisk.com/Retail/Default.aspx?CatID=1532

Would this work to recover the device if one of us tried to flash the v2?

[eXomaniac]

For me it sounds good.
Mh i will see if i have time to test this today...

What work is to be done if the reflashing / recovery works?
I mean what else must be done to get Rockbox on it ? Can we use anything from the v1 version ?

[zivan56]

Sansa Connect runs Linux and was not even made by Sandisk (or whoever makes players for Sandisk).
There is nothing that the v1 shares with the v2 in terms of the firmware, except for the basic low level architecture.

[fed]

When I asked Sansa :

If my firmware gets corrupted, I can re-update it using MCR mode?

The response was:

We would recommend using forced MSC mode.

[zajacattack]

Well, if someone is willing to upload an mi4 that won't work and then see if they can recover...

[zivan56]

The v2 does not even use mi4 files...and the format it does use requires a correct header for it to be accepted in the first place.

[Hillshum]

The v2 does not even use mi4 files...and the format it does use requires a correct header for it to be accepted in the first place.

and i don't think we can update the checksum in it yet

[zivan56]

Well there is documentation here:
http://daniel.haxx.se/sansa/v2.html
Perhaps someone could follow it and convert junk data into the proper format and upload it to the player to see what happens?  Someone has to do it eventually...

[dan_a]

It would be more prudent to change some strings in the original firmware, and recalculate the checksums on that.
At the moment, though, we don't know how to calculate the checksum at 0x14 in the header, nor do we know what the rules are for the 4 byte checksum at the end.
I've not been able to put a modified firmware onto my Clip yet.

[metalaso]

i have e280 v2 but exist msc mode and mtp mode because i update my sansa e280v2 and with have msc and mtp mode and autodetect.

[Hillshum]

This thread is almost dead. Use the general Sansa v2 thread:http://forums.rockbox.org/index.php?topic=14064.0