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

[Rob2222]

My Fuze2 had 02.03.31 on it as it came.
My patched firmware has the same CRC sum.
Already checked MD5 hash with someone in #rockbox, was even, too.

Did you first updated to 02.03.33-org and then to 02.03.33-patched?

BR Robert

[Jennifur]

My Fuze2 had 02.03.31 on it as it came.
My patched firmware has the same CRC sum.
Already checked MD5 hash with someone in #rockbox, was even, too.

Did you first updated to 02.03.33-org and then to 02.03.33-patched?

BR Robert

I did first flash from 02.03.33-org to the 02.03.33-patched. That worked fine for me. I used a svn version of mkamsboot and the boot loader that funman posted a few pages back. I can't remember whch svn version I had since the hard drive I had it on died. I can try re-flashing it with the stock OF and then flash it with the patched one when I get back today and see if that will work.

[Rob2222]

@Jennifur:
Can you post a CRC or a MD5 of your .33OF and your patched .33?
The test would be nice along with the MD5 sums.
If this works for you, then the difference is surely not in the .33OF and must be in the player.

@All
Can it be that they (my fuze2) checks 0x408="0x24" or 0x460="0x44" in the code area? At least its even in .31 and.33 (which player accepts) and its even in the older original-FW which may player doesnt accept. But its different from new to old.

BR Robert

[djphatic]

@djphatic:
The letter behind the firmware number changes regarding the region setting.
(A=America, F=Europe and P=Pacific (Rest of World)

So you have now 2 Fuze's there, one which accepts patched and older formwares than .31 and one version that only accepts .31 and .33 original, or?

Can you see any difference on these units? Any big difference in the serial number?
Maybe differences in the system files in the root folder?
Could you maybe compare that?
Where you got the working unit from? Was that a new purchase? Meaning a new unit.

BR Robert

Yes I have 2 fuzes at the moment. I have not tried older firmwares with the new one as I do not want to risk losing Rockbox on this player.

No physical differences between the 2 players and I did not notice any different files or folders on the root of the internal memory.

Non-friendly serial = BI1004CAHK-8GB
Rockbox friendly serial = BI1004CAAK-8GB

The first player was from a UK seller on ebay, brand new and sealed. The second player was from Amazon UK.

[Rob2222]

Interesting, mine non-RB-friendly has the same "serial"-number.
So it must be a model/submodel number:
I have too: BI1004CAHK-8GB

Could maybe some FUZE-V2 owners with players that accept a RB-Bootloader-patched-Firmware post their model number here?

BR Robert

[Jennifur]

@Rob2222
The output of cksum and md5sum on the OF are as followed:
jennifur@alice:~/rockbox/rbutil/mkamsboot$ cksum fuzpa.bin
1724160563 15728640 fuzpa.bin
jennifur@alice:~/rockbox/rbutil/mkamsboot$ md5sum fuzpa.bin
1599cc73d02ea7fe53fe2d4379c24b66  fuzpa.bin

The output of cksum and md5sum on the patched firmware are as followed:
jennifur@alice:~/rockbox/rbutil/mkamsboot$ cksum boot.bin
847109887 15728640 boot.bin
jennifur@alice:~/rockbox/rbutil/mkamsboot$ md5sum boot.bin
65d84013a988c098cd23b2f45dd6311c  boot.bin

I would tell you the serial number of my Fuze, but that wore off.

[Rob2222]

@Jennifur:

Thank you. I just RE-CHECKED both MD5 sums, they are equal to the files i tried with.
So we are using the same files. So when you can upgrade from .33OF to .33RB than there is something in the player different.
Would you like to try reflashing .33OF and then .33RB?

BR
Robert

[Jennifur]

@Jennifur:

OK I just RE-CHECKED both MD5 sums, they are equal to the files i tried with.
So we are using the same files. So when you can upgrade from .33OF to .33RB than there is something in the player different.
Would you like to try reflashing .33OF and then .33RB?

BR
Robert

I did after checking the crc and md5. I got sick of the slotmusic icon after the first time I flashed.(I accidently hit North America when I started the OF after flashing the first time.)

EDIT:
If it helps. I got my Fuze for a Christmas gift. So it would look like something in the most recent batch of the players are preventing non-stock firmware being used. If the extended warranty on mine covers normal wear and tare I can try exchanging mine for a newer one.

[funman]

Could maybe some FUZE-V2 owners with players that accept a RB-Bootloader-patched-Firmware post their model number here?

BI0905BLCK-8GB

[DonDan]

Could maybe some FUZE-V2 owners with players that accept a RB-Bootloader-patched-Firmware post their model number here?

B10909BMYK-8GB

$ cksum.exe fuzpa_*bin
2176550167 15728640 fuzpa_02.03.31_OF.bin
1258673945 15728640 fuzpa_02.03.31_pached_ver2.0.bin
1724160563 15728640 fuzpa_02.03.33_OF.bin
847109887 15728640 fuzpa_02.03.33_pached_ver2.0.bin

$ md5sum.exe fuzpa_*bin
74fb197ccd51707388f3b233402186a6 *fuzpa_02.03.31_OF.bin
326bed432ac27923df2100a5097369e2 *fuzpa_02.03.31_pached_ver2.0.bin
1599cc73d02ea7fe53fe2d4379c24b66 *fuzpa_02.03.33_OF.bin
65d84013a988c098cd23b2f45dd6311c *fuzpa_02.03.33_pached_ver2.0.bin


Same check/md5 sums here. It works with  both of them. Downgrading from 33_patched to 31_patched is also possible.

[ssorgatem]

Could maybe some FUZE-V2 owners with players that accept a RB-Bootloader-patched-Firmware post their model number here?

BH0906BMTK-4GB

It's black and seems to not behave exactly like the rest in in stuff about USB. My girlfriend has also a blue 4Gb fuzev2 which behaves exactly like my fuzev2, but it's SN isn't anymore there.

I haven't tested unpatched .33, but unpatched .31 allowed me to install patched .26 and .33, and patched .33 allowed me to install too patched .26 and .31. Both of them were bought last august from an online seller (Pixmania), and were new units, coming with firmware .26

[id]

Could maybe some FUZE-V2 owners with players that accept a RB-Bootloader-patched-Firmware post their model number here?

BI0912BMTK-8GB

[funman]

Can you test FS#11330 on Clip v1/v2/+ ?

It gets between 5 and 10 minutes more runtime but I want to be sure it's real and not random variation.

Just run battery_bench with and without the patch, using the same settings, and post both files on the ticket.

Thanks

[Julian67]

Could maybe some FUZE-V2 owners with players that accept a RB-Bootloader-patched-Firmware post their model number here?

B10901BKHK-8GB

[FlynDice]

Could maybe some FUZE-V2 owners with players that accept a RB-Bootloader-patched-Firmware post their model number here?

BH0812BKGK-4GB       Flashes all firmware just fine.