SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2

Rockbox Development > New Ports

<< < (380/386) > >>

skaos:
Maybe the third letter is hardware version/revision? Maybe someone can open a "C" player to see if there's any differences?

nissin:

--- Quote from: Rob2222 on May 28, 2010, 12:22:17 PM ---Hello,

my brand new FuzeV2 doesnt want to flash a patched firmware, however the original fuze02.03.33 FW he flashes flawlessly.

I tried 02.03.33 from http://forums.sandisk.com/sansa/board/message?board.id=sansafuse&thread.id=38046
with mkamsboot.exe from http://forums.rockbox.org/index.php?topic=14064.msg167356#msg167356
and output was http://pastie.org/981998

I also tried 02.02.26 from http://daniel.haxx.se/sansa/amsfw.html
with mkamsboot.exe from http://download.rockbox.org/bootloader/sandisk-sansa/mkamsboot/win32/
outpus reported success, also.

Renamed output.bin to fuzpa.bin. After disconnecting mass-storage-usb the player doesnt start the flash process.
With original fuzpa.bin he starts flash process after disconnecting mass-storage-usb.

30 minutes ago I flashed my also new Clip+ with the same mkamsboot.exe without problems.

Any hints? I can upload the output.bin if wanted.

If I don't need to set up a own compile chain it would be very nice.

EDIT: Same problem by 2 user here: http://forums.sandisk.com/sansa/board/message?board.id=sansafuse&message.id=42952#M42952
You can only flash 03.31 and 03.33. Hmm...

EDIT2: It doesnt want to flash the original 2.1.17, 2.2.26, 2.2.28, too.
It only flashes The 2.3.31 and the 2.3.33.

Looks like it has an additional check.

BTW, here is a dirlist:
DatentrÃ¤ger in Laufwerk G: ist SANSA FUZE
Volumeseriennummer: 0CF5-6F32

Verzeichnis von G:\

01.01.1980 00:00 <DIR> MUSIC
01.01.1980 00:00 320 SYS_CONF.SYS
01.01.1980 00:00 <DIR> RECORD
01.01.1980 00:00 <DIR> AUDIBLE
01.01.1980 00:00 <DIR> PHOTO
01.01.1980 00:00 <DIR> VIDEO
01.01.1980 00:00 <DIR> PODCASTS
01.01.1980 00:00 <DIR> AUDIOBOOKS
01.01.1980 00:00 51.237 RES_INFO.SYS
01.01.1980 00:00 83 version.sdk
01.01.1980 00:00 7.800 VIDEO_BM.SYS
01.01.1980 00:00 114 DID.bin
01.01.1980 00:00 1.862.468 MTABLE.SYS
6 Datei(en), 1.922.022 Bytes
7 Verzeichnis(se), 7.675.346.944 Bytes frei

Any new file maybe?

BR and thanks in advance
Robert

--- End quote ---

From the Release Notes of 02.03.31
*Max volume level is lowered in Normal volume setting to comply with new European Union requirement

I guess this maybe the reason that Sandisk prevent units with newer OF flash to older firmware.
Not sure if this applies to all units or European units only.

Vague Rant:

--- Quote from: nissin on May 31, 2010, 10:00:33 AM ---I guess this maybe the reason that Sandisk prevent units with newer OF flash to older firmware.
Not sure if this applies to all units or European units only.

--- End quote ---

Don't have a Fuze to verify, but do have a Clip+ which is practically the same thing; as far as I know the C+ is identical worldwide and the only region difference is selectable in software: after updating, the Clip+ asks for your region and I believe this impacts the FM range but more importantly, whether the volume limit is enabled (this of course means that it's probably ideal to choose America, etc. regardless of your real locale).

If that's the reasoning for blocking off updates, it seems fairly silly since the volume limit is circumvented so easily.

csavery:

--- Quote from: Vague Rant on May 31, 2010, 10:31:33 AM ---If that's the reasoning for blocking off updates, it seems fairly silly since the volume limit is circumvented so easily.

--- End quote ---
Ya, I doubt this is the reason. It's more likely related to either liability or business deals. Perhaps they need to make sure that SlotRadio (which I have zero interest in) is not bypassed since they may have contracts that require all units sold can use it.

I think it's only a matter of time before this is worked out. We probably need to start thinking of new units as Fuze v3. Since the 02.3.33 OF works fine in older units it seems to imply a possible hardware ID or change that is detected and used for basis of behavior. I was able to downgrade on my unit without problem.

Also I still haven't heard whether users that cannot install RB have tried with different Region settings? I usually use "Rest of World" - which has no SlotRadio anyway. If the restriction is related to that then perhaps that is enough to allow upgrading.

funman:

--- Quote from: Vague Rant on May 31, 2010, 10:31:33 AM ---as far as I know the C+ is identical worldwide and the only region difference is selectable in software

--- End quote ---

there might different hardware revisions:
1 have 2 clipv1 which have "M300 VER1.5" on the PCB, and 2 fuzev1 which say "FUZE REV_1.2" and "FUZE REV_1.41"

I bricked my fuzev1 and fuzev2 today doing something stupid, but good news follow:

I could unbrick the fuzev2 (back to business), the fuzev1 (although the OF won't start), and an old clipv1 I had bricked one year+ ago (although the battery doesn't seem to charge).

I'll see if I can have the fuzev1 and clipv1 working fully and I'll update the wiki pages with what I did.

Basically it's the e200v2 method, except the pins to short are at a different location (always close to the bottom left corner of the NAND, on either side of the PCB).

I only had to unmount the front covers, no need to unscrew the PCB or unplug the screen, only the fuze button board.

Opening the devices is still required, so not a user-friendly unbrick method.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version