Colour targets: Revert an optimisation from almost 18 months ago that actually turned...
[Rockbox.git] / manual / getting_started / installation.tex
blob9cff4819f8a3a621799c0a561588d41d21878007
1 % $Id$ %
2 \chapter{Installation}\label{sec:installation}
4 \opt{ipodnano}{
5 \note{Rockbox presently runs only on the original Ipod Nano. Rockbox does
6 \emph{not} run on the newer, second generation Ipod Nano (the all aluminium
7 version). For information on identifying which Ipod you own, see this page on
8 Apple's website: \url{http://www.info.apple.com/kbnum/n61688}.
11 \opt{ipodvideo}{
12 \note{Rockbox presently runs only on the 5th and 5.5th generation Ipod videos.
13 Rockbox does \emph{not} run on the newer, 6th/Classic generation Ipod.
14 For information on identifying which Ipod you own, see this page on Apple's
15 website: \url{http://www.info.apple.com/kbnum/n61688}.
18 \opt{e200,c200}{
19 \note{Rockbox doesn't function on the newer v2 models. They can be identified
20 by checking the Sandisk firmware version number under
21 Settings $\rightarrow$ Info. The v1
22 firmware is named 01.xx.xx, while the v2 firmware begins with 03.}
25 \section{Overview}
26 There are two ways of installing Rockbox: automated and manual. While the
27 manual way is older, more tested and proven to work correctly, the
28 automated installation is based on a nice graphical application that does
29 almost everything for you. It is still important that you have
30 an overview of the installation process to be able to select the correct
31 installation options.
33 \opt{MASCODEC}{Rockbox itself comes as a single package. There is no need
34 to install additional software for running Rockbox.}
35 \opt{swcodec} {
36 \opt{HAVE_RB_BL_ON_DISK}{There are three separate components,
37 two of which need to be installed in order to run Rockbox.}
38 \opt{HAVE_RB_BL_IN_FLASH}{There are two separate components of Rockbox
39 that need to be installed in order to run Rockbox.}
41 \begin{description}
42 \opt{HAVE_RB_BL_ON_DISK}{
43 \item[The \playerman{} bootloader.]
44 The \playerman{} bootloader is the program that tells your \dap{} how to boot
45 and load the firmware from disk. It is also responsible for the
46 disk mode on your \dap{}.
48 This bootloader is stored in special flash memory in your \playerman{}.
49 It is already installed on your \dap{}, so it is never necessary to modify
50 this in order to install Rockbox.}
52 \item[The Rockbox bootloader.] \index{Bootloader}
53 \opt{HAVE_RB_BL_ON_DISK}{The Rockbox bootloader is loaded from disk by
54 the \playerman{} bootloader. It is responsible for loading the Rockbox
55 firmware and for providing the dual boot function. It directly replaces the
56 \playerman{} firmware in the \daps{} boot sequence.
57 \opt{gigabeatf}{\note{Dual boot does not currently work on the Gigabeat.}}}
59 \opt{HAVE_RB_BL_IN_FLASH}{
60 The bootloader is the program that tells your
61 \dap{} how to boot and load other components of Rockbox. This is the
62 component of Rockbox that is installed to the flash memory of your
63 \playerman.}
65 \item[The Rockbox firmware.]
66 \opt{HAVE_RB_BL_IN_FLASH}{Unlike the \playerman{} firmware, which runs
67 entirely from flash memory,}
68 \opt{HAVE_RB_BL_ON_DISK}{Similar to the \playerman{} firmware,}
69 most of the Rockbox code is contained in a
70 ``build'' that resides on your \daps{} drive. This makes it easy to
71 update Rockbox. The build consists of a directory called
72 \fname{.rockbox} which contains all of the Rockbox files, and is
73 located in the root of your \daps{} drive.
75 \end{description}
78 \nopt{player} {
79 Apart from the required parts there are some addons you might be interested
80 in installing too.
81 \begin{description}
82 \item[Fonts.] Rockbox can load custom fonts. The fonts are
83 distributed as separate package and thus needs to be installed
84 separately. They are not required to run Rockbox itself but
85 a lot of themes require the fonts package to be installed.
87 \item[Themes.] The view of Rockbox can be customized by themes. Depending
88 on your taste you might want to install additional themes to change
89 the look of Rockbox.
90 \end{description}
93 \section{Prerequisites}\label{sec:prerequisites}
94 \index{Installation!Prerequisites}
95 Before installing Rockbox you should make sure you meet the prerequisites.
96 You may need some additional tools for installation. In most cases these will be
97 already available on your computer but if not you need to get some additional
98 software.
100 \begin{description}
101 \item[USB connection.] To transfer Rockbox to your \dap{} you need to
102 connect it to your computer. For manual installation/uninstallation, or
103 should autodetection fail during automatic installation, you need to know
104 where to access the \dap{}. On Windows this means you need to figure out
105 the drive letter associated with the \dap{}. On Linux you need to know the
106 mount point of your \dap{}.
108 \opt{ipod}{
109 Your \dap{} should enter disk mode automatically when connected to a
110 computer via USB. If your computer does not recognise your \dap{}, you may
111 need to enter the disk mode manually. Disconnect your \dap{} from the
112 computer. Hard reset the \dap{} by pressing and holding the \ButtonMenu{} and
113 \ButtonSelect{} buttons simultaneously. As soon as the \dap{} resets, press
114 and hold the \ButtonSelect{} and \ButtonPlay{} buttons simultaneously. Your
115 \dap{} should enter disk mode and you can try reconnecting to the computer.
118 \opt{ipod3g,ipod4g,ipodcolor,ipodmini}{
119 \note{\index{Firewire}Firewire detection is not supported in Rockbox at
120 the moment. Please use USB only.}
122 \opt{x5}{
123 \note{When instructed to connect/disconnect the USB cable, always use
124 the USB port through the subpack, not the side 'USB Host' port! The side port
125 is intended to be used for USB OTG connections only (digital cameras, memory
126 sticks, etc)!}
129 \opt{sansa}{\warn{The following steps require you to change the setting in
130 \setting{Settings $\rightarrow$ USB Mode} to \setting{MSC} from within the
131 original firmware. Never extract files to your \dap{} while it is in
132 recovery mode.}}
133 \opt{h10,h10_5gb}{\warn{The following steps require you to use UMS mode and so
134 may require use of the UMS trick as described in the bootloader installation
135 section.}}
136 \opt{gigabeatf}{\warn{During installation, do not connect your \dap{}
137 using the cradle but plug the USB cable directly to the \dap{}.}}
138 \end{description}
139 For manual installation and customization additional software is required.
140 \begin{description}
141 \item[ZIP utility.]\index{zip}
142 Rockbox is distributed as a compressed archive using the
143 \fname{.zip} format, so you'll need a tool which can open it.
144 Usually your computer will have a tool already installed that can
145 do this. Windows XP has built-in support for
146 \fname{.zip} files and presents them to you as directories unless you have
147 installed a third party program that handles compressed files. For
148 other operating systems this may vary. If the \fname{.zip} file format
149 is not recognised on your computer you can find a program to handle them
150 at \url{http://www.info-zip.org/} or \url{http://sevenzip.sf.net/}, both of
151 which can be downloaded and used free of charge.
152 \item[Text editor.] As you will see in the following chapters, Rockbox is
153 highly configurable. In addition to saving configurations,
154 Rockbox also allows you to create customised configuration files. If you
155 would like to edit custom configuration files on your computer, you will
156 need a text editor like Windows' ``Wordpad''.
157 \end{description}
159 \opt{ipod}{
160 \note{In addition to the requirements described above, Rockbox only works on
161 Ipods formatted with the FAT32 filesystem (i.e. Ipods initialized by iTunes
162 for Windows). It does not work with the HFS+ filesystem (i.e. Ipods
163 initialized by iTunes for the Mac). More information and instructions for
164 converting an Ipod to FAT32 can be found on the
165 \wikilink{IpodConversionToFAT32} wiki
166 page on the Rockbox website. Note that after conversion, you can still use
167 a FAT32 Ipod on a Mac.
171 \section{Installing Rockbox}\label{sec:installing_rockbox}\index{Installation}
173 \opt{ipodvideo}{\warn{There are separate versions of Rockbox for the 30GB and
174 60GB/80GB models. You must ensure you download the correct version for your
175 \dap{}.}}
177 \subsection{Automated Installation}
179 \opt{mrobe100}{\fixme{NOTE: The m:robe 100 is only supported in rbutil version
180 1.05 or greater which may not be available on the download site yet.}}
182 To automatically install Rockbox, download the official installer and
183 housekeeping tool \textsc{Rockbox Utility}. It allows you to
184 \begin{itemize}
185 \item Automatically install all needed components for using Rockbox
186 (``Small Installation'')
187 \item Automatically install all suggested components (``Full Installation'')
188 \item Selectively install optional components
189 \item Install additional themes
190 \item Install voice files and generate talk clips
191 \item Uninstall all components you installed using Rockbox Utility
192 \end{itemize}
193 Prebuilt binaries for Windows, Linux and MacOS~X are
194 available at the \wikilink{RockboxUtility} wiki page.
196 \warn{When first starting \textsc{Rockbox Utility} run ``Autodetect'',
197 found in the configuration dialog (File $\rightarrow$ Configure). Autodetection
198 can detect most player types. If autodetection fails or is unable to detect
199 the mountpoint, make sure to enter the correct values. The mountpoint indicates
200 the location of the \dap{} in your filesystem. On Windows, this is the drive
201 letter the \dap{} gets assigned, on other systems this is a path in the
202 filesystem.}
204 \opt{ipodvideo}
205 {\warn{Autodetection is unable to distinguish between the
206 \playerman{} 30~GB and 60~GB / 80~GB models and defaults to the
207 30~GB model. This will usually work but you might want to check the
208 detected value, especially if you experience problems with Rockbox.}
211 \note{Rockbox Utility currently lacks some guiding messages. Please have a
212 look at the manual installation instructions if you are stuck
213 during installation.}
215 \subsection{Manual Installation}
217 \subsubsection{Choosing a Rockbox version}\label{sec:choosing_version}
219 There are three different types of firmware binaries available from the
220 Rockbox website:
221 \label{Version}
222 Release version, current build and daily build. You need to decide which one
223 you want to install and get the appropriate version for your \dap{}.
225 \begin{description}
227 \item[Release.]
228 \opt{archos}{The release version is the latest stable release, free
229 of known critical bugs. The current stable release of Rockbox, version
230 2.5, is available at \url{http://www.rockbox.org/download/}.
232 \opt{swcodec}{
233 There has not yet been a stable release for the \playername{}. Until
234 there is one, use a current build.
237 \item[Current Build.] The current build is built at each source code change to
238 the Rockbox SVN repository and represents the current state of Rockbox
239 development. This means that the build could contain bugs but most of
240 the time is safe to use. You can download the current build from
241 \url{http://build.rockbox.org/}.
243 \item[Archived Build.] In addition to the release version and the current build,
244 there is also an archive of daily builds available for download. These are
245 built once a day from the latest source code in the SVN repository. You can
246 download archived builds from \url{http://www.rockbox.org/daily.shtml}.
248 \end{description}
250 \warn{Because current builds and daily builds are development versions which
251 change frequently, they may behave differently than described in this manual,
252 or they may introduce new (and maybe annoying) bugs. If you do not want to
253 get undefined behaviour from your \dap{}, you should stick to the current
254 stable release if there is one for your \dap{}. If you want to help with
255 project development, you can try development builds and help by reporting bugs.
256 Just be aware that these are development builds that are highly functional
257 but not perfect!}
259 \subsubsection{Installing the firmware}\label{sec:installing_firmware}
261 \begin{enumerate}
263 \item Download your chosen version of Rockbox from the links in the
264 previous section.
266 \item Connect your \dap{} to the computer via USB
267 \opt{ipod3g,ipod4g,ipodmini,ipodcolor}{ or Firewire} as described in
268 the manual that came with your \dap{}.
270 \item Take the \fname{.zip} file that you downloaded and use
271 the ``Extract all'' command of your unzip program to extract
272 the files onto your \dap{}.
274 \note{The entire contents of the \fname{.zip} file should be extracted
275 directly to the root of your \daps{} drive. Do not try to
276 create a separate directory on your \dap{} for the Rockbox
277 files! The \fname{.zip} file already contains the internal
278 structure that Rockbox needs.}
280 \end{enumerate}
282 \opt{archos}{
283 \note{
284 If the contents of the \fname{.zip} file are extracted correctly, you will
285 have a file called \fname{\firmwarefilename} in the main directory of your
286 \daps{} drive, and also a directory called \fname{.rockbox}, which contains a
287 number of other directories and system files needed by Rockbox. If you receive a
288 ``-1'' error when you start Rockbox, you have not extracted the contents of
289 the \fname{.zip} file to the proper location.
293 % This has nothing to do with swcodec, just that these players need our own
294 % bootloader so we can decide where we want the main binary.
295 \opt{swcodec}{
296 \note{
297 If the contents of the \fname{.zip} file are extracted correctly, you will
298 have a directory called \fname{.rockbox}, which contains all the files needed
299 by Rockbox, in the main directory of your \daps{} drive. If you receive a
300 ``-1'' error when you start Rockbox, you have not extracted the contents of
301 the \fname{.zip} file to the proper location.
305 \nopt{player}{
306 \subsubsection{Installing the fonts package}{\index{Installation!Fonts}\label{sec:installing_fonts}
307 Rockbox has a fonts package that is available at
308 \url{http://www.rockbox.org/daily.shtml} or from the \emph{extras} link in
309 the menu on the Rockbox website. While the current builds and
310 daily builds change frequently, the fonts package rarely changes and is
311 therefore not included in these builds. When installing Rockbox for the first
312 time, you should install the fonts package. The release version, on the other hand,
313 does not change, so fonts are included with it.
315 \begin{enumerate}
317 \item Download the fonts package from the link above.
319 \item Take the file that you downloaded above, and use the ``Extract
320 all'' command of your unzip program to extract the files in the
321 \fname{.zip} file onto your \dap{}. As with the firmware installation, the
322 entire contents of the fonts \fname{.zip} should be extracted directly to the
323 root of your \daps{} drive. Do not try to create a separate directory
324 on your \dap{} for the fonts! The \fname{.zip} already contains the
325 correct internal structure.
327 \end{enumerate}
331 \opt{swcodec}{
332 \subsubsection{Installing the bootloader}
333 \opt{h1xx,h300}{\input{getting_started/iriver_install.tex}}
334 \opt{ipod}{\input{getting_started/ipod_install.tex}}
335 \opt{m5,x5}{\input{getting_started/iaudio_install.tex}}
336 \opt{h10,h10_5gb}{\input{getting_started/h10_install.tex}}
337 \opt{gigabeatf}{\input{getting_started/gigabeat_install.tex}}
338 \opt{sansa}{\input{getting_started/sansa_install.tex}}
339 \opt{mrobe100}{\input{getting_started/mrobe100_install.tex}}
340 \opt{gigabeats}{\input{getting_started/gigabeats_install.tex}}
343 \subsection{Enabling Speech Support (optional)}\label{sec:enabling_speech_support}
344 \index{Speech}\index{Installation!Optional Steps}
345 If you wish to use speech support you will also need a voice file, English ones
346 are available from \url{http://www.rockbox.org/daily.shtml}. Download the
347 ``voice'' package for your player and unzip it directly to the root of your \dap.
348 You should now find an \fname{english.voice} in the \fname{/.rockbox/langs}
349 directory on your \dap{}. Voice menus are enabled by default and will come
350 into effect after a reboot. See \reference{ref:Voiceconfiguration} for details
351 on voice settings.
353 \section{Running Rockbox}
354 Remove your \dap{} from the computer's USB port. %
355 \nopt{ipod,e200}{Unplug any connected power supply and turn the unit off. When
356 you next turn the unit on, Rockbox should load. }%
357 \opt{ipod}{Hard resetting the Ipod by holding
358 \opt{IPOD_4G_PAD}{\ButtonMenu{}+\ButtonSelect{}}%
359 \opt{IPOD_3G_PAD}{\ButtonMenu{}+\ButtonPlay{}}
360 for a couple of seconds until the \dap{} resets. Now Rockbox should load.
362 \opt{e200}{Your e200 will automatically reboot and Rockbox should load. }%
363 When you see the Rockbox splash screen, Rockbox is loaded and ready for
364 use.
366 \opt{ipod}{
367 \note{
368 If you have loaded music onto your \dap{} using Itunes,
369 you will not be able to see your music properly in the \setting{File Browser}.
370 This is because Itunes changes your files' names and hides them in
371 directories in the \fname{Ipod\_Control} directory. Files placed on your
372 \dap{} using Itunes can be viewed by initializing and using Rockbox's database.
373 See \reference{ref:database} for more information.
377 \section{Updating Rockbox}
378 Updating Rockbox is easy even if you do not use the Rockbox Utility.
379 Download a Rockbox build.
380 (The latest release of the Rockbox software will always be available from
381 \url{http://www.rockbox.org/download/}). Unzip the build to the root directory
382 of your \dap{} like you did in the installation stage. If your unzip
383 program asks you whether to overwrite files, choose the ``Yes to all'' option.
384 The new build will be installed over your current build.
386 \note{If you use Rockbox Utility be aware that it cannot detect manually
387 installed components.}
389 \section{Uninstalling Rockbox}\index{Installation!uninstall}
391 \nopt{gigabeatf,m5,x5,archos,mrobe100}{
392 \note{The Rockbox bootloader allows you to choose between Rockbox and
393 the original firmware. (See \reference{ref:Dualboot} for more information.)}
396 \subsection{Automatic Uninstallation}
397 You can uninstall Rockbox automatically by using Rockbox Utility. If you
398 installed Rockbox manually you can still use Rockbox Utility for uninstallation
399 but will not be able to do this selectively.
401 \opt{h1xx,h300}{\note{Rockbox Utility cannot uninstall the bootloader due to
402 the fact that it requires a flashing procedure. To uninstall the bootloader
403 completely follow the manual uninstallation instructions below.}}
405 \subsection{Manual Uninstallation}
407 \opt{archos}{
408 If you would like to go back to using the original \playerman{} software,
409 connect the \dap{} to your computer, and delete the
410 \fname{\firmwarefilename} file.
413 \opt{h10,h10_5gb}{
414 If you would like to go back to using the original \playerman{} software,
415 connect the \dap{} to your computer, and delete the
416 \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} file and rename
417 \fname{OF.mi4} to \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}}
418 in the \fname{System} directory on your \playertype{}. As in the installation,
419 it may be necessary to first put your device into UMS mode.
422 \opt{mrobe100}{
423 If you would like to go back to using the original \playerman{} software,
424 connect the \dap{} to your computer, and delete the
425 \fname{pp5020.mi4} file and rename
426 \fname{OF.mi4} to \fname{pp5020.mi4}
427 in the \fname{System} directory on your \playertype{}.
430 \opt{e200}{
431 If you would like to go back to using the original \playerman{} software,
432 connect the \dap{} to your computer, and follow the instructions to install
433 the bootloader, but when prompted by sansapatcher, enter \texttt{u} for uninstall,
434 instead of \texttt{i} for install. As in the installation, it may be necessary to
435 first put your device into UMS mode.
438 \optv{ipod}{
439 To uninstall Rockbox and go back to using just the original Ipod software, connect
440 the \dap{} to your computer and follow the instructions to install
441 the bootloader but, when prompted by ipodpatcher, enter \texttt{u} for uninstall
442 instead of \texttt{i} for install.
445 \opt{m5,x5}{
446 If you would like to go back to using the original \playerman{} software,
447 connect the \dap{} to your computer, download the original \playername{}
448 firmware from the \playerman{} website. And copy it to the \fname{FIRMWARE}
449 directory on your \playername{}. Turn off the \dap{}, remove the USB cable
450 and insert the charger. The original firmware will automatically be flashed.
453 \opt{h1xx,h300}{
454 \note{
455 If you want to remove the Rockbox bootloader, simply flash an unpatched
456 \playerman{} firmware. Be aware that doing so will also remove the bootloader
457 USB mode. As that mode can come in quite handy (especially when
458 having disk errors) it is recommended to keep the bootloader. It also
459 gives you the possibility of trying Rockbox anytime later by simply
460 installing the distribution files.
461 \opt{h1xx}{
462 The Rockbox bootloader will automatically start the original firmware if
463 the \fname{.rockbox} directory has been deleted.
465 \opt{h300}{%
466 Although if you retain the Rockbox bootloader, you will need to hold the
467 \ButtonRec{} button each time you want to start the original firmware.
472 If you wish to clean up your disk, you may also wish to delete the
473 \fname{.rockbox} directory and its contents.
474 \nopt{m5,x5}{Turn the \playerman{} off.
475 Turn the \dap{} back on and the original \playerman{} software will load.