Rockbox Technical Forums

Third Party => Repairing and Upgrading Rockbox Capable Players => Topic started by: ericycle on September 11, 2016, 08:45:09 AM

Title: Sansa Clip+ Device not recognized and doesn't boot after successful installation
Post by: ericycle on September 11, 2016, 08:45:09 AM
Hi,

So yesterday I used the Rockbox Utility to install version 3.13 on my Sansa Clip+ for the first time. The installation was successful. I used the player for several hours, playing with different features, rebooting it into original firmware and rebooting back into Rockbox. Everything was working. I fell asleep listening to it and I suspect the battery had discharged.
Today I put it to charge, however, I keep getting 'USB Device Not Recognized' message every time. The device screen shows a dim image of a USB cable connector.

The second part of the problem is that though I have left it connected to the USB for hours, it still does not boot, neither into Rockbox, nor into the stock firmware. No response, however I play and hold the power button.

What can I do now?

Thanks
Title: Re: Sansa Clip+ Device not recognized and doesn't boot after successful installation
Post by: saratoga on September 11, 2016, 03:52:29 PM
Hold power for 30 seconds and it should reboot. Once you get it booting, update to the current build. USB is not very stable in 3.13.
Title: Re: Sansa Clip+ Device not recognized and doesn't boot after successful installation
Post by: [Saint] on September 11, 2016, 07:29:49 PM
Adding to this post to make it absolutely clear that you _should not_ be using the 3.13 release at all, really.

To do so it to cast off literally years of bug fixes, improvements, features and optimizations. There really is a very highly limited subset of devices that I would actually suggest people prefer the release over the development builds, and that list doesn't include any of the SanDisk devices.

I would very highly advise updating. You can do so without reinstalling the bootloader, and without data loss. Honestly, you don't even need Rockbox Utility to manage this for you at all. That is only (arguably) useful for initial installs. You may simply download the current development build for your device and extract the archive to the root of the device, while allowing it to replace any and all original files.

This is all Rockbox Utility is doing for you anyway. I guess it seems easy to think that there is more to it than this, but behind the scenes all it is doing during updates is providing a graphical front end for downloading and extracting a .zip archive. There's no fancy magic involved here for updating, all that magic revolves around patching the original firmware with the bootloader, which you have already done and will never need to do again unless instructed to.


[Saint]