Use a special constant so that we don't have to care about the actual line numbers
[kugel-rb.git] / manual / getting_started / installation.tex
blob8447c4be154284a2f438032a179d7ba208eee0e2
1 % $Id$ %
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}{
15 \begin{description}
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}.
25 \opt{ipodvideo}{
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}.
31 \opt{c200}{
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.
39 \opt{e200,e200v2}{
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.
46 \opt{clipv1,clipv2}{
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.
53 \opt{fuze}{
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.
60 \opt{cowond2}{
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).}
67 \end{description}
70 \opt{cowond2}{
71 \begin{description}
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
75 supported target:
76 \begin{itemize}
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.\\}
89 \end{itemize}
90 \end{description}
92 \opt{h300}{
93 \begin{description}
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.
96 \end{description}
99 \opt{sansaAMS}{
100 \begin{description}
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
103 with DRM.
104 \end{description}
107 \nopt{gigabeats}{
108 \begin{description}
110 \nopt{ipod1g2g}{
111 \item[USB connection.]
113 \opt{ipod1g2g}{
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
122 name of your \dap{}.
124 \opt{ipod}{
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.
140 \opt{x5}{
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
144 sticks, etc.).
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
149 original firmware.}
151 \nopt{sansaAMS}{\warn{Never extract files to your \dap{} while it is in recovery mode.}}
153 \opt{h10,h10_5gb}{
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:
157 \begin{enumerate}
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.
165 \end{enumerate}
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{}.
175 \end{description}
178 \opt{ipod,sansa}{
179 \begin{description}
180 \item[Administrator/Root rights.] Installing the bootloader portion of Rockbox
181 requires you to have administrative (Windows) or root (Linux) rights.
182 Consequently when doing either the automatic or manual bootloader install,
183 please ensure that you are logged in with an administrator account or have root rights.
184 \end{description}
187 \opt{ipod}{
188 \begin{description}
189 \item[File system format.] Rockbox only works on Ipods formatted with
190 the FAT32 filesystem (i.e. Ipods initialised by Itunes
191 for Windows). It does not work with the HFS+ filesystem (i.e. Ipods
192 initialised by Itunes for the Mac). More information and instructions for
193 converting an Ipod to FAT32 can be found on the
194 \wikilink{IpodConversionToFAT32} wiki
195 page on the Rockbox website. Note that after conversion, you can still use
196 a FAT32 Ipod with a Mac.
197 \end{description}
200 \section{Installing Rockbox}\label{sec:installing_rockbox}\index{Installation}
201 There are two ways to install Rockbox: automated and manual. The automated
202 way is the preferred method of installing Rockbox for the majority of
203 people. Rockbox Utility is a graphical application that does almost everything
204 for you. However, should you encounter a problem, then the manual way is
205 still available to you.\\
207 \opt{gigabeats}{\note{The automated install is not yet available for the
208 \playerlongtype{}. For now you can use the manual method to install Rockbox.
209 Please still read the section on the automatic install as it explains
210 various important aspects of Rockbox, such as the different versions
211 available.\\}}
213 \opt{hwcodec}{Rockbox itself comes as a single package. There is no need
214 to install additional software to run Rockbox.}
215 \opt{swcodec} {
216 \opt{HAVE_RB_BL_ON_DISK}{There are three separate components,
217 two of which need to be installed in order to run Rockbox:}
218 \opt{HAVE_RB_BL_IN_FLASH}{There are two separate components
219 which need to be installed in order to run Rockbox:}
221 \begin{description}
222 \opt{HAVE_RB_BL_ON_DISK}{
223 \item[The \playerman{} bootloader.]
224 The \playerman{} bootloader is the program that tells your \dap{} how to load
225 and start the original firmware. It is also responsible for any emergency,
226 recovery, or disk modes on your \dap{}. This bootloader is stored in special flash
227 memory in your \playerman{} and comes factory-installed. It is not necessary
228 to modify this in order to install Rockbox.}
230 \item[The Rockbox bootloader.] \index{Bootloader}
231 \opt{HAVE_RB_BL_ON_DISK}{The Rockbox bootloader is loaded from disk by
232 the \playerman{} bootloader. It is responsible for loading the Rockbox
233 firmware and for providing the dual boot function. It directly replaces the
234 \playerman{} firmware in the \daps{} boot sequence.
235 \opt{gigabeatf}{\note{Dual boot does not currently work on the Gigabeat.}}}
237 \opt{HAVE_RB_BL_IN_FLASH}{
238 The bootloader is the program that tells your
239 \dap{} how to load and start other components of Rockbox and for providing
240 the dual boot function. This is the component of Rockbox that is installed
241 to the flash memory of your \playerman.
242 \opt{iaudio}{\note{Dual boot does not currently work on the \playertype{}.}}}
244 \item[The Rockbox firmware.]
245 \opt{HAVE_RB_BL_IN_FLASH}{Unlike the \playerman{} firmware, which runs
246 entirely from flash memory,}
247 \opt{HAVE_RB_BL_ON_DISK}{Similar to the \playerman{} firmware,}
248 most of the Rockbox code is contained in a
249 ``build'' that resides on your \daps{} drive. This makes it easy to
250 update Rockbox. The build consists of a directory called
251 \fname{.rockbox} which contains all of the Rockbox files, and is
252 located in the root of your \daps{} drive.
254 \end{description}
257 \nopt{player} {
258 Apart from the required parts there are some addons you might be interested
259 in installing.
260 \begin{description}
261 \item[Fonts.] Rockbox can load custom fonts. The fonts are
262 distributed as a separate package and thus need to be installed
263 separately. They are not required to run Rockbox itself but
264 a lot of themes require the fonts package to be installed.
266 \item[Themes.] The appearance of Rockbox can be customised by themes. Depending
267 on your taste you might want to install additional themes to change
268 the look of Rockbox.
269 \end{description}
272 \subsection{Automated Installation}
274 To automatically install Rockbox, download the official installer and
275 housekeeping tool \caps{Rockbox Utility}. It allows you to:
276 \begin{itemize}
277 \item Automatically install all needed components for using Rockbox
278 (``Minimal Installation'').
279 \item Automatically install all suggested components (``Complete Installation'').
280 \item Selectively install optional components.
281 \nopt{player}{\item Install additional fonts and themes.}
282 \item Install voice files and generate talk clips.
283 \item Uninstall all components you installed using Rockbox Utility.
284 \end{itemize}
286 Prebuilt binaries for Windows, Linux and Mac OS X are
287 available at the \wikilink{RockboxUtility} wiki page.\\
289 \opt{gigabeats,clipv1,clipv2,clipplus}{\note{Rockbox Utility does not currently support the
290 \playertype{} and you will therefore need to follow the manual install
291 instructions below.\\}}
293 When first starting \caps{Rockbox Utility} run ``Autodetect'',
294 found in the configuration dialog (File $\rightarrow$ Configure). Autodetection
295 can detect most player types. If autodetection fails or is unable to detect
296 the mountpoint, make sure to enter the correct values. The mountpoint indicates
297 the location of the \dap{} in your filesystem. On Windows, this is the drive
298 letter the \dap{} gets assigned, on other systems this is a path in the
299 filesystem.\\*
301 \opt{ipodvideo}
302 {\note{Autodetection is unable to distinguish between the
303 \playerman{} 30~GB and 60~GB / 80~GB models and defaults to the
304 30~GB model. This will usually work but you might want to check the
305 detected value, especially if you experience problems with Rockbox.}
308 \opt{h100,h300}{
309 Rockbox Utility will ask you for a compatible copy of the original
310 firmware. This is because for legal reasons we cannot distribute
311 the bootloader directly. Instead, we have to patch the Iriver firmware
312 with the Rockbox bootloader.
314 Download a supported version of the Iriver firmware for your
315 \playername{} from the Iriver website, links can be found on
316 \wikilink{IriverBoot}.
318 Supported Iriver firmware versions currently include
319 \opt{h100}{1.63US, 1.63EU, 1.63K, 1.65US, 1.65EU, 1.65K, 1.66US,
320 1.66EU and 1.66K. Note that the H140 uses the same firmware as the H120;
321 H120 and H140 owners should use the firmware called \fname{ihp\_120.hex}.
322 Likewise, the iHP110 and iHP115 use the same firmware, called
323 \fname{ihp\_100.hex}. Be sure to use the correct firmware file for
324 your player.}
325 \opt{h300}{1.28K, 1.28EU, 1.28J, 1.29K, 1.29J and 1.30EU.
326 \note{The US \playername{} firmware is not supported and cannot be
327 patched to be used with the bootloader. If you wish to install Rockbox
328 on a US \playername{}, you must first install a non-US version of the
329 original firmware and then install one of the supported versions patched
330 with the Rockbox bootloader.}
331 \warn{Installing a non-US firmware on a US \playername{} will
332 \emph{permanently} remove DRM support from the player.}}
334 If the file that you downloaded is a \fname{.zip} file, use an unzip
335 utility like mentioned in the prerequisites section to extract
336 the \fname{.hex} from the \fname{.zip} file
337 to your desktop. Likewise, if the file that you downloaded is an
338 \fname{.exe} file, double-click on the \fname{.exe} file to extract
339 the \fname{.hex} file to your desktop.
340 When running Linux you should be able to extract \fname{.exe}
341 files using \fname{unzip}.
344 \subsubsection{Choosing a Rockbox version}\label{sec:choosing_version}
346 There are three different versions of Rockbox available from the
347 Rockbox website:
348 \label{Version}
349 Release version, current build and archived daily build. You need to decide which one
350 you want to install and get the appropriate version for your \dap{}. If you
351 select either ``Minimal Installation'' or ``Complete Installation'' from the
352 ``Quick Start'' tab, then Rockbox Utility will automatically install the
353 release version of Rockbox. Using the ``Installation'' tab will allow you
354 to select which version you wish to install.
356 \begin{description}
358 \item[Release.] The release version is the latest stable release, free
359 of known critical bugs. For a manual install, the current stable release of Rockbox is
360 available at \url{http://www.rockbox.org/download/}.
362 \item[Current Build.] The current build is built at each source code change to
363 the Rockbox SVN repository and represents the current state of Rockbox
364 development. This means that the build could contain bugs but most of
365 the time is safe to use. For a manual install, you can download the current build from
366 \url{http://build.rockbox.org/}.
368 \item[Archived Build.] In addition to the release version and the current build,
369 there is also an archive of daily builds available for download. These are
370 built once a day from the latest source code in the SVN repository. For a manual install,
371 you can download archived builds from \url{http://www.rockbox.org/daily.shtml}.
373 \end{description}
375 \note{Because current and archived builds are development versions that
376 change frequently, they may behave differently than described in this manual,
377 or they may introduce new (and potentially annoying) bugs. Unless you wish to
378 try the latest and greatest features at the price of possibly greater instability,
379 or you wish to help with development, you should stick with the release.\\*}
381 Please now go to \reference{ref:finish_install} to complete the installation procedure.
383 \subsection{Manual Installation}
385 The manual installation method is still available to you, should you need or desire it
386 by following the instructions below. If you have used Rockbox Utility
387 to install Rockbox, then you do not need to follow the next section and can skip
388 straight to \reference{ref:finish_install}
390 \opt{gigabeats}{\subsubsection{Installing the bootloader}
391 \input{getting_started/gigabeats_install.tex}
394 \subsubsection{Installing the firmware}\label{sec:installing_firmware}
396 \opt{gigabeats}{\note{When your \dap{} is in the Rockbox USB or bootloader
397 USB mode, you will see two visible partitions - the 150MB firmware
398 partition (containing at least a file called \fname{nk.bin}) and
399 the main data partition. Rockbox \emph{must} be installed onto the main
400 data partiton.}}
402 \begin{enumerate}
403 \item Download your chosen version of Rockbox from the links in the
404 previous section.
405 \opt{ipodvideo}{\note{There are separate versions of Rockbox for the 30GB and
406 60GB/80GB models. You must ensure you download the correct version for your
407 \dap{}.}}
409 \item Connect your \dap{} to the computer via USB
410 \opt{sansa,sansaAMS,h10,h10_5gb}{ in MSC mode }
411 \opt{ipod3g,ipod4g,ipodmini,ipodcolor}{ or Firewire }as described in
412 the manual that came with your \dap{}.
414 \item Take the \fname{.zip} file that you downloaded and use
415 the ``Extract all'' command of your unzip program to extract
416 the files onto%
417 \opt{gigabeats}{the main data partition of }
418 \opt{cowond2}{either an SD card or the internal memory of }
419 your \dap{}.
420 \opt{cowond2}{\note{If you have chosen to extract to the internal memory, it
421 will not be possible to save settings.}}
422 \end{enumerate}
424 \note{The entire contents of the \fname{.zip} file should be extracted
425 directly to the root of your \daps{} drive. Do not try to
426 create a separate directory on your \dap{} for the Rockbox
427 files! The \fname{.zip} file already contains the internal
428 structure that Rockbox needs.\\}
430 \opt{archos}{
431 If the contents of the \fname{.zip} file are extracted correctly, you will
432 have a file called \fname{\firmwarefilename} in the main directory of your
433 \daps{} drive, and also a directory called \fname{.rockbox}, which contains a
434 number of other directories and system files needed by Rockbox.
437 % This has nothing to do with swcodec, just that these players need our own
438 % bootloader so we can decide where we want the main binary.
439 \opt{swcodec}{
440 If the contents of the \fname{.zip} file are extracted correctly, you will
441 have a directory called \fname{.rockbox}, which contains all the files needed
442 by Rockbox, in the main directory of your \daps{} drive.
445 \opt{swcodec}{\nopt{gigabeats}{
446 \subsubsection{Installing the bootloader}
447 \opt{h100,h300}{\input{getting_started/iriver_install.tex}}
448 \opt{ipod}{\input{getting_started/ipod_install.tex}}
449 \opt{m3,m5,x5}{\input{getting_started/iaudio_install.tex}}
450 \opt{h10,h10_5gb}{\input{getting_started/h10_install.tex}}
451 \opt{gigabeatf}{\input{getting_started/gigabeat_install.tex}}
452 \opt{sansa}{\input{getting_started/sansa_install.tex}}
453 \opt{sansaAMS}{\input{getting_started/sansaAMS_install.tex}}
454 \opt{mrobe100}{\input{getting_started/mrobe100_install.tex}}
455 \opt{cowond2}{\input{getting_started/cowond2_install.tex}}
458 \subsection{Finishing the install}\label{ref:finish_install}
460 \opt{gigabeatf}{
461 After installing you \emph{need} to power-cycle the
462 \dap{} by doing the following steps. Failure to do so may result in problems.
463 \begin{itemize}
464 \item Safely eject / unmount your \dap{} and unplug the USB cable.
465 \item Unplug any power adapter.
466 \item Hold the \ButtonPower{} button to turn off the \dap{}.
467 \item Slide the battery switch located on the bottom of the \dap{} from
468 `on' to `off'.
469 \item Slide the battery switch back from `off' to `on'.
470 \end{itemize}
473 \opt{m3,m5,x5}{
474 After installing you \emph{need} to power-cycle the
475 \dap{} by doing the following steps.
476 \begin{itemize}
477 \item Safely eject / unmount your \dap{} and unplug the USB cable.
478 \item Hold the
479 \opt{IAUDIO_X5_PAD}{\ButtonPower}
480 \opt{IAUDIO_M3_PAD}{\ButtonPlay}
481 button to turn off the \dap{}.
482 \item Insert the charger. The Rockbox bootloader will automatically be flashed.
483 \end{itemize}
486 \opt{h10,h10_5gb,ipod,mrobe100,sansa,archos,sansaAMS,cowond2}{
487 Safely eject / unmount the USB drive, unplug the cable and restart.
490 \opt{gigabeats}{
491 Safely eject / unmount your \dap{}.
494 \opt{h100,h300}{
495 \begin{itemize}
496 \item Safely eject / unmount your \dap{}.
498 \item \warn{Before proceeding further, make sure that your player has a full charge
499 or that it is connected to the power adaptor. Interrupting the next step
500 due to a power failure most likely will brick your \dap{}.}
501 Update your \daps{} firmware with the patched bootloader. To do this, turn
502 the jukebox on. Press and hold the \ButtonSelect{} button to enter the main menu,
503 and navigate to \setting{General $\rightarrow$ Firmware Upgrade}. Select
504 \setting{Yes} when asked to confirm if you want to upgrade the
505 firmware. The \playerman{} will display a message indicating that the
506 firmware update is in progress. Do \emph{not} interrupt this process. When the
507 firmware update is complete the player will turn itself off. (The update
508 firmware process usually takes a minute or so.). You are now ready to go.
509 \end{itemize}
512 \opt{e200}{Your e200 will automatically reboot and Rockbox should load.}
516 \subsection{Enabling Speech Support (optional)}\label{sec:enabling_speech_support}
517 \index{Speech}\index{Installation!Optional Steps}
518 If you wish to use speech support you will also need a voice file. Voice files
519 allow Rockbox to speak the user interface to you. Rockbox Utility can install
520 an English voice file, or you can download it from \url{http://www.rockbox.org/daily.shtml}
521 and unzip it to the root of your \dap{}.
522 Rockbox Utility can also aid you in the creation of voice files with different voices
523 or in other languages if you have a suitable speech engine installed on your computer.
524 Voice menus are enabled by default and will come
525 into effect after a reboot. See \reference{ref:Voiceconfiguration} for details
526 on voice settings.
527 Rockbox Utility can also aid in the production of talk files, which allow Rockbox
528 to speak file and folder names.
530 \section{Running Rockbox}
531 \nopt{ipod,gigabeats,cowond2}{When
532 you turn the unit on, Rockbox should load.}
533 \opt{ipod}{Hard reset the Ipod by holding
534 \opt{IPOD_4G_PAD}{\ButtonMenu{} and \ButtonSelect{} simultaneously}%
535 \opt{IPOD_3G_PAD}{\ButtonMenu{} and \ButtonPlay{} simultaneously}
536 for a couple of seconds until the \dap{} resets. Now Rockbox should load.
539 \opt{gigabeats}{Rockbox should automatically load when you turn on your player.\\
541 \note{
542 If you have loaded music onto your \dap{} using the \playerman{}
543 firmware, you will not be able to see your music properly in the
544 \setting{File Browser} as MTP mode changes the location and file names.
545 Files placed on your \dap{} using the \playerman{} firmware can be
546 viewed by initialising and using Rockbox's database.
547 See \reference{ref:database} for more information.}
550 \opt{cowond2}{
551 To boot the Rockbox firmware set the \ButtonHold{} switch immediately after
552 power on.\\
553 \note{If you have chosen to install to an SD card and it is inserted at power
554 on, Rockbox will boot from that card and use it as the primary drive for
555 storing settings, etc. If there is no SD card inserted, Rockbox will boot
556 from the internal memory, and it will not be possible to save settings.}
559 \opt{ipod}{
560 \note{
561 If you have loaded music onto your \dap{} using Itunes,
562 you will not be able to see your music properly in the \setting{File Browser}.
563 This is because Itunes changes your files' names and hides them in
564 directories in the \fname{Ipod\_Control} directory. Files placed on your
565 \dap{} using Itunes can be viewed by initialising and using Rockbox's database.
566 See \reference{ref:database} for more information.
570 \opt{m3}{
571 \fixme{Add a note about the charging trick and place it here?}
574 \section{Updating Rockbox}
575 Rockbox can be easily updated with Rockbox Utility.
576 You can also update Rockbox manually -- download a Rockbox build
577 as detailed above, and unzip the build to the root directory
578 of your \dap{} as in the manual installation stage. If your unzip
579 program asks you whether to overwrite files, choose the ``Yes to all'' option.
580 The new build will be installed over your current build.\\
582 \opt{gigabeats}{
583 \note{When your \dap{} is in the Rockbox USB or bootloader
584 USB mode, you will see two visible partitions, the 150MB firmware
585 partition (containing at least a file called \fname{nk.bin}) and
586 the main data partition. Rockbox \emph{must} be installed onto the main
587 data partiton.\\}
590 \nopt{hwcodec}{
591 The bootloader only changes rarely, and should not normally
592 need to be updated.\\
595 \note{If you use Rockbox Utility be aware that it cannot detect manually
596 installed components.}
598 \section{Uninstalling Rockbox}\index{Installation!uninstall}
600 \nopt{gigabeatf,m5,x5,archos,mrobe100,gigabeats}{
601 \note{The Rockbox bootloader allows you to choose between Rockbox and
602 the original firmware. (See \reference{ref:Dualboot} for more information.)}
605 \subsection{Automatic Uninstallation}
606 \opt{gigabeats}{\note{Rockbox can only be uninstalled manually for now.}}
608 You can uninstall Rockbox automatically by using Rockbox Utility. If you
609 installed Rockbox manually you can still use Rockbox Utility for uninstallation
610 but will not be able to do this selectively.
612 \opt{h100,h300}{\note{Rockbox Utility cannot uninstall the bootloader due to
613 the fact that it requires a flashing procedure. To uninstall the bootloader
614 completely follow the manual uninstallation instructions below.}}
616 \subsection{Manual Uninstallation}
618 \opt{archos}{
619 If you would like to go back to using the original \playerman{} software,
620 connect the \dap{} to your computer, and delete the
621 \fname{\firmwarefilename} file.
624 \opt{h10,h10_5gb}{
625 If you would like to go back to using the original \playerman{} software,
626 connect the \dap{} to your computer, and delete the
627 \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}} file and rename
628 \fname{OF.mi4} to \opt{h10}{\fname{H10\_20GC.mi4}}\opt{h10_5gb}{\fname{H10.mi4}}
629 in the \fname{System} directory on your \playertype{}. As in the installation,
630 it may be necessary to first put your device into UMS mode.
633 \opt{mrobe100}{
634 If you would like to go back to using the original \playerman{} software,
635 connect the \dap{} to your computer, and delete the
636 \fname{pp5020.mi4} file and rename
637 \fname{OF.mi4} to \fname{pp5020.mi4}
638 in the \fname{System} directory on your \playertype{}.
641 \opt{e200}{
642 If you would like to go back to using the original \playerman{} software,
643 connect the \dap{} to your computer, and follow the instructions to install
644 the bootloader, but when prompted by sansapatcher, enter \texttt{u} for uninstall,
645 instead of \texttt{i} for install. As in the installation, it may be necessary to
646 first put your \dap{} into MSC mode.
649 \optv{ipod}{
650 To uninstall Rockbox and go back to using just the original Ipod software, connect
651 the \dap{} to your computer and follow the instructions to install
652 the bootloader but, when prompted by ipodpatcher, enter \texttt{u} for uninstall
653 instead of \texttt{i} for install.
656 \opt{m5,x5}{
657 If you would like to go back to using the original \playerman{} software,
658 connect the \dap{} to your computer, download the original \playername{}
659 firmware from the \playerman{} website, and copy it to the \fname{FIRMWARE}
660 directory on your \playername{}. Turn off the \dap{}, remove the USB cable
661 and insert the charger. The original firmware will automatically be flashed.
664 \opt{h100,h300}{
665 If you want to remove the Rockbox bootloader, simply flash an unpatched
666 \playerman{} firmware. Be aware that doing so will also remove the bootloader
667 USB mode. As that mode can come in quite handy (especially if you experience
668 disk errors) it is recommended to keep the bootloader. It also
669 gives you the possibility of trying Rockbox anytime later by simply
670 installing the distribution files.
671 \opt{h100}{
672 The Rockbox bootloader will automatically start the original firmware if
673 the \fname{.rockbox} directory has been deleted.
675 \opt{h300}{
676 Although if you retain the Rockbox bootloader, you will need to hold the
677 \ButtonRec{} button each time you want to start the original firmware.
681 \opt{sansaAMS}{
682 Copy an unmodified original firmware to your player and update it.
685 \nopt{gigabeats}{
686 If you wish to clean up your disk, you may also wish to delete the
687 \fname{.rockbox} directory and its contents.
688 \nopt{m5,x5}{Turn the \playerman{} off.
689 Turn the \dap{} back on and the original \playerman{} software will load.}
692 \opt{gigabeats}{
693 If you wish to clean up your disk by deleting the
694 \fname{.rockbox} directory and its contents, this must be done
695 before uninstalling the bootloader in the next step.
697 Before installation you should have downloaded a copy of the \playerman{}
698 firmware from
699 \url{http://www.tacp.toshiba.com/tacpassets-images/firmware/MESV12US.zip}.
700 \begin{itemize}
701 \item Extract \fname{MES12US.iso} from the \fname{.zip} downloaded above.
702 \item There are two files within \fname{MES12US.iso} called
703 \fname{Autorun.inf} and \fname{gbs\_update\_1\_2\_us.exe}. Extract them with
704 your favourite unzipping utility e.g. 7zip.
705 \item Connect your \dap{} to your computer.
706 \item Extract \fname{nk.bin} from within
707 \fname{gbs\_update\_1\_2\_us.exe} using e.g. 7zip and copy it to the 150 MB
708 firmware partition of your \dap{}.
709 \item Safely eject / unmount the USB drive, unplug the cable and restart.
710 \end{itemize}
712 \note{From Windows, you can also run \fname{gbs\_update\_1\_2\_us.exe}
713 directly to restore your \dap{}. This will format your \dap{},
714 removing all files.}
717 \section{Troubleshooting}
718 \begin{description}
719 \opt{sansa,ipod}{
720 \item[Bootloader install problems]
721 If you have trouble installing the bootloader,
722 please ensure that you are either logged in as an administrator (Windows), or
723 you have root rights (Linux)}
725 \opt{h100,h300}{
726 \item[Immediately loading original firmware.]
727 If the original firmware is immediately
728 loaded without the Rockbox bootloader appearing first, then the Rockbox bootloader
729 has not been correctly installed. The original firmware update will only perform
730 the update if the filename is correct, including case. Make sure that the patched
731 Iriver firmware is called \fname{.hex}.}
733 \nopt{h100,h300}{\item[``File Not Found'']}
734 \opt{h100,h300}{\item[``-1 error'']}
735 If you receive a
736 \nopt{h100,h300}{``File Not Found''}\opt{h100,h300}{``-1 error''} from the
737 bootloader, then the bootloader cannot find the Rockbox firmware. This is
738 usually a result of not extracting the contents of the \fname{.zip} file
739 to the proper location, and should not happen when Rockbox has been
740 installed with Rockbox Utility.
742 To fix this, either install Rockbox with the Rockbox Utility which will take care
743 of this for you, or recheck the Manual Install section to see where the files
744 need to be located.
745 \end{description}
747 \optv{gigabeats}{
748 If this does not fix the problem, there are two additional procedures that you
749 can try to solve this:
751 \begin{itemize}
752 \item Formatting the storage partition. It is possible that using the
753 mkdosfs utility from Linux to format the data partition from your PC
754 before installing will resolve this problem. The appropriate format command is:
755 \begin{code}
756 mkdosfs -f 2 -F 32 -S 512 -s 64 -v -n TFAT /path/to/partition/device
757 \end{code}
758 \warn{This will remove all your files.}
760 \item Copying a \fname{tar}. If you have a Rockbox build environment
761 then you can try generating \fname{rockbox.tar} instead of
762 \fname{rockbox.zip} as follows:
763 \begin{code}
764 make tar
765 \end{code}
766 and copying it to the data partition. During the next boot, the bootloader
767 will extract it.
768 \end{itemize}