Turn on suggestions
![]() Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Reply
Topic Options
Re: SanDisk Clip Sport Firmware 1.22 releasedOptions
12-14-2014 12:12 PM
I think the firmware on the older devices was made by Sandisk, whereas the new one was probably made by the company that designed the hardware, so a lot of features that were in the old player's firmware were probably never implemented in the new one. Interesting. If that's the case it would explain a lot.
Re: SanDisk Clip Sport Firmware 1.22 released[ Edited ]Options
12-14-2014 04:54 PM - edited 12-14-2014 04:56 PM so Sandisk most likely outsourced firmware developent to China*, and didn't even mention it? Niceee...
*) that would explain poor software (firmware) quality, as cheap Chinese mp3 players are known from having terrible software/firmware. Re: SanDisk Clip Sport Firmware 1.22 releasedOptions
12-20-2014 12:48 PM
I upgraded to the latest firmware, v1.22. This has gotten much, much worse. So much so that the player is now totally useless. When powering on the device, I now get the following error: 'Refreshing media' flashes by quickly. Then 'File system error! Restart the device or Format to Recovery!' Then the player shuts off.
Re: SanDisk Clip Sport Firmware 1.22 releasedOptions
12-21-2014 07:50 AM
I was able to get the device to come on and get to the menus. I selected the format option. But the problems continued. I eventually connected the device to my Windows PC via the USB. I selected to format the internal storage from Windows Explorer. I was then able to power on as before and get to my media. I then had to format my external storage as I could not get to the Music that had been previously loaded. Issues with "Unknown Artist" and "Unknown Album" persist with the new firmware. I previously had v1.17 installed.
*************BRICKED*************Options
12-24-2014 06:09 AM Soooooo.... After updating to 1.22, I kept losing my settings every other boot, and it would ask me again to set the language, world zone,etc...
So I decided to roll back to 1.17, but the firmware update failed half way, saying "error writing FW"; I used the same file that I used when I first upgraded from 1.09 to 1.17, so I am sure the file was not corrupt;
Now it is just stuck on the boot screen "SanDisk" and I cannot do anything; When I hold the power button for 10 seconds or more, the screen turns off, but when I release the button it turns on again to the same Sandisk splash screen;
It is not recognised by the computer when plugeed in via usb: I can call it bricked.
Now I wait for the battery to die out to see if it makes a difference, then return it to Amazon, get a new one, sell it fast BNIB and be done with SanDisk.
Good bye forever Re: SanDisk Clip Sport Firmware 1.22 releasedOptions
01-03-2015 09:38 PM It says to "copy hex file to player's root directory'' -- not sure what a "hex file" is, I guess it's the download, but I do not have a "Root directory" on my Clip Sport. I have "Audible", "Audiobooks", "Music", "Playlists" and "Podcasts". None of these folders contain anything called "root directory". I don't know what to do here, are there instructions in plain English somewhere? Re: SanDisk Clip Sport Firmware 1.22 releasedOptions
01-04-2015 02:18 AM The root directory is the Clip itself, not a folder on it. And the hex file is indeed the downloaded firmware file («upgrade.hex»). Just copy it to the Sport. Re: SanDisk Clip Sport Firmware 1.22 releasedOptions
01-05-2015 07:56 AM
Yes you do.
That's it. Drop the 'extracted' firmware file next to (not in) these folders. Re: SanDisk Clip Sport Firmware 1.22 releasedOptions
05-31-2015 11:08 AM Hi guys,
without the Firmware Updater,which I'm not able to install because of problems,I can't see which Firmware is the newest for my device(Clip Sport).I know that 1.22 is the newest at the moment but for the future I don't know. Re: SanDisk Clip Sport Firmware 1.22 releasedOptions
06-10-2015 08:31 AM Unlikely that there will be firmware revisions, but you simply can come here to check (and avoid having the Updater consume computer resources). |