2 \chapter{Installation
}\label{sec:installation
}
4 Installing Rockbox is generally a quick and easy procedure. However
5 before beginning there are a few things it is important to know.
7 \section{Before Starting
}
9 \opt{e200
}{\fixme{NOTE: These instructions will not work on the
10 ``Rhapsody'' version of the E200 series (also known as E200R). Please
11 follow the instructions at
12 \url{http://www.rockbox.org/twiki/bin/view/Main/SansaE200RInstallation
}.
}}
14 \opt{ipodnano,ipodnano2g,ipodvideo,e200,c200,e200v2,clipv1,clipv2,cowond2,fuze
}{
16 \item[Supported hardware versions.
]
17 \opt{ipodnano,ipodnano2g
}{
18 The
\playertype{} is available in multiple versions, not
19 all of which run Rockbox. Rockbox presently runs only on
20 the first and second generation Ipod Nano. Rockbox does
21 \emph{not
} run on the third, fourth or fifth generation Ipod Nano.
22 For information on identifying which Ipod you own, see this page on
23 Apple's website:
\url{http://www.info.apple.com/kbnum/n61688
}.
26 The
\playertype{} is the
5th/
5.5th generation
\playerman{} only.
27 Rockbox does
\emph{not
} run on the newer,
6th/Classic generation Ipod.
28 For information on identifying which Ipod you own, see this page on Apple's
29 website:
\url{http://www.info.apple.com/kbnum/n61688
}.
32 The
\playertype{} is available in multiple versions, not
33 all of which run Rockbox. Rockbox doesn't run on the
34 newer v2 models. They can be identified
35 by checking the Sandisk firmware version number under
36 Settings $
\rightarrow$ Info. The v1
37 firmware is named
01.xx.xx, while the v2 firmware begins with
03.
40 The
\playertype{} is available in multiple versions, and you need to make
41 sure which you have by checking the Sandisk firmware version number under
42 Settings $
\rightarrow$ Info. The v1 firmware is named
01.xx.xx, while the
43 v2 firmware begins with
03. Make sure that you are following the
44 instructions from the correct manual.
47 The
\playertype{} is available in multiple versions, and you need to make
48 sure which you have by checking the Sandisk firmware version number under
49 Settings $
\rightarrow$ Info. The v1 firmware is named
01.xx.xx, while the
50 v2 firmware begins with
02. Make sure that you are following the
51 instructions from the correct manual.
54 The
\playertype{} is available in multiple versions, not all of which
55 run Rockbox. Rockbox doesn't run on the newer v2 models. They can be
56 identified by checking the Sandisk firmware version number under
57 System Settings $
\rightarrow$ System Info. The v1 firmware is named
58 01.xx.xx, while the v2 firmware begins with
02.
61 Rockbox runs on all
\playerman{} \playertype{} and
\playertype{}+ variants
62 (
2 /
4 /
8 /
16GB, with or without DAB/DMB).
63 \note{Newer
\playertype{}+ hardware revisions use an updated power
64 management chip, and some functionality is not yet implemented on these
65 players (e.g. touchscreen support).
}
72 \item[Current limitations.
] Most Rockbox functions are usable on the
73 \playertype{}/
\playertype{}+, including music playback and most plugins, but
74 there are a number of shortcomings that prevent it from being a fully
77 \item An SD card is required to use many features, since the internal
78 flash memory is read-only in Rockbox.
79 \warn{The SD driver is still in development and may contain bugs.
80 There have been reports of SD cards becoming unusable after being used
81 with Rockbox on
\playerman{} \playertype{}. Only use old, low-capacity
82 cards until we are satisfied the driver is safe to use.\\
}
83 \item There is only basic touchscreen support. Further work is
84 required to make the UI more usable with a touchscreen in general.
85 \note{The touchscreen can be used in two modes, either a
3x3 grid mode
86 which divides the screen into areas to emulate a set of physical
87 buttons (the default setting), or ``absolute point'' mode where the
88 touchscreen is used to point to items on the screen.\\
}
94 \item[DRM capability.
] If your
\dap{} has a US firmware, then by installing Rockbox you will
95 \emph{permanently
} lose the ability to playback files with DRM.
101 \item[DRM capability.
] It is possible that installation of the bootloader
102 may lead to you
\emph{permanently
} losing the ability to playback files
111 \item[USB connection.
]
114 \item[Firewire connection.
]
116 To transfer Rockbox to your
\dap{} you need to
117 connect it to your computer. For manual installation/uninstallation, or
118 should autodetection fail during automatic installation, you need to know
119 where to access the
\dap{}. On Windows this means you need to know
120 the drive letter associated with the
\dap{}. On Linux you need to know
121 the mount point of your
\dap{}. On Mac OS X you need to know the volume
125 If you have Itunes installed and it is configured to open automatically
126 when your
\dap{} is attached (the default behaviour), then wait for it to
127 open and then quit it. You also need to ensure the ``Enable use as disk''
128 option is enabled for your
\dap{} in Itunes. Your
\dap{} should then enter
129 disk mode automatically when connected to a computer via
130 \nopt{ipod1g2g
}{USB.
}\opt{ipod1g2g
}{Firewire.
} If your computer does not
131 recognise your
\dap{}, you may need to enter disk mode manually. Disconnect
132 your
\dap{} from the computer. Hard reset the
\dap{} by pressing and
133 holding the
\ButtonMenu{} and
\nopt{IPOD_3G_PAD
}{\ButtonSelect{}}%
134 \opt{IPOD_3G_PAD
}{\ButtonPlay{}} buttons simultaneously. As soon as the
135 \dap{} resets, press and hold the
\nopt{IPOD_3G_PAD
}{\ButtonSelect{} and
136 \ButtonPlay{}}\opt{IPOD_3G_PAD
}{\ButtonLeft{} and
\ButtonRight{}} buttons
137 simultaneously. Your
\dap{} should enter disk mode and you can try
138 reconnecting to the computer.
141 When instructed to connect/disconnect the USB cable, always use
142 the USB port through the subpack, not the side 'USB Host' port. The side port
143 is intended to be used for USB OTG connections only (digital cameras, memory
146 \opt{sansa,e200v2,clipv1,clipv2,clipplus
}{
147 \note{The following steps require you to change the setting in
148 \setting{Settings $
\rightarrow$ USB Mode
} to
\setting{MSC
} from within the
151 \nopt{sansaAMS
}{\warn{Never extract files to your
\dap{} while it is in recovery mode.
}}
154 The installation requires you to use UMS mode and so
155 may require use of the UMS trick, whereby it is possible to force a MTP
156 \playertype{} to start up in UMS mode as follows:
158 \item Ensure the
\dap{} is fully powered off by
\opt{h10
}{using a pin to
159 push the small reset button inside the hole between the Hold switch and
160 remote control connector.
}\opt{h10_5gb
}{removing the battery and putting it back in again.
}
161 \item Connect your
\playertype{} to the computer using the data cable.
162 \item Hold
\ButtonRight{} and push
\ButtonPower{} to turn the
\dap{} on.
163 \item Continue holding
\ButtonRight{} until the USB Connected screen appears.
164 \item The
\dap{} will now appear as a regular disk on your computer.
166 \note{Once Rockbox has been installed, when you shut down your
\dap{} from Rockbox it will totally
167 power the player off so step
1 is no longer necessary.
}
169 \opt{gigabeatf
}{The installation requires you to change a setting in the
170 original firmware. Make sure the option under
\setting{Setup
171 $
\rightarrow$ Connections $
\rightarrow$ PC Connections
} is set to
172 \setting{gigabeat room
}. Also, during installation, do not connect your
173 \dap{} using the cradle but plug the USB cable directly to the
\dap{}.
176 The installation requires you to use UMS mode.
177 In order to start up your
\playertype{} in UMS mode you need to:
179 \item Turn off the
\dap{} (Original Firmware).
180 \item Connect your
\playertype{} to the computer using the data cable.
181 \item Push and hold
\ButtonPower{} (for about
2 seconds) until the "USB" screen appears.
183 The
\dap{} will now appear as a regular disk on your computer.
190 \item[Administrator/Root rights.
] Installing the bootloader portion of Rockbox
191 requires you to have administrative (Windows) or root (Linux) rights.
192 Consequently when doing either the automatic or manual bootloader install,
193 please ensure that you are logged in with an administrator account or have root rights.
199 \item[File system format.
] Rockbox only works on Ipods formatted with
200 the FAT32 filesystem (i.e. Ipods initialised by Itunes
201 for Windows). It does not work with the HFS+ filesystem (i.e. Ipods
202 initialised by Itunes for the Mac). More information and instructions for
203 converting an Ipod to FAT32 can be found on the
204 \wikilink{IpodConversionToFAT32
} wiki
205 page on the Rockbox website. Note that after conversion, you can still use
206 a FAT32 Ipod with a Mac.
210 \section{Installing Rockbox
}\label{sec:installing_rockbox
}\index{Installation
}
211 There are two ways to install Rockbox: automated and manual. The automated
212 way is the preferred method of installing Rockbox for the majority of
213 people. Rockbox Utility is a graphical application that does almost everything
214 for you. However, should you encounter a problem, then the manual way is
215 still available to you.\\
217 \opt{gigabeats
}{\note{The automated install is not yet available for the
218 \playerlongtype{}. For now you can use the manual method to install Rockbox.
219 Please still read the section on the automatic install as it explains
220 various important aspects of Rockbox, such as the different versions
223 \opt{hwcodec
}{Rockbox itself comes as a single package. There is no need
224 to install additional software to run Rockbox.
}
226 \opt{HAVE_RB_BL_ON_DISK
}{There are three separate components,
227 two of which need to be installed in order to run Rockbox:
}
228 \opt{HAVE_RB_BL_IN_FLASH
}{There are two separate components
229 which need to be installed in order to run Rockbox:
}
232 \opt{HAVE_RB_BL_ON_DISK
}{
233 \item[The
\playerman{} bootloader.
]
234 The
\playerman{} bootloader is the program that tells your
\dap{} how to load
235 and start the original firmware. It is also responsible for any emergency,
236 recovery, or disk modes on your
\dap{}. This bootloader is stored in special flash
237 memory in your
\playerman{} and comes factory-installed. It is not necessary
238 to modify this in order to install Rockbox.
}
240 \item[The Rockbox bootloader.
] \index{Bootloader
}
241 \opt{HAVE_RB_BL_ON_DISK
}{The Rockbox bootloader is loaded from disk by
242 the
\playerman{} bootloader. It is responsible for loading the Rockbox
243 firmware and for providing the dual boot function. It directly replaces the
244 \playerman{} firmware in the
\daps{} boot sequence.
245 \opt{gigabeatf
}{\note{Dual boot does not currently work on the Gigabeat.
}}}
247 \opt{HAVE_RB_BL_IN_FLASH
}{
248 The bootloader is the program that tells your
249 \dap{} how to load and start other components of Rockbox and for providing
250 the dual boot function. This is the component of Rockbox that is installed
251 to the flash memory of your
\playerman.
252 \opt{iaudio
}{\note{Dual boot does not currently work on the
\playertype{}.
}}}
254 \item[The Rockbox firmware.
]
255 \opt{HAVE_RB_BL_IN_FLASH
}{Unlike the
\playerman{} firmware, which runs
256 entirely from flash memory,
}
257 \opt{HAVE_RB_BL_ON_DISK
}{Similar to the
\playerman{} firmware,
}
258 most of the Rockbox code is contained in a
259 ``build'' that resides on your
\daps{} drive. This makes it easy to
260 update Rockbox. The build consists of a directory called
261 \fname{.rockbox
} which contains all of the Rockbox files, and is
262 located in the root of your
\daps{} drive.
268 Apart from the required parts there are some addons you might be interested
271 \item[Fonts.
] Rockbox can load custom fonts. The fonts are
272 distributed as a separate package and thus need to be installed
273 separately. They are not required to run Rockbox itself but
274 a lot of themes require the fonts package to be installed.
276 \item[Themes.
] The appearance of Rockbox can be customised by themes. Depending
277 on your taste you might want to install additional themes to change
282 \subsection{Automated Installation
}
284 To automatically install Rockbox, download the official installer and
285 housekeeping tool
\caps{Rockbox Utility
}. It allows you to:
287 \item Automatically install all needed components for using Rockbox
288 (``Minimal Installation'').
289 \item Automatically install all suggested components (``Complete Installation'').
290 \item Selectively install optional components.
291 \nopt{player
}{\item Install additional fonts and themes.
}
292 \item Install voice files and generate talk clips.
293 \item Uninstall all components you installed using Rockbox Utility.
296 Prebuilt binaries for Windows, Linux and Mac OS X are
297 available at the
\wikilink{RockboxUtility
} wiki page.\\
299 \opt{gigabeats,clipv1,clipv2,clipplus
}{\note{Rockbox Utility does not currently support the
300 \playertype{} and you will therefore need to follow the manual install
301 instructions below.\\
}}
303 When first starting
\caps{Rockbox Utility
} run ``Autodetect'',
304 found in the configuration dialog (File $
\rightarrow$ Configure). Autodetection
305 can detect most player types. If autodetection fails or is unable to detect
306 the mountpoint, make sure to enter the correct values. The mountpoint indicates
307 the location of the
\dap{} in your filesystem. On Windows, this is the drive
308 letter the
\dap{} gets assigned, on other systems this is a path in the
312 {\note{Autodetection is unable to distinguish between the
313 \playerman{} 30~GB and
60~GB /
80~GB models and defaults to the
314 30~GB model. This will usually work but you might want to check the
315 detected value, especially if you experience problems with Rockbox.
}
319 Rockbox Utility will ask you for a compatible copy of the original
320 firmware. This is because for legal reasons we cannot distribute
321 the bootloader directly. Instead, we have to patch the Iriver firmware
322 with the Rockbox bootloader.
324 Download a supported version of the Iriver firmware for your
325 \playername{} from the Iriver website, links can be found on
326 \wikilink{IriverBoot
}.
328 Supported Iriver firmware versions currently include
329 \opt{h100
}{1.63US,
1.63EU,
1.63K,
1.65US,
1.65EU,
1.65K,
1.66US,
330 1.66EU and
1.66K. Note that the H140 uses the same firmware as the H120;
331 H120 and H140 owners should use the firmware called
\fname{ihp
\_120.hex
}.
332 Likewise, the iHP110 and iHP115 use the same firmware, called
333 \fname{ihp
\_100.hex
}. Be sure to use the correct firmware file for
335 \opt{h300
}{1.28K,
1.28EU,
1.28J,
1.29K,
1.29J and
1.30EU.
336 \note{The US
\playername{} firmware is not supported and cannot be
337 patched to be used with the bootloader. If you wish to install Rockbox
338 on a US
\playername{}, you must first install a non-US version of the
339 original firmware and then install one of the supported versions patched
340 with the Rockbox bootloader.
}
341 \warn{Installing a non-US firmware on a US
\playername{} will
342 \emph{permanently
} remove DRM support from the player.
}}
344 If the file that you downloaded is a
\fname{.zip
} file, use an unzip
345 utility like mentioned in the prerequisites section to extract
346 the
\fname{.hex
} from the
\fname{.zip
} file
347 to your desktop. Likewise, if the file that you downloaded is an
348 \fname{.exe
} file, double-click on the
\fname{.exe
} file to extract
349 the
\fname{.hex
} file to your desktop.
350 When running Linux you should be able to extract
\fname{.exe
}
351 files using
\fname{unzip
}.
354 \subsubsection{Choosing a Rockbox version
}\label{sec:choosing_version
}
356 There are three different versions of Rockbox available from the
359 Release version, current build and archived daily build. You need to decide which one
360 you want to install and get the appropriate version for your
\dap{}. If you
361 select either ``Minimal Installation'' or ``Complete Installation'' from the
362 ``Quick Start'' tab, then Rockbox Utility will automatically install the
363 release version of Rockbox. Using the ``Installation'' tab will allow you
364 to select which version you wish to install.
368 \item[Release.
] The release version is the latest stable release, free
369 of known critical bugs. For a manual install, the current stable release of Rockbox is
370 available at
\url{http://www.rockbox.org/download/
}.
372 \item[Current Build.
] The current build is built at each source code change to
373 the Rockbox SVN repository and represents the current state of Rockbox
374 development. This means that the build could contain bugs but most of
375 the time is safe to use. For a manual install, you can download the current build from
376 \url{http://build.rockbox.org/
}.
378 \item[Archived Build.
] In addition to the release version and the current build,
379 there is also an archive of daily builds available for download. These are
380 built once a day from the latest source code in the SVN repository. For a manual install,
381 you can download archived builds from
\url{http://www.rockbox.org/daily.shtml
}.
385 \note{Because current and archived builds are development versions that
386 change frequently, they may behave differently than described in this manual,
387 or they may introduce new (and potentially annoying) bugs. Unless you wish to
388 try the latest and greatest features at the price of possibly greater instability,
389 or you wish to help with development, you should stick with the release.\\*
}
391 Please now go to
\reference{ref:finish_install
} to complete the installation procedure.
393 \subsection{Manual Installation
}
395 The manual installation method is still available to you, should you need or desire it
396 by following the instructions below. If you have used Rockbox Utility
397 to install Rockbox, then you do not need to follow the next section and can skip
398 straight to
\reference{ref:finish_install
}
400 \opt{gigabeats
}{\subsubsection{Installing the bootloader
}
401 \input{getting_started/gigabeats_install.tex
}
404 \subsubsection{Installing the firmware
}\label{sec:installing_firmware
}
406 \opt{gigabeats
}{\note{When your
\dap{} is in the Rockbox USB or bootloader
407 USB mode, you will see two visible partitions - the
150MB firmware
408 partition (containing at least a file called
\fname{nk.bin
}) and
409 the main data partition. Rockbox
\emph{must
} be installed onto the main
413 \item Download your chosen version of Rockbox from the links in the
415 \opt{ipodvideo
}{\note{There are separate versions of Rockbox for the
30GB and
416 60GB/
80GB models. You must ensure you download the correct version for your
419 \item Connect your
\dap{} to the computer via USB
420 \opt{sansa,sansaAMS,h10,h10_5gb,vibe500
}{ in MSC mode
}
421 \opt{ipod3g,ipod4g,ipodmini,ipodcolor
}{ or Firewire
}as described in
422 the manual that came with your
\dap{}.
424 \item Take the
\fname{.zip
} file that you downloaded and use
425 the ``Extract all'' command of your unzip program to extract
427 \opt{gigabeats
}{the main data partition of
}
428 \opt{cowond2
}{either an SD card or the internal memory of
}
430 \opt{cowond2
}{\note{If you have chosen to extract to the internal memory, it
431 will not be possible to save settings.
}}
434 \note{The entire contents of the
\fname{.zip
} file should be extracted
435 directly to the root of your
\daps{} drive. Do not try to
436 create a separate directory on your
\dap{} for the Rockbox
437 files! The
\fname{.zip
} file already contains the internal
438 structure that Rockbox needs.\\
}
441 If the contents of the
\fname{.zip
} file are extracted correctly, you will
442 have a file called
\fname{\firmwarefilename} in the main directory of your
443 \daps{} drive, and also a directory called
\fname{.rockbox
}, which contains a
444 number of other directories and system files needed by Rockbox.
447 % This has nothing to do with swcodec, just that these players need our own
448 % bootloader so we can decide where we want the main binary.
450 If the contents of the
\fname{.zip
} file are extracted correctly, you will
451 have a directory called
\fname{.rockbox
}, which contains all the files needed
452 by Rockbox, in the main directory of your
\daps{} drive.
455 \opt{swcodec
}{\nopt{gigabeats
}{
456 \subsubsection{Installing the bootloader
}
457 \opt{h100,h300
}{\input{getting_started/iriver_install.tex
}}
458 \opt{ipod
}{\input{getting_started/ipod_install.tex
}}
459 \opt{m3,m5,x5
}{\input{getting_started/iaudio_install.tex
}}
460 \opt{h10,h10_5gb
}{\input{getting_started/h10_install.tex
}}
461 \opt{gigabeatf
}{\input{getting_started/gigabeat_install.tex
}}
462 \opt{sansa
}{\input{getting_started/sansa_install.tex
}}
463 \opt{sansaAMS
}{\input{getting_started/sansaAMS_install.tex
}}
464 \opt{mrobe100
}{\input{getting_started/mrobe100_install.tex
}}
465 \opt{cowond2
}{\input{getting_started/cowond2_install.tex
}}
466 \opt{vibe500
}{\input{getting_started/vibe500_install.tex
}}
469 \subsection{Finishing the install
}\label{ref:finish_install
}
472 After installing you
\emph{need
} to power-cycle the
473 \dap{} by doing the following steps. Failure to do so may result in problems.
475 \item Safely eject / unmount your
\dap{} and unplug the USB cable.
476 \item Unplug any power adapter.
477 \item Hold the
\ButtonPower{} button to turn off the
\dap{}.
478 \item Slide the battery switch located on the bottom of the
\dap{} from
480 \item Slide the battery switch back from `off' to `on'.
485 After installing you
\emph{need
} to power-cycle the
486 \dap{} by doing the following steps.
488 \item Safely eject / unmount your
\dap{} and unplug the USB cable.
490 \opt{IAUDIO_X5_PAD
}{\ButtonPower}
491 \opt{IAUDIO_M3_PAD
}{\ButtonPlay}
492 button to turn off the
\dap{}.
493 \item Insert the charger. The Rockbox bootloader will automatically be flashed.
497 \opt{h10,h10_5gb,ipod,mrobe100,sansa,archos,sansaAMS,cowond2,vibe500
}{
498 Safely eject / unmount the USB drive, unplug the cable and restart.
502 Safely eject / unmount your
\dap{}.
507 \item Safely eject / unmount your
\dap{}.
509 \item \warn{Before proceeding further, make sure that your player has a full charge
510 or that it is connected to the power adaptor. Interrupting the next step
511 due to a power failure most likely will brick your
\dap{}.
}
512 Update your
\daps{} firmware with the patched bootloader. To do this, turn
513 the jukebox on. Press and hold the
\ButtonSelect{} button to enter the main menu,
514 and navigate to
\setting{General $
\rightarrow$ Firmware Upgrade
}. Select
515 \setting{Yes
} when asked to confirm if you want to upgrade the
516 firmware. The
\playerman{} will display a message indicating that the
517 firmware update is in progress. Do
\emph{not
} interrupt this process. When the
518 firmware update is complete the player will turn itself off. (The update
519 firmware process usually takes a minute or so.). You are now ready to go.
523 \opt{e200
}{Your e200 will automatically reboot and Rockbox should load.
}
527 \subsection{Enabling Speech Support (optional)
}\label{sec:enabling_speech_support
}
528 \index{Speech
}\index{Installation!Optional Steps
}
529 If you wish to use speech support you will also need a voice file. Voice files
530 allow Rockbox to speak the user interface to you. Rockbox Utility can install
531 an English voice file, or you can download it from
\url{http://www.rockbox.org/daily.shtml
}
532 and unzip it to the root of your
\dap{}.
533 Rockbox Utility can also aid you in the creation of voice files with different voices
534 or in other languages if you have a suitable speech engine installed on your computer.
535 Voice menus are enabled by default and will come
536 into effect after a reboot. See
\reference{ref:Voiceconfiguration
} for details
538 Rockbox Utility can also aid in the production of talk files, which allow Rockbox
539 to speak file and folder names.
541 \section{Running Rockbox
}
542 \nopt{ipod,gigabeats,cowond2
}{When
543 you turn the unit on, Rockbox should load.
}
544 \opt{ipod
}{Hard reset the Ipod by holding
545 \opt{IPOD_4G_PAD
}{\ButtonMenu{} and
\ButtonSelect{} simultaneously
}%
546 \opt{IPOD_3G_PAD
}{\ButtonMenu{} and
\ButtonPlay{} simultaneously
}
547 for a couple of seconds until the
\dap{} resets. Now Rockbox should load.
550 \opt{gigabeats
}{Rockbox should automatically load when you turn on your player.\\
553 If you have loaded music onto your
\dap{} using the
\playerman{}
554 firmware, you will not be able to see your music properly in the
555 \setting{File Browser
} as MTP mode changes the location and file names.
556 Files placed on your
\dap{} using the
\playerman{} firmware can be
557 viewed by initialising and using Rockbox's database.
558 See
\reference{ref:database
} for more information.
}
562 To boot the Rockbox firmware set the
\ButtonHold{} switch immediately after
564 \note{If you have chosen to install to an SD card and it is inserted at power
565 on, Rockbox will boot from that card and use it as the primary drive for
566 storing settings, etc. If there is no SD card inserted, Rockbox will boot
567 from the internal memory, and it will not be possible to save settings.
}
572 If you have loaded music onto your
\dap{} using Itunes,
573 you will not be able to see your music properly in the
\setting{File Browser
}.
574 This is because Itunes changes your files' names and hides them in
575 directories in the
\fname{Ipod
\_Control} directory. Files placed on your
576 \dap{} using Itunes can be viewed by initialising and using Rockbox's database.
577 See
\reference{ref:database
} for more information.
582 \fixme{Add a note about the charging trick and place it here?
}
585 \section{Updating Rockbox
}
586 Rockbox can be easily updated with Rockbox Utility.
587 You can also update Rockbox manually -- download a Rockbox build
588 as detailed above, and unzip the build to the root directory
589 of your
\dap{} as in the manual installation stage. If your unzip
590 program asks you whether to overwrite files, choose the ``Yes to all'' option.
591 The new build will be installed over your current build.\\
594 \note{When your
\dap{} is in the Rockbox USB or bootloader
595 USB mode, you will see two visible partitions, the
150MB firmware
596 partition (containing at least a file called
\fname{nk.bin
}) and
597 the main data partition. Rockbox
\emph{must
} be installed onto the main
602 The bootloader only changes rarely, and should not normally
603 need to be updated.\\
606 \note{If you use Rockbox Utility be aware that it cannot detect manually
607 installed components.
}
609 \section{Uninstalling Rockbox
}\index{Installation!uninstall
}
611 \nopt{gigabeatf,m5,x5,archos,mrobe100,gigabeats
}{
612 \note{The Rockbox bootloader allows you to choose between Rockbox and
613 the original firmware. (See
\reference{ref:Dualboot
} for more information.)
}
616 \subsection{Automatic Uninstallation
}
617 \opt{gigabeats
}{\note{Rockbox can only be uninstalled manually for now.
}}
619 You can uninstall Rockbox automatically by using Rockbox Utility. If you
620 installed Rockbox manually you can still use Rockbox Utility for uninstallation
621 but will not be able to do this selectively.
623 \opt{h100,h300
}{\note{Rockbox Utility cannot uninstall the bootloader due to
624 the fact that it requires a flashing procedure. To uninstall the bootloader
625 completely follow the manual uninstallation instructions below.
}}
627 \subsection{Manual Uninstallation
}
630 If you would like to go back to using the original
\playerman{} software,
631 connect the
\dap{} to your computer, and delete the
632 \fname{\firmwarefilename} file.
636 If you would like to go back to using the original
\playerman{} software,
637 connect the
\dap{} to your computer, and delete the
638 \opt{h10
}{\fname{H10
\_20GC.mi4
}}\opt{h10_5gb
}{\fname{H10.mi4
}} file and rename
639 \fname{OF.mi4
} to
\opt{h10
}{\fname{H10
\_20GC.mi4
}}\opt{h10_5gb
}{\fname{H10.mi4
}}
640 in the
\fname{System
} directory on your
\playertype{}. As in the installation,
641 it may be necessary to first put your device into UMS mode.
645 If you would like to go back to using the original
\playerman{} software,
646 connect the
\dap{} to your computer, and delete the
647 \fname{jukebox.mi4
} file and rename
648 \fname{OF.mi4
} to
\fname{JUKEBOX.mi4
}
649 in the
\fname{System
} directory on your
\playertype{}. As in the installation,
650 it may be necessary to first put your device into UMS mode.
654 If you would like to go back to using the original
\playerman{} software,
655 connect the
\dap{} to your computer, and delete the
656 \fname{pp5020.mi4
} file and rename
657 \fname{OF.mi4
} to
\fname{pp5020.mi4
}
658 in the
\fname{System
} directory on your
\playertype{}.
662 If you would like to go back to using the original
\playerman{} software,
663 connect the
\dap{} to your computer, and follow the instructions to install
664 the bootloader, but when prompted by sansapatcher, enter
\texttt{u
} for uninstall,
665 instead of
\texttt{i
} for install. As in the installation, it may be necessary to
666 first put your
\dap{} into MSC mode.
670 To uninstall Rockbox and go back to using just the original Ipod software, connect
671 the
\dap{} to your computer and follow the instructions to install
672 the bootloader but, when prompted by ipodpatcher, enter
\texttt{u
} for uninstall
673 instead of
\texttt{i
} for install.
677 If you would like to go back to using the original
\playerman{} software,
678 connect the
\dap{} to your computer, download the original
\playername{}
679 firmware from the
\playerman{} website, and copy it to the
\fname{FIRMWARE
}
680 directory on your
\playername{}. Turn off the
\dap{}, remove the USB cable
681 and insert the charger. The original firmware will automatically be flashed.
685 If you want to remove the Rockbox bootloader, simply flash an unpatched
686 \playerman{} firmware. Be aware that doing so will also remove the bootloader
687 USB mode. As that mode can come in quite handy (especially if you experience
688 disk errors) it is recommended to keep the bootloader. It also
689 gives you the possibility of trying Rockbox anytime later by simply
690 installing the distribution files.
692 The Rockbox bootloader will automatically start the original firmware if
693 the
\fname{.rockbox
} directory has been deleted.
696 Although if you retain the Rockbox bootloader, you will need to hold the
697 \ButtonRec{} button each time you want to start the original firmware.
702 Copy an unmodified original firmware to your player and update it.
706 If you wish to clean up your disk, you may also wish to delete the
707 \fname{.rockbox
} directory and its contents.
708 \nopt{m5,x5
}{Turn the
\playerman{} off.
709 Turn the
\dap{} back on and the original
\playerman{} software will load.
}
713 If you wish to clean up your disk by deleting the
714 \fname{.rockbox
} directory and its contents, this must be done
715 before uninstalling the bootloader in the next step.
717 Before installation you should have downloaded a copy of the
\playerman{}
719 \url{http://www.tacp.toshiba.com/tacpassets-images/firmware/MESV12US.zip
}.
721 \item Extract
\fname{MES12US.iso
} from the
\fname{.zip
} downloaded above.
722 \item There are two files within
\fname{MES12US.iso
} called
723 \fname{Autorun.inf
} and
\fname{gbs
\_update\_1\_2\_us.exe
}. Extract them with
724 your favourite unzipping utility e.g.
7zip.
725 \item Connect your
\dap{} to your computer.
726 \item Extract
\fname{nk.bin
} from within
727 \fname{gbs
\_update\_1\_2\_us.exe
} using e.g.
7zip and copy it to the
150 MB
728 firmware partition of your
\dap{}.
729 \item Safely eject / unmount the USB drive, unplug the cable and restart.
732 \note{From Windows, you can also run
\fname{gbs
\_update\_1\_2\_us.exe
}
733 directly to restore your
\dap{}. This will format your
\dap{},
737 \section{Troubleshooting
}
740 \item[Bootloader install problems
]
741 If you have trouble installing the bootloader,
742 please ensure that you are either logged in as an administrator (Windows), or
743 you have root rights (Linux)
}
746 \item[Immediately loading original firmware.
]
747 If the original firmware is immediately
748 loaded without the Rockbox bootloader appearing first, then the Rockbox bootloader
749 has not been correctly installed. The original firmware update will only perform
750 the update if the filename is correct, including case. Make sure that the patched
751 Iriver firmware is called
\fname{.hex
}.
}
753 \nopt{h100,h300
}{\item[``File Not Found''
]}
754 \opt{h100,h300
}{\item[``-
1 error''
]}
756 \nopt{h100,h300
}{``File Not Found''
}\opt{h100,h300
}{``-
1 error''
} from the
757 bootloader, then the bootloader cannot find the Rockbox firmware. This is
758 usually a result of not extracting the contents of the
\fname{.zip
} file
759 to the proper location, and should not happen when Rockbox has been
760 installed with Rockbox Utility.
762 To fix this, either install Rockbox with the Rockbox Utility which will take care
763 of this for you, or recheck the Manual Install section to see where the files
768 If this does not fix the problem, there are two additional procedures that you
769 can try to solve this:
772 \item Formatting the storage partition. It is possible that using the
773 mkdosfs utility from Linux to format the data partition from your PC
774 before installing will resolve this problem. The appropriate format command is:
776 mkdosfs -f
2 -F
32 -S
512 -s
64 -v -n TFAT /path/to/partition/device
778 \warn{This will remove all your files.
}
780 \item Copying a
\fname{tar
}. If you have a Rockbox build environment
781 then you can try generating
\fname{rockbox.tar
} instead of
782 \fname{rockbox.zip
} as follows:
786 and copying it to the data partition. During the next boot, the bootloader