Help? Rockbox works on Clip+, then fails; my attempts to reinstall fail

[Mark Colan]

Executive Summary: After two freezes while playing then restarting Rockbox on my Sansa Clip+, it stopped working altogether.  I tried simply reinstalling with RockboxUtility, then reloading the original firmware and reinstalling Rockbox, then formatting the Clip+, reloading, and reinstalling Rockbox.  The original firmware comes up and works, but Rockbox does not.

I tried everything I could think of (see Details below), and would like some suggestions to restore Rockbox.  Thanks!

Versions:

OS: Windows7 64-bit, latest patches installed
RockboxUtility: v1.2.8 and v1.2.9
Clip+ firmware: 01.02.15

Details:

Automatic installation of v1.2.8 of Rockbox proceeded normally, and I used the player on many occasions with no problems.  I keep the player in MSC mode.

One day I was playing a playlist. During one song, the player became silent.  The panel showed it was still playing the song.  Buttons did not do anything, except the power, so I turned it off and restarted it successfully.

I think I successfully played that song, but it hung in the same way for the next song.  When I tried to restart it, Rockbox booted, but it said "Firmware file not found" (may not be exact: from my memory).  Rockbox does not play.

I tried reinstalling Rockbox with RockboxUtility (same way, always Automatic).  There was a new version (1.2.9), so I used it.  It appeared to install normally.  Rockbox did not start - I THINK with the same "Firmware file not found" message.  Note that during installation, I am required to supply the Clip+ firmware file, and I did; had I not, it would not have installed normally.

I read somewhere that Rockbox could be removed by reinstalling the Sansa firmware, which I did by dragging the dat and bin files onto the player file system, then disconnecting from the computer.  It said "Updating Firmware" and worked correctly.  It started fine with the Sansa firmware.  I noticed that the .rockbox folder was gone, suggesting that Rockbox had been properly removed.  I reinstalled Rockbox again (same way), but it said there was an existing installation, did I want to back it up.  The installation completed normally.  Disconnected player, turned it off and on, but Sansa firmware comes up, not Rockbox.

I backed up all files onto my computer, then used the Sansa Format function.  Noted that even after reformatting, Sansa firmware still works, and basic file system is in place.  I updated Sansa firmware again just to be sure.  I reinstalled Rockbox (same way).  Rockbox still does not start; Sansa firmware works fine, but I prefer Rockbox and want it back.

Would very much appreciate some help, thanks!

[Raiden175]

Well I can't tell you much about the first part but I do know that when you update it with the Sansa Firmware it removes the boot loader *atleast on the Sansa Fuze* I did the same thing. So try reinstalling the boot loader and tell me how it goes from there.
And you will again need Sansa's Firmware.

[Mark Colan]

Thanks for your reply.

I have been doing the complete installation, which includes the bootloader.  As noted, it has asked for the Clip+ firmware, which I think is an indication that the bootloader is being installed. 

To try something different, I went to the Installation tab and tried installing the boot loader and Rockbox itself separately, using those buttons.  It has not changed the situation: I still get Sansa's firmware instead of Rockbox.

So I still need help.

[saratoga]

Do you get the firmware update message?

[Raiden175]

Hehe I didn't know rockbox had a complete installation. hehe.

Anyways try this.
Use the removes buttons on Rockbox utility. Remove the .rockbox folder from your files in the windows explorer. Reinstall Rockbox but with the Installation buttoms first. So first Install the bootloader and then install Rockbox.

Try it and tell me how it works out:)

[Mark Colan]

saratoga wrote: Do you get the firmware update message?

I don't know, sorry, but see below.  As I tried what Raiden175 suggested, I did see it.

Raiden175: I did the following

Noticed that there was no .rockbox folder, which surprised me.
Used the Uninstall Rockbox button to remove all components except presumably the bootloader, which has a separate button.
Used the Remove Bootloader button.  It said it failed, suggested I update the firmware to get rid of the bootloader.
Updated Sansa firmware by dragging bin and dat files to the root then disconnecting.  Waited for firmware upgrade to finish.
Switched USB mode back to MSC (because firmware refresh changes it back to auto)
Installed bootloader using button on Installation tab.
Installed Rockbox using button on Installation tab.
Still no .rockbox folder!  Is this a symptom of the problem?
Disconnected.
Waited for Sansa refreshing media.
Turned off Clip+.
Turned on Clip+.  It still starts Sansa firmware.

I'm still hosed.  Other ideas?  Appreciate the help so far.

[Raiden175]

Well I'm not much of a expert on Rockbox. Maybe Mods or Experts can Help you.

But last thing I can suggest is manual installation? You can try that.

And sorry I couldn't be much help!  :'(

And I'm pretty sure the .rockbox folder missing is the cause!

[saratoga]

saratoga wrote: Do you get the firmware update message?

I don't know, sorry, but see below. 

Then find out ?

Noticed that there was no .rockbox folder, which surprised me.

If you can't install the bootloader, it makes little difference if you've installed the main build.  Without a bootloader nothing will be run.  Stop messing with that and figure out why you can't install the bootloader.  Then once you've got that figured out, you can put your player into MSC mode and extract a build. 

[torne]

The .rockbox folder disappearing in the first place (causing your initial problem) suggests your filesystem might be corrupted; this may explain a whole host of subsequent problems

[Mark Colan]

As am experienced PC user, I'm embarrassed to reveal that this was user error, but it does suggest a way to improve RockboxUtility.

When I first used RU a few weeks ago, I autodetected the Clip+.  More recently, I plugged in a USB drive when my Clip+ was not connected, and it assigned the same letter formerly assigned to my Clip+.  Connecting Clip+ assigned a new drive letter, but RU was looking at the old drive letter, which is now a hard disk.  I did not think to autodetect again, so RU installed to the hard disk.  By the way, it installs much faster that way! 

If I can make this mistake, it will bite others too.  RU could be enhanced to automatically check on start-up to verify that the configured drive has expected files for the OF, and give a warning if not found, suggesting that the user try AutoDetect again.

RU and Rockbox are truly useful works, and I am grateful to have them, as well as a community willing to help out in using them.   I appreciate the time and consideration for all who answered.
Post Merge: May 05, 2011, 07:28:15 AM

Stop messing with that and figure out why you can't install the bootloader.

What should I be looking for in the file system to verify that bootloader is installed?

Then once you've got that figured out, you can put your player into MSC mode and extract a build. 

Shouldn't I always have the player in MSC mode for anything I do with Rockbox? Do I leave MSC mode to verify that bootloader is installed?