Sansa Clip+ "unknown original firmware" version.

[Groundhog]

Is there a way of using the Rockbox Utility with Sansa Clip+ firmwares newer than v. 01.02.15? The only OF that I can find online is v. 01.02.16 and I'm getting an "Original Firmware Unknown" error when I try to install Rockbox via the utility. Cheers.

[saratoga]

Just use the previous firmware:

http://mp3support.sandisk.com/firmware/clipplus/clipplus01.02.15.zip

[bertrik]

There is already a fix in our software archive to allow patching 1.02.16, but it's not in our current rbutil release yet. The next release of rbutil will most likely support this newer firmware.

[Groundhog]

Just use the previous firmware:

http://mp3support.sandisk.com/firmware/clipplus/clipplus01.02.15.zip

Thanks, now I have it and the Utility appears to have worked perfectly. I looked all over the Sansa site and could not find previous firmwares anywhere, so cheers!

[hardhu]

There is already a fix in our software archive to allow patching 1.02.16, but it's not in our current rbutil release yet. The next release of rbutil will most likely support this newer firmware.

Is it possible to know when will approximately be ready this next release?

[saratoga]

There is already a fix in our software archive to allow patching 1.02.16, but it's not in our current rbutil release yet. The next release of rbutil will most likely support this newer firmware.

Is it possible to know when will approximately be ready this next release?

Its whenever the rbutil people are ready for a new release.

[hardhu]

There is already a fix in our software archive to allow patching 1.02.16, but it's not in our current rbutil release yet. The next release of rbutil will most likely support this newer firmware.

Is it possible to know when will approximately be ready this next release?

Its whenever the rbutil people are ready for a new release.

This means: days, weeks, months?
I am not forcing anybody, just curious to know.

[saratoga]

Theres usually a new release every few months. 

[bluebrother]

Is it possible to know when will approximately be ready this next release?

In the past releases have been made approximately every 3 - 4 month. You can easily extract this from the RockboxUtility wiki page. In the meantime you can also try svn binaries (see my signature) -- I've updated them just now.

Given the current number of changes it would make sense to get a new release done soon. But someone needs to find the time to actually do it

[hardhu]

Is it possible to know when will approximately be ready this next release?

In the past releases have been made approximately every 3 - 4 month. You can easily extract this from the RockboxUtility wiki page. In the meantime you can also try svn binaries (see my signature) -- I've updated them just now.

Thanks for your answer, I've tried your svn binaries, but rbutil crash during autodetection of device connected (this didn't happen with 1.2.10). If you need more info to debug the problem I am glad to help.

[bluebrother]

Thanks for your answer, I've tried your svn binaries, but rbutil crash during autodetection of device connected (this didn't happen with 1.2.10). If you need more info to debug the problem I am glad to help.

This is strange -- there hasn't been any change in the autodetection code since the last release.

Does it work if you don't use autodetection? Otherwise something might have been went wrong building the binaries (can't imagine what right now, but who knows ...)

[hardhu]

Thanks for your answer, I've tried your svn binaries, but rbutil crash during autodetection of device connected (this didn't happen with 1.2.10). If you need more info to debug the problem I am glad to help.

This is strange -- there hasn't been any change in the autodetection code since the last release.

Does it work if you don't use autodetection? Otherwise something might have been went wrong building the binaries (can't imagine what right now, but who knows ...)

Yes, it works without (apparently) problems. To be more precise, with 1.2.10 autodetection doesn't cause rbutil to crash, but it only detects the correct device, missing the correct mount point.

[bluebrother]

Yes, it works without (apparently) problems. To be more precise, with 1.2.10 autodetection doesn't cause rbutil to crash, but it only detects the correct device, missing the correct mount point.

That's not that surprising -- autodetection has quite a couple of flaws and is on the todo list for getting rewritten since quite a while. It shouldn't crash though

[mefsute]

I am trying to install RockBox on a Sansa Clip+.

The Sansa updater identifies my firmware as 1.02.15, but when I run the RockBox installer, it aborts with error message: "Original firmware unknown, please try an other version. Tested Clip+v1 versions are : 01.02.09, 01.02.13, 01.02.15, 01.02.16"! This is especially frustrating as my version is explicitly listed as an OK alternative in the error message! Or does the presence/absence of the leading zero on the version number matter more than I am imagining?

Thought I might use saratoga's link to retrieve and reinstall 1.02.15, but noticed name of .bin file in the download is clppa.bin, whereas the .bin file on my player is called DID.bin! Is this significant?

Any advice on how to proceed most appreciated ...

More generally (sorry if this is naive, but the instructions are not crystal-clear), my assumption is that the overall process is as follows ...
1) copy the .bin file from my player to my computer
2) run the RockBox Utility to amend the local .bin file
3) copy the amended .bin file back to the player.

Again, grateful for any guidance ...

[saratoga]

Yes its significant, dd.bin is not a clip plus firmware file.