Thank You for your continued support and contributions!
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-4GBBI 0901 BKHK-8GBBI 0905 BLCK-8GBBH 0906 BMTK-4GB BI 0909 BMYK-8GBBI 0912 BMTK-8GBBI 1004 CAAK-8GBUnits 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.
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.
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=38046with mkamsboot.exe from http://forums.rockbox.org/index.php?topic=14064.msg167356#msg167356and output was http://pastie.org/981998I also tried 02.02.26 from http://daniel.haxx.se/sansa/amsfw.htmlwith 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#M42952You 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> MUSIC01.01.1980 00:00 320 SYS_CONF.SYS01.01.1980 00:00 <DIR> RECORD01.01.1980 00:00 <DIR> AUDIBLE01.01.1980 00:00 <DIR> PHOTO01.01.1980 00:00 <DIR> VIDEO01.01.1980 00:00 <DIR> PODCASTS01.01.1980 00:00 <DIR> AUDIOBOOKS01.01.1980 00:00 51.237 RES_INFO.SYS01.01.1980 00:00 83 version.sdk01.01.1980 00:00 7.800 VIDEO_BM.SYS01.01.1980 00:00 114 DID.bin01.01.1980 00:00 1.862.468 MTABLE.SYS 6 Datei(en), 1.922.022 Bytes 7 Verzeichnis(se), 7.675.346.944 Bytes freiAny new file maybe?BR and thanks in advanceRobert
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.
If that's the reasoning for blocking off updates, it seems fairly silly since the volume limit is circumvented so easily.
as far as I know the C+ is identical worldwide and the only region difference is selectable in software
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.
Page created in 0.215 seconds with 68 queries.