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,c200v2,e200v2,clipv1,clipv2,cowond2,fuze,fuzev2
}{
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
}.
31 \opt{c200,c200v2,e200,e200v2
}{
32 The
\playertype{} is available in multiple versions, and you need to make
33 sure which you have by checking the Sandisk firmware version number under
34 Settings $
\rightarrow$ Info. The v1 firmware is named
01.xx.xx, while the
35 v2 firmware begins with
03. Make sure that you are following the
36 instructions from the correct manual.
38 \opt{clipv1,clipv2,fuze,fuzev2
}{
39 The
\playertype{} is available in multiple versions, and you need to make
40 sure which you have by checking the Sandisk firmware version number under
41 Settings $
\rightarrow$
\opt{fuze,fuzev2
}{System Settings $
\rightarrow$
}
42 Info. The v1 firmware is named
01.xx.xx, while the v2 firmware begins with
43 02. Make sure that you are following the instructions from the correct
47 Rockbox runs on all
\playerman{} \playertype{} and
\playertype{}+ variants
48 (
2 /
4 /
8 /
16~GB, with or without DAB/DMB).
49 \note{Newer
\playertype{}+ hardware revisions use an updated power
50 management chip, and some functionality is not yet implemented on these
51 players (e.g. touchscreen support).
}
58 \item[Current limitations.
] Most Rockbox functions are usable on the
59 \playertype{}/
\playertype{}+, including music playback and most plugins, but
60 there are a number of shortcomings that prevent it from being a fully
63 \item An SD card is required to use many features, since the internal
64 flash memory is read-only in Rockbox.
65 \warn{The SD driver is still in development and may contain bugs.
66 There have been reports of SD cards becoming unusable after being used
67 with Rockbox on
\playerman{} \playertype{}. Only use old, low-capacity
68 cards until we are satisfied the driver is safe to use.\\
}
69 \item There is only basic touchscreen support. Further work is
70 required to make the UI more usable with a touchscreen in general.
71 \note{The touchscreen can be used in two modes, either a
3$
\times$
3 grid mode
72 which divides the screen into areas to emulate a set of physical
73 buttons (the default setting), or ``absolute point'' mode where the
74 touchscreen is used to point to items on the screen.\\
}
80 \item[Current limitations.
] Most Rockbox functions are usable on the
81 \playertype{}, including music playback and most plugins, but
82 there are a number of shortcomings that prevent it from being a fully
85 \item A MicroSD card is required to run Rockbox, since the internal
86 flash memory hasn't been figured out yet.
87 \item There is only basic touchscreen support. Further work is
88 required to make the UI more usable with a touchscreen in general.
89 \note{The touchscreen can be used in two modes, either a
3$
\times$
3 grid mode
90 which divides the screen into areas to emulate a set of physical
91 buttons (the default setting), or ``absolute point'' mode where the
92 touchscreen is used to point to items on the screen.\\
}
98 \item[DRM capability.
] If your
\dap{} has a US firmware, then by installing Rockbox you will
99 \emph{permanently
} lose the ability to playback files with DRM.
105 \item[DRM capability.
] It is possible that installation of the bootloader
106 may lead to you
\emph{permanently
} losing the ability to playback files
115 \item[USB connection.
]
118 \item[Firewire connection.
]
120 To transfer Rockbox to your
\dap{} you need to
121 connect it to your computer. For manual installation/uninstallation, or
122 should autodetection fail during automatic installation, you need to know
123 where to access the
\dap{}. On Windows this means you need to know
124 the drive letter associated with the
\dap{}. On Linux you need to know
125 the mount point of your
\dap{}. On Mac OS X you need to know the volume
129 If you have Itunes installed and it is configured to open automatically
130 when your
\dap{} is attached (the default behaviour), then wait for it to
131 open and then quit it. You also need to ensure the ``Enable use as disk''
132 option is enabled for your
\dap{} in Itunes. Your
\dap{} should then enter
133 disk mode automatically when connected to a computer via
134 \nopt{ipod1g2g
}{USB.
}\opt{ipod1g2g
}{Firewire.
} If your computer does not
135 recognise your
\dap{}, you may need to enter disk mode manually. Disconnect
136 your
\dap{} from the computer. Hard reset the
\dap{} by pressing and
137 holding the
\ButtonMenu{} and
\nopt{IPOD_3G_PAD
}{\ButtonSelect{}}%
138 \opt{IPOD_3G_PAD
}{\ButtonPlay{}} buttons simultaneously. As soon as the
139 \dap{} resets, press and hold the
\nopt{IPOD_3G_PAD
}{\ButtonSelect{} and
140 \ButtonPlay{}}\opt{IPOD_3G_PAD
}{\ButtonLeft{} and
\ButtonRight{}} buttons
141 simultaneously. Your
\dap{} should enter disk mode and you can try
142 reconnecting to the computer.
145 When instructed to connect/disconnect the USB cable, always use
146 the USB port through the subpack, not the side `USB Host' port. The side port
147 is intended to be used for USB OTG connections only (digital cameras, memory
150 \opt{sansa,e200v2,clipv1,clipv2
}{
151 \note{The following steps require you to change the setting in
152 \setting{Settings $
\rightarrow$ USB Mode
} to
\setting{MSC
} from within the
155 \nopt{sansaAMS
}{\warn{Never extract files to your
\dap{} while it is in recovery mode.
}}
158 \opt{fuze,fuzev2,clipplus
}{
159 \note{The following steps require you to change the setting in
160 \setting{Settings $
\rightarrow$ System Settings $
\rightarrow$ USB Mode
} to
161 \setting{MSC
} from within the original firmware.
}
164 \opt{iriverh10,iriverh10_5gb
}{
165 The installation requires you to use UMS mode and so
166 may require use of the UMS trick, whereby it is possible to force a MTP
167 \playertype{} to start up in UMS mode as follows:
169 \item Ensure the
\dap{} is fully powered off by
\opt{iriverh10
}{using
170 a pin to push the small reset button inside the hole between the
171 \ButtonHold{} switch and remote control connector.
}\opt{iriverh10_5gb
}{removing
172 the battery and putting it back in again.
}
173 \item Connect your
\playertype{} to the computer using the data cable.
174 \item Hold
\ButtonRight{} and push
\ButtonPower{} to turn the
\dap{} on.
175 \item Continue holding
\ButtonRight{} until the USB Connected screen appears.
176 \item The
\dap{} will now appear as a regular disk on your computer.
178 \note{Once Rockbox has been installed, when you shut down your
\dap{} from Rockbox it will totally
179 power the player off so step
1 is no longer necessary.
}
181 \opt{gigabeatf
}{The installation requires you to change a setting in the
182 original firmware. Make sure the option under
\setting{Setup
183 $
\rightarrow$ Connections $
\rightarrow$ PC Connections
} is set to
184 \setting{gigabeat room
}. Also, during installation, do not connect your
185 \dap{} using the cradle but plug the USB cable directly to the
\dap{}.
188 The installation requires you to use UMS mode.
189 In order to start up your
\playertype{} in UMS mode you need to:
191 \item Turn off the
\dap{} (Original Firmware).
192 \item Connect your
\playertype{} to the computer using the data cable.
193 \item Push and hold
\ButtonPower{} (for about
2 seconds) until the ``USB'' screen appears.
195 The
\dap{} will now appear as a regular disk on your computer.
202 \item[Administrator/Root rights.
] Installing the bootloader portion of Rockbox
203 requires you to have administrative (Windows) or root (Linux) rights.
204 Consequently when doing either the automatic or manual bootloader install,
205 please ensure that you are logged in with an administrator account or have root rights.
211 \item[File system format.
] Rockbox only works on Ipods formatted with
212 the FAT32 filesystem (i.e. Ipods initialised by Itunes
213 for Windows). It does not work with the HFS+ filesystem (i.e. Ipods
214 initialised by Itunes for the Mac). More information and instructions for
215 converting an Ipod to FAT32 can be found on the
216 \wikilink{IpodConversionToFAT32
} wiki
217 page on the Rockbox website. Note that after conversion, you can still use
218 a FAT32 Ipod with a Mac.
222 \section{Installing Rockbox
}\label{sec:installing_rockbox
}\index{Installation
}
223 There are two ways to install Rockbox: automated and manual. The automated
224 way is the preferred method of installing Rockbox for the majority of
225 people. Rockbox Utility is a graphical application that does almost everything
226 for you. However, should you encounter a problem, then the manual way is
227 still available to you.\\
229 \opt{gigabeats
}{\note{The automated install is not yet available for the
230 \playerlongtype{}. For now you can use the manual method to install Rockbox.
231 Please still read the section on the automatic install as it explains
232 various important aspects of Rockbox, such as the different versions
235 \opt{hwcodec
}{Rockbox itself comes as a single package. There is no need
236 to install additional software to run Rockbox.
}
238 \opt{HAVE_RB_BL_ON_DISK
}{There are three separate components,
239 two of which need to be installed in order to run Rockbox:
}
240 \opt{HAVE_RB_BL_IN_FLASH
}{There are two separate components
241 which need to be installed in order to run Rockbox:
}
244 \opt{HAVE_RB_BL_ON_DISK
}{
245 \item[The
\playerman{} bootloader.
]
246 The
\playerman{} bootloader is the program that tells your
\dap{} how to load
247 and start the original firmware. It is also responsible for any emergency,
248 recovery, or disk modes on your
\dap{}. This bootloader is stored in special flash
249 memory in your
\playerman{} and comes factory-installed. It is not necessary
250 to modify this in order to install Rockbox.
}
252 \item[The Rockbox bootloader.
] \index{Bootloader
}
253 \opt{HAVE_RB_BL_ON_DISK
}{The Rockbox bootloader is loaded from disk by
254 the
\playerman{} bootloader. It is responsible for loading the Rockbox
255 firmware and for providing the dual boot function. It directly replaces the
256 \playerman{} firmware in the
\daps{} boot sequence.
257 \opt{gigabeatf
}{\note{Dual boot does not currently work on the Gigabeat.
}}}
259 \opt{HAVE_RB_BL_IN_FLASH
}{
260 The bootloader is the program that tells your
261 \dap{} how to load and start other components of Rockbox and for providing
262 the dual boot function. This is the component of Rockbox that is installed
263 to the flash memory of your
\playerman.
264 \opt{iaudiom3,iaudiom5,iaudiox5
}{\note{Dual boot does not currently work on the
\playertype.
}}}
266 \item[The Rockbox firmware.
]
267 \opt{HAVE_RB_BL_IN_FLASH
}{Unlike the
\playerman{} firmware, which runs
268 entirely from flash memory,
}
269 \opt{HAVE_RB_BL_ON_DISK
}{Similar to the
\playerman{} firmware,
}
270 most of the Rockbox code is contained in a
271 ``build'' that resides on your
\daps{} drive. This makes it easy to
272 update Rockbox. The build consists of a directory called
273 \fname{.rockbox
} which contains all of the Rockbox files, and is
274 located in the root of your
\daps{} drive.
279 Apart from the required parts there are some addons you might be interested
282 \item[Fonts.
] Rockbox can load custom fonts. The fonts are
283 distributed as a separate package and thus need to be installed
284 separately. They are not required to run Rockbox itself but
285 a lot of themes require the fonts package to be installed.
287 \item[Themes.
] The appearance of Rockbox can be customised by themes. Depending
288 on your taste you might want to install additional themes to change
293 \subsection{Automated Installation
}
295 To automatically install Rockbox, download the official installer and
296 housekeeping tool
\caps{Rockbox Utility
}. It allows you to:
298 \item Automatically install all needed components for using Rockbox
299 (``Minimal Installation'').
300 \item Automatically install all suggested components (``Complete Installation'').
301 \item Selectively install optional components.
302 \nopt{player
}{\item Install additional fonts and themes.
}
303 \item Install voice files and generate talk clips.
304 \item Uninstall all components you installed using Rockbox Utility.
307 Prebuilt binaries for Windows, Linux and Mac OS X are
308 available at the
\wikilink{RockboxUtility
} wiki page.\\
310 \opt{gigabeats,ondavx777
}{\note{Rockbox Utility does not currently support the
311 \playertype{} and you will therefore need to follow the manual install
312 instructions below.\\
}}
314 When first starting
\caps{Rockbox Utility
} run ``Autodetect'',
315 found in the configuration dialog (File $
\rightarrow$ Configure). Autodetection
316 can detect most player types. If autodetection fails or is unable to detect
317 the mountpoint, make sure to enter the correct values. The mountpoint indicates
318 the location of the
\dap{} in your filesystem. On Windows, this is the drive
319 letter the
\dap{} gets assigned, on other systems this is a path in the
323 \opt{iriverh100,iriverh300
}{
324 Rockbox Utility will ask you for a compatible copy of the original
325 firmware. This is because for legal reasons we cannot distribute
326 the bootloader directly. Instead, we have to patch the Iriver firmware
327 with the Rockbox bootloader.
329 Download a supported version of the Iriver firmware for your
330 \playername{} from the Iriver website, links can be found on
331 \wikilink{IriverBoot
}.
333 Supported Iriver firmware versions currently include
334 \opt{iriverh100
}{1.63US,
1.63EU,
1.63K,
1.65US,
1.65EU,
1.65K,
1.66US,
335 1.66EU and
1.66K. Note that the H140 uses the same firmware as the H120;
336 H120 and H140 owners should use the firmware called
\fname{ihp
\_120.hex
}.
337 Likewise, the iHP110 and iHP115 use the same firmware, called
338 \fname{ihp
\_100.hex
}. Be sure to use the correct firmware file for
340 \opt{iriverh300
}{1.28K,
1.28EU,
1.28J,
1.29K,
1.29J and
1.30EU.
341 \note{The US
\playername{} firmware is not supported and cannot be
342 patched to be used with the bootloader. If you wish to install Rockbox
343 on a US
\playername{}, you must first install a non-US version of the
344 original firmware and then install one of the supported versions patched
345 with the Rockbox bootloader.
}
346 \warn{Installing a non-US firmware on a US
\playername{} will
347 \emph{permanently
} remove DRM support from the player.
}}
349 If the file that you downloaded is a
\fname{.zip
} file, use an unzip
350 utility like mentioned in the prerequisites section to extract
351 the
\fname{.hex
} from the
\fname{.zip
} file
352 to your desktop. Likewise, if the file that you downloaded is an
353 \fname{.exe
} file, double-click on the
\fname{.exe
} file to extract
354 the
\fname{.hex
} file to your desktop.
355 When running Linux you should be able to extract
\fname{.exe
}
356 files using
\fname{unzip
}.
360 Rockbox Utility will ask you for a compatible copy of the original
361 firmware. This is because for legal reasons we cannot distribute
362 the bootloader directly. Instead, we have to patch the MPIO firmware
363 with the Rockbox bootloader.
365 Download a supported version of the MPIO firmware for your
366 \playername{} from the MPIO website, links can be found on
367 \wikilink{MPIOHD200Port
}.
369 \warn{The only tested version of the original firmware is
1.30.05
370 and as such is the only supported version
}
372 If the file that you downloaded is a
\fname{.zip
} file, use an unzip
373 utility like mentioned in the prerequisites section to extract
374 the
\fname{.SYS
} from the
\fname{.zip
} file
375 to your desktop. Likewise, if the file that you downloaded is an
376 \fname{.exe
} file, double-click on the
\fname{.exe
} file to extract
377 the
\fname{.SYS
} file to your desktop.
378 When running Linux you should be able to extract
\fname{.exe
}
379 files using
\fname{unzip
}.
382 \subsubsection{Choosing a Rockbox version
}\label{sec:choosing_version
}
384 There are three different versions of Rockbox available from the
387 Release version, current build and archived daily build. You need to decide which one
388 you want to install and get the appropriate version for your
\dap{}. If you
389 select either ``Minimal Installation'' or ``Complete Installation'' from the
390 ``Quick Start'' tab, then Rockbox Utility will automatically install the
391 release version of Rockbox. Using the ``Installation'' tab will allow you
392 to select which version you wish to install.
396 \item[Release.
] The release version is the latest stable release, free
397 of known critical bugs. For a manual install, the current stable release of Rockbox is
398 available at
\url{http://www.rockbox.org/download/
}.
400 \item[Current Build.
] The current build is built at each source code change to
401 the Rockbox SVN repository and represents the current state of Rockbox
402 development. This means that the build could contain bugs but most of
403 the time is safe to use. For a manual install, you can download the current build from
404 \url{http://build.rockbox.org/
}.
406 \item[Archived Build.
] In addition to the release version and the current build,
407 there is also an archive of daily builds available for download. These are
408 built once a day from the latest source code in the SVN repository. For a manual install,
409 you can download archived builds from
\url{http://www.rockbox.org/daily.shtml
}.
413 \note{Because current and archived builds are development versions that
414 change frequently, they may behave differently than described in this manual,
415 or they may introduce new (and potentially annoying) bugs. Unless you wish to
416 try the latest and greatest features at the price of possibly greater instability,
417 or you wish to help with development, you should stick with the release.\\*
}
419 Please now go to
\reference{ref:finish_install
} to complete the installation procedure.
421 \subsection{Manual Installation
}
423 The manual installation method is still available to you, should you need or desire it
424 by following the instructions below. If you have used Rockbox Utility
425 to install Rockbox, then you do not need to follow the next section and can skip
426 straight to
\reference{ref:finish_install
}
428 \opt{gigabeats
}{\subsubsection{Installing the bootloader
}
429 \input{getting_started/gigabeats_install.tex
}
432 \subsubsection{Installing the firmware
}\label{sec:installing_firmware
}
434 \opt{gigabeats
}{\note{When your
\dap{} is in the Rockbox USB or bootloader
435 USB mode, you will see two visible partitions - the
150~MB firmware
436 partition (containing at least a file called
\fname{nk.bin
}) and
437 the main data partition. Rockbox
\emph{must
} be installed onto the main
441 \item Download your chosen version of Rockbox from the links in the
443 \opt{ipodvideo
}{\note{There are separate versions of Rockbox for the
30~GB and
444 60/
80~GB
\playerman{} \playertype{} models. You must ensure you download the
445 correct version for your
\dap{}.
}}
447 \item Connect your
\dap{} to the computer via USB
448 \opt{sansa,sansaAMS,iriverh10,iriverh10_5gb,vibe500
}{ in MSC mode
}
449 \opt{ipod3g,ipod4g,ipodmini,ipodcolor
}{ or Firewire
}as described in
450 the manual that came with your
\dap{}.
452 \item Take the
\fname{.zip
} file that you downloaded and use
453 the ``Extract all'' command of your unzip program to extract
455 \opt{gigabeats
}{the main data partition of
}
456 \opt{cowond2
}{either an SD card or the internal memory of
}
457 \opt{ondavx777
}{the MicroSD of
}
459 \opt{cowond2
}{\note{If you have chosen to extract to the internal memory, it
460 will not be possible to save settings.
}}
463 \note{The entire contents of the
\fname{.zip
} file should be extracted
464 directly to the root of your
\daps{} drive. Do not try to
465 create a separate directory on your
\dap{} for the Rockbox
466 files! The
\fname{.zip
} file already contains the internal
467 structure that Rockbox needs.\\
}
470 If the contents of the
\fname{.zip
} file are extracted correctly, you will
471 have a file called
\fname{\firmwarefilename} in the main directory of your
472 \daps{} drive, and also a directory called
\fname{.rockbox
}, which contains a
473 number of other directories and system files needed by Rockbox.
476 % This has nothing to do with swcodec, just that these players need our own
477 % bootloader so we can decide where we want the main binary.
479 If the contents of the
\fname{.zip
} file are extracted correctly, you will
480 have a directory called
\fname{.rockbox
}, which contains all the files needed
481 by Rockbox, in the main directory of your
\daps{} drive.
486 \subsubsection{Installing the bootloader
}
487 \opt{iriverh100,iriverh300
}{\input{getting_started/iriver_install.tex
}}
488 \opt{mpiohd200
}{\input{getting_started/mpio_install.tex
}}
489 \opt{ipod
}{\input{getting_started/ipod_install.tex
}}
490 \opt{iaudio
}{\input{getting_started/iaudio_install.tex
}}
491 \opt{iriverh10,iriverh10_5gb
}{\input{getting_started/h10_install.tex
}}
492 \opt{gigabeatf
}{\input{getting_started/gigabeat_install.tex
}}
493 \opt{sansa
}{\input{getting_started/sansa_install.tex
}}
494 \opt{sansaAMS
}{\input{getting_started/sansaAMS_install.tex
}}
495 \opt{mrobe100
}{\input{getting_started/mrobe100_install.tex
}}
496 \opt{cowond2
}{\input{getting_started/cowond2_install.tex
}}
497 \opt{vibe500
}{\input{getting_started/vibe500_install.tex
}}
498 \opt{ondavx777
}{\input{getting_started/ondavx777_install.tex
}}
502 \subsection{Finishing the install
}\label{ref:finish_install
}
505 After installing you
\emph{need
} to power-cycle the
506 \dap{} by doing the following steps. Failure to do so may result in problems.
508 \item Safely eject / unmount your
\dap{} and unplug the USB cable.
509 \item Unplug any power adapter.
510 \item Hold the
\ButtonPower{} button to turn off the
\dap{}.
511 \item Slide the battery switch located on the bottom of the
\dap{} from
513 \item Slide the battery switch back from `off' to `on'.
517 \opt{iaudiom3,iaudiom5,iaudiox5
}{
518 After installing you
\emph{need
} to power-cycle the
519 \dap{} by doing the following steps.
521 \item Safely eject / unmount your
\dap{} and unplug the USB cable.
523 \opt{IAUDIO_X5_PAD
}{\ButtonPower}
524 \opt{IAUDIO_M3_PAD
}{\ButtonPlay}
525 button to turn off the
\dap{}.
526 \item Insert the charger. The Rockbox bootloader will automatically be flashed.
530 \opt{iriverh10,iriverh10_5gb,ipod,mrobe100,sansa,archos,sansaAMS,cowond2,vibe500,ondavx777
}{
531 Safely eject / unmount the USB drive, unplug the cable and restart.
535 Safely eject / unmount your
\dap{}.
538 \opt{iriverh100,iriverh300
}{
540 \item Safely eject / unmount your
\dap{}.
542 \item \warn{Before proceeding further, make sure that your player has a full charge
543 or that it is connected to the power adaptor. Interrupting the next step
544 due to a power failure most likely will brick your
\dap{}.
}
545 Update your
\daps{} firmware with the patched bootloader. To do this, turn
546 the jukebox on. Press and hold the
\ButtonSelect{} button to enter the main menu,
547 and navigate to
\setting{General $
\rightarrow$ Firmware Upgrade
}. Select
548 \setting{Yes
} when asked to confirm if you want to upgrade the
549 firmware. The
\playerman{} will display a message indicating that the
550 firmware update is in progress. Do
\emph{not
} interrupt this process. When the
551 firmware update is complete the player will turn itself off. (The update
552 firmware process usually takes a minute or so.). You are now ready to go.
557 \item Safely eject /unmount your
\dap{}.
559 \item \warn{Before proceeding further, make sure that your player has a full charge
560 or that it is connected to the power adaptor. Interrupting the next step
561 due to a power failure most likely will brick your
\dap{}.
}
562 Update your
\daps{} firmware with the patched bootloader. To do this, turn
563 the jukebox on. The update process should start automaticaly. The
\playerman{} will
564 display animation indicating that the firmware update is in progress. Do
\emph{not
}
565 interrupt this process. When the firmware update is complete the player will restart.
566 (The update firmware process usually takes a minute or so.). You are now ready to go.
569 \opt{e200
}{Your e200 will automatically reboot and Rockbox should load.
}
573 \subsection{Enabling Speech Support (optional)
}\label{sec:enabling_speech_support
}
574 \index{Speech
}\index{Installation!Optional Steps
}
575 If you wish to use speech support you will also need a voice file. Voice files
576 allow Rockbox to speak the user interface to you. Rockbox Utility can install
577 an English voice file, or you can download it from
\url{http://www.rockbox.org/daily.shtml
}
578 and unzip it to the root of your
\dap{}.
579 Rockbox Utility can also aid you in the creation of voice files with different voices
580 or in other languages if you have a suitable speech engine installed on your computer.
581 Voice menus are enabled by default and will come
582 into effect after a reboot. See
\reference{ref:Voiceconfiguration
} for details
584 Rockbox Utility can also aid in the production of talk files, which allow Rockbox
585 to speak file and folder names.
587 \section{Running Rockbox
}
588 \nopt{ipod,gigabeats,cowond2
}{When
589 you turn the unit on, Rockbox should load.
}
590 \opt{ipod
}{Hard reset the Ipod by holding
591 \opt{IPOD_4G_PAD
}{\ButtonMenu{} and
\ButtonSelect{} simultaneously
}%
592 \opt{IPOD_3G_PAD
}{\ButtonMenu{} and
\ButtonPlay{} simultaneously
}
593 for a couple of seconds until the
\dap{} resets. Now Rockbox should load.
596 \opt{gigabeats
}{Rockbox should automatically load when you turn on your player.\\
599 If you have loaded music onto your
\dap{} using the
\playerman{}
600 firmware, you will not be able to see your music properly in the
601 \setting{File Browser
} as MTP mode changes the location and file names.
602 Files placed on your
\dap{} using the
\playerman{} firmware can be
603 viewed by initialising and using Rockbox's database.
604 See
\reference{ref:database
} for more information.
}
608 To boot the Rockbox firmware set the
\ButtonHold{} switch immediately after
610 \note{If you have chosen to install to an SD card and it is inserted at power
611 on, Rockbox will boot from that card and use it as the primary drive for
612 storing settings, etc. If there is no SD card inserted, Rockbox will boot
613 from the internal memory, and it will not be possible to save settings.
}
618 If you have loaded music onto your
\dap{} using Itunes,
619 you will not be able to see your music properly in the
\setting{File Browser
}.
620 This is because Itunes changes your files' names and hides them in
621 directories in the
\fname{Ipod
\_Control} directory. Files placed on your
622 \dap{} using Itunes can be viewed by initialising and using Rockbox's database.
623 See
\reference{ref:database
} for more information.
628 \fixme{Add a note about the charging trick and place it here?
}
631 \section{Updating Rockbox
}
632 Rockbox can be easily updated with Rockbox Utility.
633 You can also update Rockbox manually -- download a Rockbox build
634 as detailed above, and unzip the build to the root directory
635 of your
\dap{} as in the manual installation stage. If your unzip
636 program asks you whether to overwrite files, choose the ``Yes to all'' option.
637 The new build will be installed over your current build.\\
640 \note{When your
\dap{} is in the Rockbox USB or bootloader
641 USB mode, you will see two visible partitions, the
150~MB firmware
642 partition (containing at least a file called
\fname{nk.bin
}) and
643 the main data partition. Rockbox
\emph{must
} be installed onto the main
648 The bootloader only changes rarely, and should not normally
649 need to be updated.\\
652 \note{If you use Rockbox Utility be aware that it cannot detect manually
653 installed components.
}
655 \section{Uninstalling Rockbox
}\index{Installation!uninstall
}
657 \nopt{gigabeatf,iaudiom3,iaudiom5,iaudiox5,archos,mrobe100,gigabeats
}{
658 \note{The Rockbox bootloader allows you to choose between Rockbox and
659 the original firmware. (See
\reference{ref:Dualboot
} for more information.)
}
662 \subsection{Automatic Uninstallation
}
663 \opt{gigabeats
}{\note{Rockbox can only be uninstalled manually for now.
}}
665 You can uninstall Rockbox automatically by using Rockbox Utility. If you
666 installed Rockbox manually you can still use Rockbox Utility for uninstallation
667 but will not be able to do this selectively.
669 \opt{iriverh100,iriverh300
}{\note{Rockbox Utility cannot uninstall the bootloader due to
670 the fact that it requires a flashing procedure. To uninstall the bootloader
671 completely follow the manual uninstallation instructions below.
}}
673 \subsection{Manual Uninstallation
}
676 If you would like to go back to using the original
\playerman{} software,
677 connect the
\dap{} to your computer, and delete the
678 \fname{\firmwarefilename} file.
681 \opt{iriverh10,iriverh10_5gb
}{
682 If you would like to go back to using the original
\playerman{} software,
683 connect the
\dap{} to your computer, and delete the
684 \opt{iriverh10
}{\fname{H10
\_20GC.mi4
}}\opt{iriverh10_5gb
}{\fname{H10.mi4
}}
685 file and rename
\fname{OF.mi4
} to
\opt{iriverh10
}{\fname{H10
\_20GC.mi4
}}%
686 \opt{iriverh10_5gb
}{\fname{H10.mi4
}} in the
\fname{System
} directory on
687 your
\playertype{}. As in the installation, it may be necessary to first
688 put your device into UMS mode.
692 If you would like to go back to using the original
\playerman{} software,
693 connect the
\dap{} to your computer, and delete the
694 \fname{jukebox.mi4
} file and rename
695 \fname{OF.mi4
} to
\fname{JUKEBOX.mi4
}
696 in the
\fname{System
} directory on your
\playertype{}. As in the installation,
697 it may be necessary to first put your device into UMS mode.
701 If you would like to go back to using the original
\playerman{} software,
702 connect the
\dap{} to your computer, and delete the
703 \fname{pp5020.mi4
} file and rename
704 \fname{OF.mi4
} to
\fname{pp5020.mi4
}
705 in the
\fname{System
} directory on your
\playertype{}.
709 If you would like to go back to using the original
\playerman{} software,
710 connect the
\dap{} to your computer, and follow the instructions to install
711 the bootloader, but when prompted by sansapatcher, enter
\texttt{u
} for uninstall,
712 instead of
\texttt{i
} for install. As in the installation, it may be necessary to
713 first put your
\dap{} into MSC mode.
717 To uninstall Rockbox and go back to using just the original Ipod software, connect
718 the
\dap{} to your computer and follow the instructions to install
719 the bootloader but, when prompted by ipodpatcher, enter
\texttt{u
} for uninstall
720 instead of
\texttt{i
} for install.
723 \opt{iaudiom3,iaudiom5,iaudiox5
}{
724 If you would like to go back to using the original
\playerman{} software,
725 connect the
\dap{} to your computer, download the original
\playername{}
726 firmware from the
\playerman{} website, and copy it to the
\fname{FIRMWARE
}
727 directory on your
\playername{}. Turn off the
\dap{}, remove the USB cable
728 and insert the charger. The original firmware will automatically be flashed.
731 \opt{iriverh100,iriverh300
}{
732 If you want to remove the Rockbox bootloader, simply flash an unpatched
733 \playerman{} firmware. Be aware that doing so will also remove the bootloader
734 USB mode. As that mode can come in quite handy (especially if you experience
735 disk errors) it is recommended to keep the bootloader. It also
736 gives you the possibility of trying Rockbox anytime later by simply
737 installing the distribution files.
739 The Rockbox bootloader will automatically start the original firmware if
740 the
\fname{.rockbox
} directory has been deleted.
743 Although if you retain the Rockbox bootloader, you will need to hold the
744 \ButtonRec{} button each time you want to start the original firmware.
749 Copy an unmodified original firmware to your player and update it.
753 If you want to remove the Rockbox bootloader, simply flash an unpatched
754 \playerman{} firmware.
758 If you wish to clean up your disk, you may also wish to delete the
759 \fname{.rockbox
} directory and its contents.
760 \nopt{iaudiom3,iaudiom5,iaudiox5
}{Turn the
\playerman{} off.
761 Turn the
\dap{} back on and the original
\playerman{} software will load.
}
765 If you wish to clean up your disk by deleting the
766 \fname{.rockbox
} directory and its contents, this must be done
767 before uninstalling the bootloader in the next step.
769 Before installation you should have downloaded a copy of the
\playerman{}
771 \url{http://www.tacp.toshiba.com/tacpassets-images/firmware/MESV12US.zip
}.
773 \item Extract
\fname{MES12US.iso
} from the
\fname{.zip
} downloaded above.
774 \item There are two files within
\fname{MES12US.iso
} called
775 \fname{Autorun.inf
} and
\fname{gbs
\_update\_1\_2\_us.exe
}. Extract them with
776 your favourite unzipping utility e.g.
7zip.
777 \item Connect your
\dap{} to your computer.
778 \item Extract
\fname{nk.bin
} from within
779 \fname{gbs
\_update\_1\_2\_us.exe
} using e.g.
7zip and copy it to the
150~MB
780 firmware partition of your
\dap{}.
781 \item Safely eject / unmount the USB drive, unplug the cable and restart.
784 \note{From Windows, you can also run
\fname{gbs
\_update\_1\_2\_us.exe
}
785 directly to restore your
\dap{}. This will format your
\dap{},
789 \section{Troubleshooting
}
792 \item[Bootloader install problems
]
793 If you have trouble installing the bootloader,
794 please ensure that you are either logged in as an administrator (Windows), or
795 you have root rights (Linux)
}
797 \opt{iriverh100,iriverh300
}{
798 \item[Immediately loading original firmware.
]
799 If the original firmware is immediately
800 loaded without the Rockbox bootloader appearing first, then the Rockbox bootloader
801 has not been correctly installed. The original firmware update will only perform
802 the update if the filename is correct, including case. Make sure that the patched
803 Iriver firmware is called
\fname{.hex
}.
}
805 \nopt{iriverh100,iriverh300,mpiohd200
}{\item[``File Not Found''
]}
806 \opt{iriverh100,iriverh300,mpiohd200
}{\item[``-
1 error''
]}
808 \nopt{iriverh100,iriverh300,mpiohd200
}{``File Not Found''
}
809 \opt{iriverh100,iriverh300,mpiohd200
}{``-
1 error''
}
810 from the bootloader, then the bootloader cannot find the Rockbox firmware.
811 This is usually a result of not extracting the contents of the
\fname{.zip
}
812 file to the proper location, and should not happen when Rockbox has been
813 installed with Rockbox Utility.
815 To fix this, either install Rockbox with the Rockbox Utility which will take care
816 of this for you, or recheck the Manual Install section to see where the files
821 If this does not fix the problem, there are two additional procedures that you
822 can try to solve this:
825 \item Formatting the storage partition. It is possible that using the
826 mkdosfs utility from Linux to format the data partition from your PC
827 before installing will resolve this problem. The appropriate format command is:
829 mkdosfs -f
2 -F
32 -S
512 -s
64 -v -n TFAT /path/to/partition/device
831 \warn{This will remove all your files.
}
833 \item Copying a
\fname{tar
}. If you have a Rockbox build environment
834 then you can try generating
\fname{rockbox.tar
} instead of
835 \fname{rockbox.zip
} as follows:
839 and copying it to the data partition. During the next boot, the bootloader