Using Rockbox and Rhapsody on Fuze V2 (it works!!!)

[P.Opus]

I know most people have no interest in using Rhapsody on a Rockbox enabled Fuze, but I really like to use Rhapsody Channels to "try" new music, so my inability to communicate with Rhapsody after installing Rockbox was a pretty big deal.

Well I finally got my Fuze to be able to not only run Rockbox but also keep my Rhapsody integration (kind of).  If you LOVE Rockbox, and still desire Rhapsody track support, I have a solution.  (NOTE:  I Don't load Audible books, so I don't if it will work with Audible books, but if the Audible DRM is similar to Rhapsody, then there is no reason it can't)

You will need the following:

- The latest fuze firmware (fuzea.bin) available on the forums.sandisk.com forum.  (keep this in a safe location, you will need it)

- The Rockbox Utility for loading Rockbox (easiest method of installing Rockbox)

- Fuze V2 (I haven't tested on other Sansa platforms but it should work similarly)

- Rhapsody client software and a Rhapsody to go subscription:

 

SETTING UP YOUR FUZE FOR ROCKBOX

 

Step 1.  Load your Rhapsody Tracks and channels on your Rhapsody player and re-license your player so that your tracks are all up to date and you have approximately 30 days remaining until you need to sync your device to Rhapsody

Step 2.  Switch the players USB mode to MSC.  Use the Rockbox Utility to load Rockbox on your player.  Use the Complete installation button from the Quckstart Tab for the easiest installation.  Rockbox will first install a bootloader by creating a modified fuzea.bin file and installing it on your device.   This will allow your Fuze to "dual boot" between Sansa Firmware and Rockbox  The Utility will then download the latest stable version and install it to your player.  The installation will NOT alter the fuzea.bin file stored on your computer.

Step 3.  Once installation is finished, disconnect your player.   it will refresh your media and will change your settings as if you just upgraded firmware.  Your tracks should still be playable however.  Keep the player in MSC mode.  Turn off your player.

Step 4.  Once rockbox is loaded to your player, it will default to Rockbox when you turn on the player. .

 

At this point you will be able to switch between Rockbox and Original Firmware at your whim.

 

If you want to use Rockbox, simply turn on your player. I use Rockbox MOST of the time because it has better database handling and adds a lot of functionality to the player (like the ability to create playlists directly on my player)  In my case, its the ONLY way I can access to all of my Music collection since Rockbox does NOT have the 8000 song DB limit that the original firmware has.

 

If you want to boot into original firmware to play subscription music or Rhapsody channels, simply turn off the player, hold down the left side of the scroll wheel and turn on your player.

 

NOTE:  VERY IMPORTANT!!!! NEVER ADJUST YOUR DATE AND TIME WHILE RUNNING THE ROCKBOX FIRMWARE.  DOING SO WILL IMMEDIATELY EXPIRE YOUR SUBSCRIPTION CONTENT THE NEXT TIME YOU BOOT INTO ORIGINAL FIRMWARE.  You will simply have to "live" with the fact that when running Rockbox, your Date and Time will be incorrect.

 

TO ADD UNPROTECTED CONTENT:

 

Step 1:  With your player off, plug it into your computer with the sync cable.  Your player will boot in original firmware.  Since it is now a Mass Storage Class device, you can simply copy and paste into the player or use a program like Winamp or Media Monkey.

Step 2:  Once you have transferred your unprotected content, disconnect the player.  The player will reboot automatically and you will have to wait the Updating Media message.  Once this is finished, you can power cycle the player to get back into Rockbox.

 

TO ADD ADDITIONAL RHAPSODY TRACKS, UPDATE YOUR CHANNELS, OR RENEW YOUR DEVICE LICENSE.

 

At some point you will need to connect your player to Rhapsody to keep your DRM content playable.  Unfortunately, the modified boot loader prevents your player from properly communicating with Rhapsody even if it is in MSC mode.  So we need to temporarily remove the Bootloader.  Luckily its simple.

 

Step 1:  Connect your player to your computer (with the player in MSC mode)

Step 2:  Copy your original fuzea.bin file to the root of the player.

Step 3:  Remove the player from your computer.  This will force a firmware upgrade and will effectively remove the bootloader from your player.  At this point your player will boot into original firmware and Rockbox will not be available until you reload the bootloader

Step 4:  Your player should default it's USB mode back to Auto Detect.  If you wish, you can manually change it to MTP mode so you can connect to Rhapsody.  However, in most cases, Auto Detect will work just fine.

Step 5:   Reconnect your player to your computer and launch Rhapsody.  Your player should now communicate properly with Rhapsody and you should be able to Renew your licenses, add or remove subscription tracks, and update your channels.

 

Once you have updated your Rhapsody content, you will now want to reload the bootloader so that Rockbox is accessible.

 

REINSTALLING THE ROCKBOX BOOTLOADER:

 

Step 1:  Change your USB mode on your player to MSC mode

Step 2:  Connect your player to your computer

Step 3:  Run Rockbox Utility, and click the installation tab

Step 4:  Choose the "Install the Bootloader" option.  The Utility will ask you to browse to your fuzea.bin file so it can create the bootloader.  It will then install the boot loader on your player.

Step 5.  Once bootloader installation is finished, disconnect your player.   it will refresh your media and will change your settings as if you just upgraded firmware.  Your tracks should still be playable however.  Keep the player in MSC mode.  Turn off your player.

Step 6.  Once rockbox is loaded to your player, it will default to Rockbox when you turn on the player.

 

I know, the documentation seems to be more trouble than it's worth, but it's really quite easy.  And typically I only do this about once a month because I fill up on channels, toggle between my music and my Rhapsody Channels until my subscription has almost expired.  As far as other subscription tracks go, I may load the occasional album from Rhapsody to see how I like it.  If I like it enough to hold it on my player for more than 30 days, then I'll buy it, and load it as a non-protected .mp3 and use Rockbox to play it.

 

I hope this helps those users who love Rockbox, or by necessity NEED Rockbox, but still mourn the variety of Rhapsody Channels or test driving the occasional new album.

[bertrik]

What time and date does rockbox display?

[P.Opus]

Original firmware Date and Time 10:25 AM 9/10/2011.  Rockbox Time:  7:00 AM 10/5/2013.

I get it now.  It makes perfect sense!!!

Setting Date and time in the original firmware does not write to the hardware clock.  It justs sets an offset between the hardware clock and what is displayed in the firmware.  This would prevent users from simply keeping their DRM protected content forever by trying to set back the date and time through the original firmware. 

When you connect to Rhapsody, it sets a value to your hardware clock.  It also readjusts the offset between the hardware clock and the firmware so that the user doesn't notice whats going on in the background.

When DRM material is loaded, the certificate is witten based on the current value of the hardware clock.  Tracks are set to expire 30 days from the value on the hardware clock. 
 
When you download Rockbox, you don't "break" DRM per se.  You do, however do two things.

1.  You eliminate the players ability to communicate with the Rhapsody software.  I don't know why, perhaps there is a checksum or value the software expects that changes when the bootloader is created.  This would make sense.  Rhapsody wants to make sure you are running unmodifed firmware.

2.  When you adjust the date and time in Rockbox you write changes to the hardware clock.  This has the side effect of voiding all your track licenses as your track licenses are now outside the expiration date.

Since the Rhapsody application wlll no longer communicate to your device, then you have no way of renewing the licenses.

In fact, I'm pretty sure that each time you connect to Rhapsody to renew your tracks, it changes the hardware clock setting to a new value just so someone could not "predict" the offset and find a way to extend their licenses. 

Pretty clever actually.

Even if the bootloader did allow you to communicate with Rhapsody, then everytime your login and renew your licenses, it would affect the date and time displayed in Rockbox, and if you tried to set it back, you'd have the same problem.

[bertrik]

Basically, the AMSv1 and AMSv2 players just count seconds starting from some "base date" (= date/time when second value = 0).
My theory so far, was that different models just had different base date.

Interesting theory about the RTC date/time being changed when doing something Rhapsody related.
Can you confirm this, for example do you see the date/time change in rockbox after contacting Rhapsody in the OF?

[P.Opus]

i was simply suggesting that Rhapsody manipulates the RTC because it would make sense. 

Rhapsody does have a utility (hidden) called "reset secure clock" which is a troubleshooting step Rhapsody uses if you are having a problem connecting.

I don't know if the RTC is reset everytime you connect.  But I imagine it is reset during the "reset secure clock" function.  I'll have to check if it is done when you first authorize a device as well.

Thinking about it, I doubt it changes it each time you connect.

I'll do some checking.