mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-21 02:10:11 +08:00
Merge pull request #4764 from name1e5s/master
[Translated]The Complete Guide to Flashing Factory Images Using Fastb
This commit is contained in:
Xingyu.Wang
GitHub
commit
65e94c013e
@ -1,271 +0,0 @@
|
||||
Name1e5s Translating
|
||||
|
||||
The Complete Guide to Flashing Factory Images Using Fastboot
|
||||
==========
|
||||
|
||||
|
||||
|
||||
If your phone has an unlocked [bootloader][31], you can use [Fastboot][32] commands to flash factory images. That may sound like a bunch of technical jargon, but when it comes down to it, this is the best method for updating a [rooted][33] device, fixing a [bricked][34] phone, reverting to stock, or even getting new Android updates before everyone else.
|
||||
|
||||
Much like [ADB][35], Fastboot is a very powerful Android utility that accepts commands through a terminal shell. But if that sounds intimidating, don't worry—because once you've learned your way around things, you'll know so much more about the inner workings of Android, as well as how to fix most common problems.
|
||||
|
||||
### A Note About Samsung Devices
|
||||
|
||||
The process outlined below will work for most Nexus, Pixel, HTC, and Motorola devices, as well as phones and tablets from many other manufacturers. However, Samsung devices use their own firmware-flashing software, so Fastboot isn't the way to go if you own a Galaxy. Instead, it's best to use [Odin][36] to flash firmware on a Samsung device, and we've covered that process at the following link.
|
||||
|
||||
|
||||
### Step 1Install ADB & Fastboot on Your Computer
|
||||
|
||||
First, you'll have to install ADB and Fastboot on your computer, which are the utilities that let you flash images using Fastboot commands. There are several "one-click" and "light" versions of ADB and Fastboot, but I wouldn't recommend using these because they're not updated as frequently as the official utilities, so they might not be fully compatible with newer devices.
|
||||
|
||||
Instead, your best bet is to install the Android SDK Tools from Google. This is the "real" ADB and Fastboot, and it may take a little longer to install, but it's well worth the initial time investment. I've outlined the install process for Windows, Mac, and Linux in _Method 1_ at the following guide, so head over there to get started.
|
||||
|
||||
|
||||
### Step 2Enable OEM Unlocking
|
||||
|
||||
In order to flash images using Fastboot, your device's [bootloader][37] will need to be unlocked. If you've already done this, you can skip ahead to Step 3.
|
||||
|
||||
But before you can unlock your bootloader, there's [a setting that you'll need to enable][38] if your device shipped with [Android Marshmallow or higher][39] preinstalled. To access this setting, start by **[enabling the Developer options menu][18]** on your phone or tablet. Once you've done that, open the Developer options menu, then enable the switch next to "OEM unlocking," and you'll be good to go.
|
||||
|
||||
[
|
||||
|
||||
][1]
|
||||
|
||||
If this option is not present on your device, it's likely that your device didn't ship with Android Marshmallow or higher preinstalled. However, if the option is present but grayed out, this usually means that your bootloader cannot be unlocked, which means you won't be able to flash images using Fastboot.
|
||||
|
||||
### Step 3Put Your Phone into Bootloader Mode
|
||||
|
||||
In order to run any Fastboot commands, your phone or tablet will need to be in bootloader mode. This process will vary depending on your device.
|
||||
|
||||
For most phones, start by powering your device completely off. When the screen goes black, press and hold the volume down and power buttons simultaneously, and keep holding them for about 10 seconds.
|
||||
|
||||
If that doesn't work, turn the phone off, then press and hold the volume down button. From there plug a USB data cable into your PC, then simply wait a few seconds.
|
||||
|
||||
If that still didn't work, try repeating the USB cable method, but this time use the volume up button.
|
||||
|
||||
Within moments, you should be greeted by Android's Bootloader menu, which should look something like this:
|
||||
|
||||
[
|
||||
|
||||
][2]
|
||||
|
||||
When you see this screen, make sure your phone or tablet is plugged into your computer with a USB data cable. Aside from that, leave the device alone, as the rest of the work will be done on the computer side of things.
|
||||
|
||||
|
||||
### Step 4 Open an ADB Shell on Your Computer
|
||||
|
||||
Navigate to the ADB and Fastboot installation directory on your computer. For Windows users, this can usually be found at _C:\Program Files (x86)\Android\android-sdk\platform-tools_. For Mac and Linux users, it depends on where you extracted your ADB folder when you installed the utility, so search your hard drive for the _platform-tools_ folder if you've forgotten.
|
||||
|
||||
From here, if you're using a Windows PC, hold down the shift button on your keyboard, then right-click any empty space and choose "Open command window here." For Mac and Linux users, simply open a Terminal window, then change directories to the _platform-tools_ folder inside of your ADB installation directory.
|
||||
|
||||
[
|
||||
|
||||
][3]
|
||||
|
||||
### Step 5Unlock the Bootloader
|
||||
|
||||
This next step is something you only need to do once, so if your bootloader is already unlocked, you can skip ahead. Otherwise, you'll need to run a single Fastboot command—but note that **this will wipe all data on your device**.
|
||||
|
||||
Before we get into this part, note that I'll be listing the commands for Windows users. Mac users will have to add a period and a slash (**./**) before each of these commands, and Linux users will have to add a slash (**/**) to the front.
|
||||
|
||||
So from the ADB shell, type the following command, then hit enter.
|
||||
|
||||
* **fastboot devices**
|
||||
|
||||
If that returns a series of letters and numbers followed by the word "fastboot," then your device is connected properly and you're good to go. Otherwise, refer back to Step 1 to check your ADB and Fastboot installation, and ensure that your device is in bootloader mode as shown in Step 3.
|
||||
|
||||
[
|
||||
|
||||
][4]
|
||||
|
||||
Next up, it's time to unlock your bootloader. Depending on the Android version your device shipped with, this will be done in one of two ways.
|
||||
|
||||
So if your device shipped with Lollipop or lower pre-installed, enter the following command:
|
||||
|
||||
* **fastboot oem unlock**
|
||||
|
||||
If your device shipped with Marshmallow or higher, type the following command, then hit enter:
|
||||
|
||||
* **fastboot flashing unlock**
|
||||
|
||||
[
|
||||
|
||||
][5]
|
||||
|
||||
>Sending the bootloader unlock command to a device that shipped with Marshmallow or higher.
|
||||
|
||||
At this point, you'll see a message on your Android device asking if you're sure you'd like to unlock the bootloader. Make sure the "Yes" option is highlighted, and if it's not, use your volume keys to do so. From there, press the power button, then your bootloader will unlock and your phone will reboot back into Fastboot mode.
|
||||
|
||||
[
|
||||
|
||||
][6]
|
||||
|
||||
Bootloader-unlock screen on the Nexus 6P.Image by Dallas Thomas/Gadget Hacks
|
||||
|
||||
### Step 6Download the Factory Images
|
||||
|
||||
Now that your bootloader is unlocked, you're ready to start flashing factory images—but first, you'll have to download the actual images themselves. Below are some links to download the factory images package for common devices.
|
||||
|
||||
* **[Factory images for Nexus or Pixel devices][15]**
|
||||
* **[Factory images for HTC devices][16]**
|
||||
* **[Factory images for Motorola devices][17]**
|
||||
|
||||
With each of the above links, simply locate your device model in the list, then download the latest available firmware on your computer. If your manufacturer is not listed here, try Googling "factory images for `<phone name>`."
|
||||
|
||||
|
||||
### Step 7Flash the Factory Images
|
||||
|
||||
Now it's time to flash the images. The first thing you'll want to do here is extract the factory images archive that you downloaded from your manufacturer's website. For that part, I'd recommend using **[7-Zip][19]**, as it's free and works with most archive formats.
|
||||
|
||||
[
|
||||
|
||||
][7]
|
||||
|
||||
Extracting the factory images archive.
|
||||
|
||||
Next, move all of the contents of the archive to the _platform-tools_ folder inside of your ADB installation directory, then open an ADB Shell window in this folder. For more information on that, refer back to Step 4 above.
|
||||
|
||||
[
|
||||
|
||||
][8]
|
||||
|
||||
Factory image files transferred to the platform-tools folder.
|
||||
|
||||
Aside from that, there are two different approaches you can take when flashing the images. I'll outline both of them in separate sections below.
|
||||
|
||||
|
||||
### Option 1: Use the Flash-All Script
|
||||
|
||||
Most factory images packages will contain a "flash-all" script that applies all of the images in one fell swoop. If you're trying to recover your device from a soft brick, this is the simplest way to go. However, it will unroot your device and wipe all existing data, so if you'd rather avoid that, see Option 2 below.
|
||||
|
||||
But to run the flash-all script, type the following line into the command prompt, then hit enter:
|
||||
|
||||
* **flash-all**
|
||||
|
||||
[
|
||||
|
||||
][9]
|
||||
|
||||
Sending the "flash-all" command.
|
||||
|
||||
The process will take a few minutes, but when it's done, your phone should automatically reboot and you'll be running complete, 100% stock firmware.
|
||||
|
||||
|
||||
### Option 2: Extract the Images & Flash Them Individually
|
||||
|
||||
For a second option, you can flash the system images individually. This method takes some extra work, but it can be used to un-root, update, or un-brick your device without losing existing data.
|
||||
|
||||
Start by extracting any additional archives from the factory images package. Sometimes, factory images packages can contain a series of three or four nested archives, so make sure to unzip all of them. From there, copy all of the image files to the main _platform-tools_ folder—in other words, don't leave them in any sub-folders.
|
||||
|
||||
[
|
||||
|
||||
][10]
|
||||
|
||||
All images extracted from factory images package into platform-tools folder.
|
||||
|
||||
From here, there are two images that you can get rid of: _cache.img_ and _userdata.img_. These are the images that will overwrite your data and cache with blank space, so if you don't flash them, your existing data will remain intact.
|
||||
|
||||
Of the remaining images, six make up the core elements of Android: _boot_, _bootloader_, _radio_, _recovery_, _system_, and _vendor_.
|
||||
|
||||
The _boot_ image contains the kernel, so if you just want to get rid of a custom kernel that's causing issues with your device, you only have to flash this one. To do that, type the following command into the ADB shell window:
|
||||
|
||||
* **fastboot flash boot <boot image file name>.img**
|
||||
|
||||
Next is the _bootloader_ image—this is the the interface that you're using to flash images with Fastboot commands. So to update your bootloader, type:
|
||||
|
||||
* **fastboot flash bootloader <bootloader image file name>.img**
|
||||
|
||||
Once you've done that, you should reload the bootloader so that you can continue flashing images on the newer version. To do that, type:
|
||||
|
||||
* **fastboot reboot-bootloader**
|
||||
|
||||
After that, we have the _radio_ image. This one controls connectivity on your device, so if you're having problems with Wi-Fi or mobile data, or if you just want to update your radio, type:
|
||||
|
||||
* **fastboot flash radio <radio image file name>.img**
|
||||
|
||||
Then there's _recovery_. This is something you may or may not want to flash, depending on the modifications you've made. For example, if you've installed TWRP custom recovery, flashing this image will overwrite your modification and replace it with the stock recovery interface. So if you're just updating your modded device, you should skip this one. Otherwise, if you plan to keep your phone stock and want the newer version of stock recovery, type:
|
||||
|
||||
* **fastboot flash recovery <recovery file name>.img**
|
||||
|
||||
Next up is the big one: The _system_ image. This one contains all of the files that make up the actual Android OS. As such, it's the most essential part of any update.
|
||||
|
||||
However you may not be updating your phone. You may just be re-flashing the stock firmware to recover from a soft brick. If this is the case, the system image is often the only image you need to flash in order to fix everything, because it contains the entirety of Android. In other words, if you flash this image and nothing else, it will undo any changes you made with root access and put everything back the way it was.
|
||||
|
||||
So as a cure-all in most soft brick situations, or as a method for getting the core part of an Android update, type:
|
||||
|
||||
* **fastboot flash system <system file name>.img**
|
||||
|
||||
Finally, there's the _vendor_ image. This is only present on newer phones, so don't worry if it's not in your factory images package. But if it's there, it contains a few important files, so type the following line to get this partition updated:
|
||||
|
||||
* **fastboot flash vendor <vendor file name>.img**
|
||||
|
||||
After you've sent any or all of the above commands, you'll be ready to restart your device and boot into Android. To do that, type:
|
||||
|
||||
* **fastboot reboot**
|
||||
|
||||
[
|
||||
|
||||
][11]
|
||||
|
||||
Flashing the factory images individually.
|
||||
|
||||
At this point, your device should be fully updated, or if you were trying to recover from a soft brick, it should be running flawlessly. And since you now know what each of the core system images actually _does_, you'll have a better sense of how Android works going forward.
|
||||
|
||||
Flashing factory images individually has helped me understand more about Android than any other mod or process. If you think about it, Android is just a series of images written to flash storage, and now that you've dealt with each of them individually, you should be able to identify and resolve root-related issues a lot easier.
|
||||
|
||||
* Follow Gadget Hacks on [Facebook][20], [Twitter][21], [Google+][22], and [YouTube][23]
|
||||
* Follow Android Hacks on [Facebook][24], [Twitter][25], and [Pinterest][26]
|
||||
* Follow WonderHowTo on [Facebook][27], [Twitter][28], [Pinterest][29], and [Google+][30]
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://android.wonderhowto.com/how-to/complete-guide-flashing-factory-images-using-fastboot-0175277/
|
||||
|
||||
作者：[ Dallas Thomas][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 组织编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://creator.wonderhowto.com/dallasthomas/
|
||||
[1]:http://img.wonderhowto.com/img/original/95/62/63613181132511/0/636131811325119562.jpg
|
||||
[2]:http://img.wonderhowto.com/img/original/12/37/63615501357234/0/636155013572341237.jpg
|
||||
[3]:http://img.wonderhowto.com/img/original/42/51/63613181192903/0/636131811929034251.jpg
|
||||
[4]:http://img.wonderhowto.com/img/original/06/56/63613181203998/0/636131812039980656.jpg
|
||||
[5]:http://img.wonderhowto.com/img/original/53/86/63613181215032/0/636131812150325386.jpg
|
||||
[6]:http://img.wonderhowto.com/img/original/55/72/63613181234096/0/636131812340965572.jpg
|
||||
[7]:http://img.wonderhowto.com/img/original/81/31/63616200792994/0/636162007929948131.jpg
|
||||
[8]:http://img.wonderhowto.com/img/original/05/92/63616201348448/0/636162013484480592.jpg
|
||||
[9]:http://img.wonderhowto.com/img/original/58/38/63616206141588/0/636162061415885838.jpg
|
||||
[10]:http://img.wonderhowto.com/img/original/47/26/63616206657885/0/636162066578854726.jpg
|
||||
[11]:http://img.wonderhowto.com/img/original/31/31/63616269700533/0/636162697005333131.jpg
|
||||
[12]:http://android.wonderhowto.com/how-to/know-your-android-tools-what-is-fastboot-do-you-use-it-0155640/
|
||||
[13]:http://gs6.wonderhowto.com/how-to/unroot-restore-samsung-galaxy-s6-back-stock-0162155/
|
||||
[14]:http://android.wonderhowto.com/how-to/android-basics-install-adb-fastboot-mac-linux-windows-0164225/
|
||||
[15]:https://developers.google.com/android/images
|
||||
[16]:http://www.htc.com/us/support/rom-downloads.html
|
||||
[17]:https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone%2Fbootloader%2Frecovery-images
|
||||
[18]:http://android.wonderhowto.com/how-to/android-basics-enable-developer-options-usb-debugging-0161948/
|
||||
[19]:http://www.7-zip.org/download.html
|
||||
[20]:http://facebook.com/gadgethacks/
|
||||
[21]:http://twitter.com/gadgethax
|
||||
[22]:https://plus.google.com/+gadgethacks
|
||||
[23]:https://www.youtube.com/user/OfficialSoftModder/
|
||||
[24]:http://facebook.com/androidhacksdotcom/
|
||||
[25]:http://twitter.com/androidhackscom
|
||||
[26]:https://www.pinterest.com/wonderhowto/android-hacks-mods-tips/
|
||||
[27]:http://facebook.com/wonderhowto/
|
||||
[28]:http://twitter.com/wonderhowto/
|
||||
[29]:http://pinterest.com/wonderhowto/
|
||||
[30]:https://plus.google.com/+wonderhowto
|
||||
[31]:http://android.wonderhowto.com/news/big-android-dictionary-glossary-terms-you-should-know-0165594/
|
||||
[32]:http://android.wonderhowto.com/news/big-android-dictionary-glossary-terms-you-should-know-0165594/
|
||||
[33]:http://android.wonderhowto.com/how-to/android-basics-what-is-root-0167400/
|
||||
[34]:http://android.wonderhowto.com/news/big-android-dictionary-glossary-terms-you-should-know-0165594/
|
||||
[35]:http://android.wonderhowto.com/how-to/know-your-android-tools-what-is-adb-do-you-use-it-0155456/
|
||||
[36]:http://tag.wonderhowto.com/odin/
|
||||
[37]:http://android.wonderhowto.com/news/big-android-dictionary-glossary-terms-you-should-know-0165594/
|
||||
[38]:http://android.wonderhowto.com/news/psa-enable-hidden-setting-before-modding-anything-android-0167840/
|
||||
[39]:http://android.wonderhowto.com/how-to/android-basics-tell-what-android-version-build-number-you-have-0168050/
|
||||
@ -0,0 +1,255 @@
|
||||
The Complete Guide to Flashing Factory Images Using Fastboot
|
||||
==========
|
||||
|
||||
|
||||
|
||||
如果你的手机有一个没有解锁的 [bootloader][31] 的话，你可以用 [Fastboot][32] 命令来刷入出厂镜像。听起来这好像是外行弄不懂的东西，但是当你需要升级被 [root][33] 过的设备，修理坏掉的手机，恢复到原生系统，或者是比别人更早的享受 Android 更新时，它可是最好的办法。
|
||||
|
||||
和 [ADB][35] 类似，Fastboot 是一个强大的 Android 命令行工具。这听起来可能会很恐怖 —— 别担心，一旦你了解了它，你就会知道Android的内部工作原理，以及如何解决最常见的问题。
|
||||
|
||||
### 关于三星设备的注释
|
||||
|
||||
下面的指南对于大多数 Nexus, Pixel, HTC, 以及 Motorola 等众多厂商的手机和平板电脑都适用。但是，三星的设备有自己的刷机软件，所以你的 Galaxy 设备并不支持 Fastboot。对于三星的设备，最好使用 [Odin][36] 来进行刷机工作，我们在下文的链接中提供了相关指南。
|
||||
|
||||
### 第一步 在你的电脑上安装 ADB 和 Fastboot
|
||||
|
||||
首先，你需要在你的电脑上安装 ADB 和 Fastboot，只有有了它们你才能使用 Fastboot 命令刷入镜像。网上有不少 “一键安装版” 或者 “绿色版”的 ADB 和 Fastboot，但是我不建议安装这样的版本，它们没有官方版本更新频繁，所以可能不会适用于新版设备。
|
||||
|
||||
你最好选择安装 Google 的 Android SDK Tools。这才是“真正的' ADB 和 Fastboot。安装 SDK Tools 可能需要一点时间，不过这等待是值得的。在下面的 _方法 1_ 中，我会说明在 Windows, Mac,以及 Linux 中安装这个软件的方法，所以在这里我们先讲后续的工作。
|
||||
|
||||
|
||||
### 第二步 解锁 bootloader
|
||||
|
||||
为了能够使用 Fastboot 刷入镜像，你需要解锁你设备的 [bootloader][37]。如果你已经解锁，你可以跳过这步。
|
||||
|
||||
如果你的设备的 Android 版本在 6.0 以上的话，在你解锁 bootloader 之前，你还[需要开启一项设置][38]。首先你需要**开启开发者选项**。开启之后，进入"开发者选项菜单"，然后开启 “OEM 解锁” 选项。之后就可以进行下一步了。
|
||||
|
||||
[
|
||||
|
||||
][1]
|
||||
|
||||
如果你的设备没有这个选项，那么你的设备的 Android 版本可能不是 6.0 以上。如果这个选项存在但是是灰色的，这就意味着你的 bootloader 不能解锁，也就是说你不能使用 Fastboot 给你的手机刷入镜像。
|
||||
|
||||
### 第三步 进入 Bootloader 模式
|
||||
|
||||
在使用 Fastboot 软件之前，你还需要让你的设备进入 bootloader 模式。具体进入方式与你的设备有关。
|
||||
|
||||
对于大多数手机，你需要先完全关闭你的手机。在屏幕黑掉以后，同时按住开机键和音量下键大约 10 秒。
|
||||
|
||||
如果这不起效的话，关掉手机，按住音量下键。然后把手机连到电脑上，等上几秒钟。
|
||||
|
||||
如果还不起效的话，改按音量上键，再试试第二种方法。
|
||||
|
||||
很快你就会看见像这样的 bootloader 界面：
|
||||
|
||||
[
|
||||
|
||||
][2]
|
||||
|
||||
看到这个界面之后，确保你的设备已经连接到电脑上。之后的工作就都是在电脑上完成了，把手机放在那里就成。
|
||||
|
||||
### 第四步 在你的电脑上为 ADB 打开一个命令行窗口
|
||||
|
||||
转到 ADB 和 Fastboot 的安装目录。对于 Windows 用户来说，这目录通常是 _C:\Program Files (x86)\Android\android-sdk\platform-tools_ 对于 Mac 和 Linux 用户则取决于你设定的安装位置，如果你忘了的话，就在硬盘里搜索 _platform-tools_。
|
||||
|
||||
在此之后，如果你使用 Windows 的话，按住右侧的 Shift 键，在文件管理器的空白处单击右键，然后选择“在此处开启命令行窗口”。如果你用的是 Mac 或者 Linux 那么你仅仅需要打开一个终端，然后转到 _platform-tools_ 下。
|
||||
|
||||
[
|
||||
|
||||
][3]
|
||||
|
||||
### 第五步 解锁 bootloader
|
||||
|
||||
这一步你仅仅需要做一次，如果你的 bootloader 已经解锁，你可以直接跳过这步。否则你还需要运行一条命令 —— 注意，这条命令会**清空你设备上的数据**。
|
||||
|
||||
在输入命令之前，我需要说明下，下面的命令仅仅对 Windows 适用，Mac 用户需要在命令前加上一个句号和一个斜线(**./**)，Linux 用户则需要加上一个斜线(**/**)。
|
||||
|
||||
所以，在 ADB Shell 里输入如下命令，然后按下回车键。
|
||||
|
||||
* **fastboot devices**
|
||||
|
||||
如果程序输出了以 fastboot 结尾的一串字符，那就说明你的设备连接正常可以继续操作。如果没有的话，回到第一步，检查你的 ADB 以及 Fastooot是否正确安装，之后再确定设备是否正确地连到了电脑上。
|
||||
|
||||
[
|
||||
|
||||
][4]
|
||||
|
||||
之后，解锁你的 bootloader。因为 Android 版本的差别，我们有两种方法来解决这个问题。
|
||||
|
||||
如果你的设备的 Android 版本是 5.0 或者更低版本 ，输入如下命令：
|
||||
|
||||
* **fastboot oem unlock**
|
||||
|
||||
如果你的 Android 版本高于 6.0 的话，输入如下命令，然后按下回车：
|
||||
|
||||
* **fastboot flashing unlock**
|
||||
|
||||
[
|
||||
|
||||
][5]
|
||||
|
||||
>将解锁命令发送到 6.0 或者更高版本的 Android 手机上
|
||||
|
||||
在这时，你的 Android 手机会问你是否确定要解锁 bootloader。确定你选中了 “Yes” 的选项，如果没有，使用音量键选中 “Yes”。然后按下电源键，你的设备将会开始解锁，之后会重启到 Fastboot 模式。
|
||||
|
||||
[
|
||||
|
||||
][6]
|
||||
|
||||
Nexus 6P 上的解锁菜单。图像来自 Dallas Thomas/Gadget Hacks
|
||||
|
||||
### 第六步 下载出厂镜像
|
||||
|
||||
现在你的 bootloader 已经解锁。你还需要把你从你的设备厂商下载下来的镜像解压。我推荐 **[7-Zip][19]** 它是免费的，支持大多数格式。
|
||||
|
||||
[
|
||||
|
||||
][7]
|
||||
|
||||
解压出厂镜像
|
||||
|
||||
下一步，把压缩包中内容移动到 _platform-tools_ 文件夹。之后在这里打开一个命令行窗口。要得到更多信息，请看第四步。
|
||||
|
||||
[
|
||||
|
||||
][8]
|
||||
|
||||
移动到 platform-tools 的文件
|
||||
|
||||
你有两种刷入镜像的方法。我会在下文分开叙述。
|
||||
|
||||
### 方法一
|
||||
|
||||
大多数出厂镜像都会包含一个 "flash-all" 脚本可以让你一条命令就完成刷机过程。如果你试图让你的黑砖回复正常的话，这是最简单的方法。但是这会让你的手机回到未 root 的状态并会擦除所有数据，如果你不想这样的话，请选择方法二。
|
||||
|
||||
如果要运行 "flash-all" 脚本，输入如下命令，之后敲下回车：
|
||||
|
||||
* **flash-all**
|
||||
|
||||
[
|
||||
|
||||
][9]
|
||||
|
||||
运行 "flash-all" 命令
|
||||
|
||||
这需要一点时间，当这步完成之后，你的手机应当自动重启，你可以享受 100% 原生固件。
|
||||
|
||||
### 方法二 手动解压刷入镜像
|
||||
|
||||
你可以手动刷入系统镜像。这么做需要额外的工作，但是它可以不清除数据的情况下反 root，升级设备，或者救回你的砖机。
|
||||
|
||||
首先解压出厂镜像包中的所有压缩文件。通常压缩包里会包含三到四个压缩包，确认你已经解压了所有的压缩文件。之后把这些文件移动到 _platform-tools_ —— 或者说，别把他们放到子文件夹下。
|
||||
|
||||
[
|
||||
|
||||
][10]
|
||||
|
||||
|
||||
解压后的所有文件
|
||||
|
||||
在这些文件里，有两个镜像是可以直接删除的： _cache.img_ 和 _userdata.img_。就是这两个文件清除了你的设备数据，如果你不刷入这两个镜像，你的数据就不会消失。
|
||||
|
||||
在剩下的文件中，有六个镜像构成了 Android 的核心部分： _boot_, _bootloader_, _radio_, _recovery_, _system_, 和 _vendor_。
|
||||
|
||||
_boot_ 镜像包含了内核，如果你想要换掉一个不太好用的自制内核的话，你仅仅需要刷入这个文件。通过键入如下命令完成工作：
|
||||
|
||||
* **fastboot flash boot <boot image file name>.img**
|
||||
|
||||
下一个就是 _bootloader_ —— 也就是你用来刷入镜像的界面。如果你要升级的话，输入如下命令：
|
||||
|
||||
* **fastboot flash bootloader <bootloader image file name>.img**
|
||||
|
||||
做完这步之后你就可以用新版的 bootloader 刷入镜像。要想如此，输入：
|
||||
|
||||
* **fastboot reboot-bootloader**
|
||||
|
||||
之后就是 _radio_ 镜像。这个镜像和你设备的网络连接有关，如果你手机的 Wi-Fi 或者移动数据出现了毛病。或者你仅仅想升级你的基带固件，输入：
|
||||
|
||||
|
||||
* **fastboot flash radio <radio image file name>.img**
|
||||
|
||||
然后就是 _recovery_。你可以自由选择是否刷入这个镜像，如果你已经刷入 TWRP 的话，刷入这个镜像会恢复到原生 recovery。如果你仅仅要升级你的已经被修改过的设备，你就可以跳过这步。如果你想要新版的原生 recovery ，键入：
|
||||
|
||||
* **fastboot flash recovery <recovery file name>.img**
|
||||
|
||||
下一个可是个大家伙：_system_ 镜像，它包含了 Android 系统所需的全部文件。它是升级过程中最重要的部分。
|
||||
|
||||
如果你不想升级系统仅仅是要换回原生固件或者是救砖的话，你只需要刷入这个镜像，它包含了 Android 的所有文件。换言之，如果你仅仅刷入了这个文件，那你之前对这个设备做的修改都会被取消。
|
||||
|
||||
作为一个救砖的通用方法，以及升级 Android 的方法，键入：
|
||||
|
||||
* **fastboot flash system <system file name>.img**
|
||||
|
||||
最后，就是 _vendor_ 镜像。只有新版的设备才包含这个包。没有的话也不必担心，不过如果有这个文件的话，那它就包含了一些重要的文件，键入如下命令使其更新：
|
||||
|
||||
* **fastboot flash vendor <vendor file name>.img**
|
||||
|
||||
在这之后，你就可以重新启动设备：
|
||||
|
||||
* **fastboot reboot**
|
||||
|
||||
[
|
||||
|
||||
][11]
|
||||
|
||||
手动刷入出厂镜像
|
||||
|
||||
至此，你的设备已经完全更新，如果你是救砖的话，你的手机应该已经完好的运行。如果你知道每个系统镜像怎么是干什么的话，你就会更好的理解 Android 是怎么运行的。
|
||||
|
||||
手动刷入镜像比做任何修改已经帮助我更多地理解了 Android。你会发现，Android 就是写进存储设备里的一堆镜像，现在你可以自己处理他们，你也能更好的处理有关 root 的问题。
|
||||
|
||||
* 在[Facebook][20], [Twitter][21], [Google+][22], 以及 [YouTube][23] 关注 Gadget Hacks
|
||||
* 在 [Facebook][24], [Twitter][25], 和 [Pinterest][26] 上关注 Android Hacks
|
||||
* 在 [Facebook][27], [Twitter][28], [Pinterest][29], 还有 [Google+][30] 上关注 WonderHowTo
|
||||
|
||||
|
||||
|
||||
|
||||
via: http://android.wonderhowto.com/how-to/complete-guide-flashing-factory-images-using-fastboot-0175277/
|
||||
|
||||
作者：[ Dallas Thomas][a]
|
||||
译者：[name1e5s](https://github.com/name1e5s)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 组织编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://creator.wonderhowto.com/dallasthomas/
|
||||
[1]:http://img.wonderhowto.com/img/original/95/62/63613181132511/0/636131811325119562.jpg
|
||||
[2]:http://img.wonderhowto.com/img/original/12/37/63615501357234/0/636155013572341237.jpg
|
||||
[3]:http://img.wonderhowto.com/img/original/42/51/63613181192903/0/636131811929034251.jpg
|
||||
[4]:http://img.wonderhowto.com/img/original/06/56/63613181203998/0/636131812039980656.jpg
|
||||
[5]:http://img.wonderhowto.com/img/original/53/86/63613181215032/0/636131812150325386.jpg
|
||||
[6]:http://img.wonderhowto.com/img/original/55/72/63613181234096/0/636131812340965572.jpg
|
||||
[7]:http://img.wonderhowto.com/img/original/81/31/63616200792994/0/636162007929948131.jpg
|
||||
[8]:http://img.wonderhowto.com/img/original/05/92/63616201348448/0/636162013484480592.jpg
|
||||
[9]:http://img.wonderhowto.com/img/original/58/38/63616206141588/0/636162061415885838.jpg
|
||||
[10]:http://img.wonderhowto.com/img/original/47/26/63616206657885/0/636162066578854726.jpg
|
||||
[11]:http://img.wonderhowto.com/img/original/31/31/63616269700533/0/636162697005333131.jpg
|
||||
[12]:http://android.wonderhowto.com/how-to/know-your-android-tools-what-is-fastboot-do-you-use-it-0155640/
|
||||
[13]:http://gs6.wonderhowto.com/how-to/unroot-restore-samsung-galaxy-s6-back-stock-0162155/
|
||||
[14]:http://android.wonderhowto.com/how-to/android-basics-install-adb-fastboot-mac-linux-windows-0164225/
|
||||
[15]:https://developers.google.com/android/images
|
||||
[16]:http://www.htc.com/us/support/rom-downloads.html
|
||||
[17]:https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone%2Fbootloader%2Frecovery-images
|
||||
[18]:http://android.wonderhowto.com/how-to/android-basics-enable-developer-options-usb-debugging-0161948/
|
||||
[19]:http://www.7-zip.org/download.html
|
||||
[20]:http://facebook.com/gadgethacks/
|
||||
[21]:http://twitter.com/gadgethax
|
||||
[22]:https://plus.google.com/+gadgethacks
|
||||
[23]:https://www.youtube.com/user/OfficialSoftModder/
|
||||
[24]:http://facebook.com/androidhacksdotcom/
|
||||
[25]:http://twitter.com/androidhackscom
|
||||
[26]:https://www.pinterest.com/wonderhowto/android-hacks-mods-tips/
|
||||
[27]:http://facebook.com/wonderhowto/
|
||||
[28]:http://twitter.com/wonderhowto/
|
||||
[29]:http://pinterest.com/wonderhowto/
|
||||
[30]:https://plus.google.com/+wonderhowto
|
||||
[31]:http://android.wonderhowto.com/news/big-android-dictionary-glossary-terms-you-should-know-0165594/
|
||||
[32]:http://android.wonderhowto.com/news/big-android-dictionary-glossary-terms-you-should-know-0165594/
|
||||
[33]:http://android.wonderhowto.com/how-to/android-basics-what-is-root-0167400/
|
||||
[34]:http://android.wonderhowto.com/news/big-android-dictionary-glossary-terms-you-should-know-0165594/
|
||||
[35]:http://android.wonderhowto.com/how-to/know-your-android-tools-what-is-adb-do-you-use-it-0155456/
|
||||
[36]:http://tag.wonderhowto.com/odin/
|
||||
[37]:http://android.wonderhowto.com/news/big-android-dictionary-glossary-terms-you-should-know-0165594/
|
||||
[38]:http://android.wonderhowto.com/news/psa-enable-hidden-setting-before-modding-anything-android-0167840/
|
||||
[39]:http://android.wonderhowto.com/how-to/android-basics-tell-what-android-version-build-number-you-have-0168050/
|
||||
Loading…
Reference in New Issue
Block a user