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

[funman]

Check the battery debug menu so you can give more info with your report

[lazy]

i just fully charged it via OF
should i let it drain, then do the debug?

[Xanikseo]

This is gonna sound trivial compared to bricked fuzes and bootloader-patched-fws not working, but the backlight doesn't fade in smoothly anymore on the fuzev2 . It kinda switches on, off and on again, without really fading in nicely. This has been going on for a few days I reckon... Sorry I didn't report this earlier

[Vague Rant]

i just fully charged it via OF
should i let it drain, then do the debug?

As a general rule, it's probably most practical to debug any problems you're having while you're having them rather than after the event. Not saying this wouldn't provide any useful information, but would most likely have been more helpful during the issue.

[mbr]

• 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

I just bought a Sansa Fuze. It has the serial number BI 1004 CAHK - 8GB. It is not possible to install a patched 2.3.31 firmware with rockbox bootloader.

But I modified the 2.3.31 firmware with a hex editor (HipHop->oiphHp). The modified firmware installs without any problem.

[EDIT]
Additionally modified "http://" to ":ttph//". Update also flawless. It seems that at last the checksum didn't change.
[/EDIT]

[Rob2222]

I didnt had the time for report yet,
but I had the same results as MBR. Hex-Edited firmware he accepts.

Also updated my stats post about this issue:
http://forums.rockbox.org/index.php?topic=14064.msg167599#msg167599

(I will keep this post updated when I get new information for now)

BR Robert

[lazy]

i'm charging it now, how do i get to the debug menu while it's charging, i have no access to anything while it's charging

[saratoga]

i'm charging it now, how do i get to the debug menu while it's charging, i have no access to anything while it's charging

Are you charging in the OF?  If so, you should probably be charging in rockbox so you have access to rockbox menus.  Hold center while you plugin the USB cable to charge in rockbox (see the manual).

[Xanikseo]

OK so these "fuzev3"s (okok fuzev2s) obviously calculate the checksums and make sure they match with known values. This begs the question: how will it accept new fws released by sansa, since it can't know the md5sums before they are released? Maybe if we change the version number reported by fuzpa.bin to 02.03.35 or something, it would accept the fw, since it checking the md5sum of an unreleased fw should be pointless (I'm hoping sansa had some sense)?

Or maybe Sansa aren't planning to release anymore fw updates.... Which would be disappointing.

EDIT: Rob2222: I also have a BI  0901 BKHK-8GB, and can flash whatever I want.

[lazy]

i just plug it in, and it boots to rockbox with a usb plug pic (and cant do anything else)
i just plugged it in with centre pressed and it appears to be charging and can move around

but just now, i plugged it in (with the usb plug pic) for an hour, and it didnt charge again (checked battery, was still at 1%)
the last thing i did that might have caused this is that i plugged it into a usb wall charger (from phone)

[Jennifur]

This is gonna sound trivial compared to bricked fuzes and bootloader-patched-fws not working, but the backlight doesn't fade in smoothly anymore on the fuzev2 . It kinda switches on, off and on again, without really fading in nicely. This has been going on for a few days I reckon... Sorry I didn't report this earlier

Make sure Backlight Fade In and Backlight Fade out are on. Its under Settings -> General Settings -> Display -> LCD Settings

[Xanikseo]

Backlight fade in and out are both set as yes in settings as always.

I've noticed that backlight fade in and out are fine just after you switch on. But as soon as you play a file, fade in is not smooth, even if playback is paused, and no matter what screen you are on.

Ah! I stopped playback altogether by holding down home, and fade in and out are smooth again.

[Rob2222]

Xanikseo:
Its more probable that the new units check a flag/byte/mark in the new firmware at a specific location, that the old firmware and the RB firmware doesnt have.
Even more player has a reserved (hidden) storage area where the first half is the firmware-file-data and the second half has data, too.
In the data in the second half of the reserved space can be a difference, too.
But to see this data you have to open the unit and connect it in the "recovery" mode like found out and described by funman in the SansaAMSUnbrick wiki article.

BR Robert

[Xanikseo]

Its more propable that the new units check a flag/byte/mark in the new firmware at a specific location, that the old firmware and the RB firmware doesnt have.
Even more player has a reserved (hidden) storage area where the first half is the firmware-file-data and the second half has data, too.
In the data in the second half of the reserved space can be a difference, too.
But to see this data you have to open the unit and connect it in the "recovery" mode like found out and described by funman in the SansaAMSUnbrick wiki article.

Ah ok, so the rockbox bootloader modifies the part of the fw file which the new fuzes check, or at least inserts code above the flag/byte/mark which is checked.

There was some talk a few weeks ago about some byte being different in the new 02.03.* fws. I take it this is related...

[Rob2222]

But the "bad" fuzes accept 02.03.31 AND 02.03.33.

BR Rob