Difference between revisions of "Android: Fastboot setup"
(New page: = Overview = Fastboot is a protocol and associated utility, used primarily to modify flash file system while the device is in a bootloader. Fastboot operates via USB OTG. In addition to th...) |
(→Forcing fastboot mode) |
||
Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
− | Fastboot is a protocol and associated utility, used primarily to modify flash file system while the device is | + | Fastboot is a protocol and associated utility, used primarily to modify flash file system while the device is running a bootloader. Fastboot operates via USB OTG. In addition to the bootloader implementing the fastboot protocol, fastboot client utility must be installed on user's workstation. |
= Getting Fastboot = | = Getting Fastboot = | ||
Line 7: | Line 7: | ||
= Useful commands = | = Useful commands = | ||
− | * List connected devices | + | * List connected devices <pre>$ fastboot devices</pre> |
− | <pre> | + | * Reboot device <pre>$ fastboot reboot</pre> |
− | $ fastboot devices | + | * Flash image file onto partition identified by its name, e.g. ''boot'' <pre>$ fastboot flash boot boot.img</pre> |
− | </pre> | + | * Boot device, loading ''boot.img'' from the PC workstation, instead of boot partition <pre>$ fastboot boot boot.img</pre> |
− | * Reboot device | + | |
− | <pre> | + | = Forcing fastboot mode = |
− | $ fastboot reboot | + | Normally a bootloader will proceed to booting a valid boot partition. In case there is none, the bootloader will fall back into fastboot mode.<br/> |
− | </pre> | + | There are a few options to force fastboot mode despite valid boot partition: |
− | * Flash image file onto partition identified by its name, e.g. ''boot'' | + | * By rebooting to fastboot mode. Issue on either workstation <pre>$ adb reboot bootloader</pre> or Android device itself <pre># reboot bootloader</pre> |
− | <pre> | + | * By powering up while pressing the '''boot select''' button. |
− | $ fastboot flash boot boot.img | + | * By invalidating boot partition. Destroy boot partition signature, issuing on the device (in either Linux or Android command line): <pre># dd if=/dev/zero of=/path/to/boot/partition bs=1 count=1</pre> |
− | </pre> | + | {{Note | path-to-boot-partition may be, e.g, {{filename | /dev/block/platform/msm_sdcc.1/by-name/boot}} }} |
− | * Boot device, loading ''boot.img'' from the PC workstation, instead of boot partition | ||
− | <pre> | ||
− | $ fastboot boot boot.img | ||
− | </pre> | ||
= See Also = | = See Also = |
Latest revision as of 08:55, 21 September 2015
Overview
Fastboot is a protocol and associated utility, used primarily to modify flash file system while the device is running a bootloader. Fastboot operates via USB OTG. In addition to the bootloader implementing the fastboot protocol, fastboot client utility must be installed on user's workstation.
Getting Fastboot
In general fastboot utility is provided within the Android SDK. Also some Linux disributions provide fastboot within their package repositories. For example, on Ubuntu platform, fastboot may be obtained via android-tools-fastboot package.
Useful commands
- List connected devices
$ fastboot devices
- Reboot device
$ fastboot reboot
- Flash image file onto partition identified by its name, e.g. boot
$ fastboot flash boot boot.img
- Boot device, loading boot.img from the PC workstation, instead of boot partition
$ fastboot boot boot.img
Forcing fastboot mode
Normally a bootloader will proceed to booting a valid boot partition. In case there is none, the bootloader will fall back into fastboot mode.
There are a few options to force fastboot mode despite valid boot partition:
- By rebooting to fastboot mode. Issue on either workstation
$ adb reboot bootloader
or Android device itself# reboot bootloader
- By powering up while pressing the boot select button.
- By invalidating boot partition. Destroy boot partition signature, issuing on the device (in either Linux or Android command line):
# dd if=/dev/zero of=/path/to/boot/partition bs=1 count=1
path-to-boot-partition may be, e.g, /dev/block/platform/msm_sdcc.1/by-name/boot |