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

[Rob2222]

OK, I'll getting the serials together. And as long as I'm following this thread I will keep this post updated.

Fuze units where you can flash what you want:

BH 0812 BKGK-4GB
BI  0901 BKHK-8GB (2 unit already)
BI  0903 BLAK-8GB
BI  0905 BLCK-8GB
BH 0906 BMTK-4GB
BI  0909 BMYK-8GB
BI  0912 BMTK-8GB
BI  1001 BMTK-8GB
BI  1003 BMTK-8GB
BH 1004 CABK-4GB
BI  1004 CAAK-8GB (2 units already)


Units that doesnt accept firmwares other then 02.03.31-OF and 02.03.33-OF:

BI  1004 CAHK-8GB (3 units with this number already)

The numbers look like the date code YYMM.
For the letters I dont really have an idea.

EDIT: Actual 04.June.2010

BR Robert

[Jennifur]

OK, I'll getting the serials together. And as long as I'm following this thread I will keep this post updated.

Fuze units where you can flash what you want:

BH 0812 BKGK-4GB
BI  0901 BKHK-8GB
BI  0905 BLCK-8GB
BH 0906 BMTK-4GB
BI  0909 BMYK-8GB
BI  0912 BMTK-8GB
BI  1004 CAAK-8GB


Units that doesnt accept firmwares other then 02.03.31-OF and 02.03.33-OF:

BI  1004 CAHK-8GB (2 units with this number already)

The numbers look like the date code YYMM.
For the letters I dont really have an idea.

BR Robert

First two letters of the code, e.g. BH and BI would seem like it indicates the capacity. BH for 4GB and BI for 8GB. As you said the middle four numbers look like a date code. The last four letters are what I'm stuck on. A part of me wants to say one or two letters indicate colour, but I can't be 100% sure.

[lazo]

Silver Fuze v2, serial: BI 0903 BLAK - 8GB
Successful Rockbox installation on OF 02.02.26 and 02.03.31

[Rob2222]

So, regarding the Fuzu wont accept RB-Flash:

So I have calles Sandisk about the "issue" and the nice women said that they are aware of it, the ready it already in the forums and im the second person that asks fot that. At the same sentence she says also, that she is sorry, but that this (issue) is made that people "dont make this" (... use alternative firmware?!) anymore.
She still tries to help and is trying to get a official announcement for that.

I think I wait for 2-3 days and then im returning my unit and trying to get another one.

BR Robert

[funman]

First two letters of the code, e.g. BH and BI would seem like it indicates the capacity. BH for 4GB and BI for 8GB. As you said the middle four numbers look like a date code. The last four letters are what I'm stuck on. A part of me wants to say one or two letters indicate colour, but I can't be 100% sure.

Last part could be an increasing number: my Fuzev1 4GB is

Code: [Select]

BH0707AXWK-4GB

So I have calles Sandisk about the "issue" and the nice women said that they are aware of it, the ready it already in the forums and im the second person that asks fot that. At the same sentence she says also, that she is sorry, but that this (issue) is made that people "dont make this" (... use alternative firmware?!) anymore.
She still tries to help and is trying to get a official announcement for that.

I am not sure why they care at all, perhaps they were returned several "defective" players with rockbox installed?

EDIT:

You can try this to see how the protection they added is effective:
Be sure you want to risk bricking your fuze by running modified code

• Open a working OF file in an hex editor and swap 2 characters
• The characters must be distant of a multiple of 4 bytes, because the checksum is calculated as a sum of 32bits numbers
• For example swap a character at position N and position N+4, the firmware will be different but the checksum will be the same
• At position 0x38090 (outside the firmware block, in the "drmndt_pers" library block) there is the string "http://go.microsoft.com/fwlink/?LinkId=28745", make that be ":ttph//go.microsoft.com/fwlink/?LinkId=28745" (h and : swapped)
• Try to patch that OF, see if it works (I don't know how to display this string, it must be related to WMA drm)
• At position 0x216d9 (inside firmware block), there is the string "Hiphop", make that "oiphHp", see if the OF can be patched

[skaos]

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

[nissin]

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

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]

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.

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]

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

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]

as far as I know the C+ is identical worldwide and the only region difference is selectable in software

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.

[HorizonGrey]

Just rockbox'd my fuze v2 serial BI0903BLAK-8GB, works great thanks everyone for the hard work. I have patiently waited for this to be completed and not disappointed!

[id]

Something weird just happened with my Fuze v2. I compiled a Rockbox from source ( Version: r26433-100531 ) and installed it.
Then I wanted to test USB charging mode so I pressed left button and pluged the USB.
Since I've done that everything is off and it's not responding to anything.
I tried holding power button for a whole minute, I tried plugging it in and out from USB. Nothing works and nothing shows up in dmesg.

Has anyone any idea what happened to my Fuze ?

[funman]

have a look at this post

[funman]

there could be a bug in USB detection but it's not clear what happens there (or if there is any bug at all)

btw, to prevent rebooting you have to press center button.

left button is the one to press when you power up with the power button and want to boot OF

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.

I created SansaAMSUnbrick.
If you find spelling errors or want to clarify the wording, feel free ^^

I had to copy the whole reserved part from another Fuzev1 to have the OF work on this one.

The bootloader r20603 came with it and it seems it's much faster than the v1 bootloader - perhaps something to come in the next days.

The Clipv1 works fine except I had removed the jack from it to make a longer jack cable.

I soldered the jack from another PCB but now I have a lot of noise in the phones.

Also the battery doesn't seem to charge (in the OF or rockbox).

When I boot rockbox and plug USB the voltage readout decreases to ~3.0V and rockbox battery debug says charger absent / discharging, although the charger icon is shown in the status bar.



bertrik tried to find the pins on c200v2 without luck so far and JDGordon will try on Clip+.

[lazy]

for some reason, my clip+ stopped charging via usb via rockbox at ~68%
using the build r26441 i think (whatever was on the site 3 days ago)

tired replugging, didnt do anything, booted back to original firmware to charge it now