Sees the phone in fastboot mode. Download and install ADB, drivers and Fastboot

Need to flash Android using FastBoot, but don't know how? This article provides detailed instructions on using the FastBoot utility and how to use it to flash an Android device.

This manual will fully explain how to use FastBoot! If you don’t know how to install archived updates, then you need the article - Clockwordmod - what is it. Instructions for CWM recovery with pictures

Downloading and installing FastBoot

Before flashing Android using FastBoot, you need to download it and install it on the desired computer.

1. You can download the FastBoot utility with the official Android SDK program (heavy weight)

why ADB RUN is better

Launch

If you downloaded Separately Fastboot

After you have downloaded and installed FastBoot, open the " Command line »

and vve Enter the commands to go to the folder with the Fastboot utility (if you installed separately FastBoot)

cd/
cd adb

If you downloaded ADB RUN

If your choice fell on the ADB RUN program, then launch it and select Manual -> ADB from the menu

The files that need to be flashed must be located in the same folder as the Fastboot utility

Instructions for commands on how to flash Android using FastBoot

It is very important to write commands and firmware files as they are specified!

If your command is specified

fastboot flash cache NazvaniAFiLe.img

then you need to write exactly like that, but not any other way. In other words, the case of letters is important, otherwise you will get an error cannot load 'image' - there is no such file.

Reboot commands into firmware mode (bootloader)

fastboot reboot-bootloader

The command "sees" your Android PC

Get into the habit of checking before doing anything in Fastboot if the connection between your computer and Android is:

Checking whether your PC can see your Android

fastboot devices

Execute this command when the device is already in firmware mode (bootloader)

Nexus Bootloader Unlock and Lock Commands

Unlock bootloader for Nexus

fastboot oem unlock

Lock bootloader for Nexus

fastboot oem lock

Command to find out bootloader version

Shows the bootloader version number installed on Android

fastboot getvar version-bootloader

Partition formatting commands

Before flashing any partition in Android, you must first format it so that there are no problems with operation

fastboot erase Imya_razdela - erase partition: boot, radio, recovery, system, userdata and others

Erases the Cache partition

fastboot erase cache

Erases the Data section

fastboot erase userdata

Erases the System partition

fastboot erase system

Erases the Recovery partition

fastboot erase recovery

Commands for flashing a partition

After you have formatted the partition or partitions, you can start flashing the firmware

fastboot flash Imya_razdela imya_file.img - firmware of the selected partition: boot, radio, recovery, system, userdata and others

Flash the system partition (System)

fastboot flash system imya.img

Flash the cache partition

fastboot flash cache imya.img

Flash the data section

fastboot flash userdata imya.img

Flash the Recovery partition

fastboot flash recovery imya.img

Setting the power-on animation (firmware partition with animation)

fastboot flash splash1 splash.img

Flash all partitions (boot, recovery and system)

fastboot flashall

Instead of imya.img- you need to enter the name of the file you are going to flash

Command to install update.zip

Flashes an update archive on Android in update.zip format or a ZIP archive with IMG images of various sections

fastboot update filename.zip

For Sony devices

Checking the connection of the Sony device, if the answer is 0.3 device, then it is connected

fastboot.exe -i 0x0fce getvar version

Unlock bootloader

fastboot.exe -i 0x0fce oem unlock 0xReceived_Key

More detailed information on unlocking Bootloader Sony - How to unlock Bootloader Sony

Waiting for Device error

If you have the following message on in the command window for a long time: waiting for device- Means:

The driver is not installed or installed incorrectly - reinstall or install
Android device is not in Bootloader mode - translate
Incorrect connection to the USB port - use the rear USB 2.0 ports of the computer, do not use USB hubs

Many of us are already familiar with ADB (Android Debug Bridge), since, as the owner of an Android device, quite often we have to perform such simple actions as adb push And pull, or adb reboot etc. But for many novice users, just the sight of the command line is already scary, and it seems prohibitively possible. Although in fact everything is quite simple, experienced users will not let me lie, and the biggest difficulty is to remember all these commands, although this is not necessary to do either, since the Internet is always at hand and finding the right command is not difficult.

Android Debug Bridge, which is part of the Android SDK emulator, allows you to communicate between your computer and an Android device connected to it. By the way, if you need some software, you can download the programs for your laptop for free here. What can I do with ADB? Its capabilities are quite wide, for example, the most popular actions: copy files from an Android device to a computer, upload files from a computer to Android, execute many Linux commands, receive error reports, etc.

So if you're new to this and want to learn a little more about ADB than just what it is, then I suggest you check out my little basic guide to learning ADB.

What you will need

1. Android Debug Bridge (ADB) for Windows 32bit - download

2. Android Debug Bridge (ADB) for Windows 64bit - download

3. Computer with Windows OS installed.

Now let's move on to the active phase:

1. Download the required zip archive and extract it wherever you want, for example, drive C.

2. Now go to the directory C:/adb/sdk/platform-tools. Here you will find a set of files as shown in the image below.

3. Hold down the Shift button + right-click and launch the Windows command line from the current directory.

4. Enter the command adb start-server.

5. To make sure that your device is connected correctly and has been recognized by the computer, enter the command: adb devices. If all is well, you will see something similar to this:

Now that your device is connected and everything is working, let's play with it a little.

Reading LOGCAT via ADB

The easiest way is to run the command: adb logcat. As a result, the entire contents of the device log file will appear on the screen. To get logcat in a separate file run: adb logcat > logcat.txt.

BUGREPORT

You can run the command: adb bugreport, but you will receive a notification that the generated report will not be readable, so it is better to use: adb bugreport >result.txt.

ADB together with ROOT access rights

To work from ADB with full access rights, you need to root the device. If the device is already manual, then run the command: adb root and we see what is shown in the picture below (reboot ADB with root rights).

Installing applications via ADB

To install the application, make sure that there are no spaces in the apk file name and you need to know exactly the correct path to it. Well, then we run the command: adb install+ name of the installation file. In my example, I installed the papertoss game, so if everything goes well, you will get this picture on the screen:

Hello friends. Today, we can say, a spontaneous post happened, what it will be about, you could already guess from the title. The thing is that just today a parcel arrived from the USA, and I became the owner of a brand new Google LG Nexus 4. And now I have two Nexuses at once - Samsung Galaxy Nexus and LG Nexus 4 - maybe I’ll even write a comparison review, if you're interested, but that's not what we're talking about today.
Yes, who cares, and I’m sure that many – the issue price is 12k rubles with delivery! But again, that’s not what I’m talking about...

Yes, Pure Android 4 is wonderful in itself - convenient, fast and almost perfect. Please note that I am talking specifically about the android that is installed in Nexus Google phones, and not all other phones (htc, Samsung, sony, etc.), because... they have been seriously reworked and changed, unfortunately, not for the better. So what could be better than almost perfect firmware? Improved custom firmware, of course!

So today I turned on the phone for the first time just to make sure it worked at all. When I was convinced of this, I turned it off and started “dancing with a tambourine.” Hot on the heels, I’ll tell you how to unlock Bootloader on Nexus 4, install recovery and flash any firmware.

In fact, all these dances with a tambourine are not such dances and even almost not with a tambourine =) I, as an already experienced user, felt confident, did not worry and did not even make any backups. As it turned out, all the procedures described below are completely identical to the procedures that I did a year ago on the Galaxy Nexus. Everything will be simple, I promise!

First you need to prepare a little and download the necessary drivers:
Download the drivers usb_driver.rar - they will be useful for connecting the device in bootloader mode to our PC. We also download the adb.rar archive – it contains Fastboot and ADB files.

Unpack the Fastboot and ADB archive to the root of drive C, it should look like C:\adb.
We also unpack the drivers to the root of drive C, it will turn out to be C:\usb_driver.

Now into battle!

Installing drivers and unlocking Bootloader in LG Nexus 4

First you need to unlock Bootloader, without this nothing can be done.

There are various solutions and even programs that allow you to unlock, get root and install recovery in one click, but I somehow don’t trust this approach, because the procedure is delicate. Although I still tried to use the NEXUS 4 TOOLKIT 1.3 program today, but, as it turned out, you can only download the basic version, and the update is available only after payment, and without the update the choice of android 4.2.2 support is not available. In short - not our option!

Three simple steps and no show-offs:

It's simple, right?

Installing custom recovery on LG Nexus 4

Now we need to install recovery, without which we simply will not be able to flash firmware, kernels and any tweaks and mods.

For recovery, I recommend TWRP Team Win Recovery Project. You can view the description and features on XDA in the official topic for NEXUS 4, there is always the current version there. At the time of writing this post, the newest version is 2.4.4.0. Here is a convenient direct download link. Have you downloaded it? Great, let's move on.

We have a file openrecovery-twrp-2.4.4.0-mako.img. If you put it in the c:\adb folder and rename it twrp.img it will be easier in the next step.

Well, the bootloader is unlocked, recovery is installed. The simplest thing left is to install new firmware. By the way, we don’t need to get root if we are going to install custom firmware, root will already be there by default.

Installing custom firmware on LG Nexus 4

For almost a year of using my previous Samsung Galaxy Nexus, I tried a whole bunch of different firmware, often reflashed it, and conducted all sorts of experiments. And you know, one day I found the ideal firmware, the firmware of my dreams - this is ParanoidAndroid. I simply cannot recommend anything else other than this firmware. But, one way or another, the choice is yours; the procedure for installing different firmware is identical.

This is what your Nexus 4 might look like after installing ParanoidAndroid:

Here is a video review of the same firmware, but for those who have not personally used ParanoidAndroid, little will be clear:

So, we have decided on the firmware, we need to download it. Official topic for firmware developers, there is also a description, links and new versions. You can download the firmware itself in the mako section on goo.im, and you will also need to download Google Apps in the corresponding section on goo.im.

We downloaded the firmware and gapps, now we need to somehow upload them to the phone. If the phone is normally visible in the explorer, then skip the block of text below; if you can’t get into the phone’s memory through the explorer, then read.

A small snag may arise here, but only if you do not read this post - because all the snags are resolved for me, and I will definitely write about it!

I’m sitting and connecting the phone via USB using a cable, but it’s charging, but in the explorer I can’t see it as a folder to put our archives there for the firmware. If you have the same story, then here is the solution!

I don’t know why, but Windows decided to install ADB drivers when the phone was turned on (this does not mean fastboot, but the running android system). Maybe I did something wrong somehow, but the fact is the fact - the phone folder is not visible in Explorer. I thought that some drivers were missing, I Googled for a long time, but found nothing. I decided to use the harsh method: We go to the device manager, we see “Android device something like ADB” - just right-click on it and select Delete. We disconnect the phone and immediately connect it back - Windows should re-detect the device and install the correct drivers on it. This worked for me and the required Nexus 4 folder appeared in Explorer!

Select the folder Nexus 4 / Internal memory / Download and drop the archives there, in my case it’s pa_mako-3.10-11MAR2013-131748.zip and pa_gapps-full-4.2-20130308.zip. In your case, these will be newer versions; it’s not at all difficult to understand the markings.

When all the archives are downloaded, disconnect the phone from the computer and turn it off. We need to get into recovery mode again, to do this we hold down Volume Down + Power until fastboot turns on, where we use the volume buttons to select Recovery mode and press Power.

If it suddenly happened that you didn’t see the main screen of TWRP (it’s very easy to identify, there will be no doubt about it), but you saw an android lying on its back with a red triangle, then there is a way out, but what would you do without it?

To do this, hold down the Power button until the phone turns off. We boot into fastboot again, connect the phone via USB and repeat the recovery installation script. When the recovery is installed, do not reboot, but use the volume buttons to find the Recovery mode item and select it with the power button. Now TWRP will definitely start, which means we follow the instructions below.

We will see the main screen of TWRP, click on the top right Wipe button, and then Factory Reset - this will delete all data on the phone!

After a complete reset, you need to return to the previous screen and click on the upper left Install button. On the screen that opens, select Download from the list of folders, and then first click on the pa_mako firmware file, then Add More Zips and immediately select the pa_gapps file and finally do Swipe to Confirm Flash. Now both the firmware and Google Apps applications will be flashed immediately, about a minute of waiting and we should see the inscription Successful. It is very important to clear all caches; to do this, select the Wipe cache/dalvik button. Everything is ready - click Reboot System.

Now the system will boot, but with the ParanoidAndroid firmware. After a long download, we find ourselves in the initial phone setup menu, where you need to select a language, specify an account, etc.

Actually that's all! Good luck to you friends. If you have any questions or suggestions about the firmware process or about ParanoidAndroid, please write in the comments.

Note: How to access the developer menu on any firmware.

Open the settings, select the “About phone” item at the very bottom, scroll the screen to the “Build Number” item, it will say JDQ39, which corresponds to android version 4.2.2, you may have something else written, it doesn’t matter. Press this line 7 times in a row. As a result, the message “You have become a developer!” should appear. It turns out how easy it is to become a developer for androind =))) We return back to the settings menu, we see a new item “For Developers”.

UPD: If suddenly the phone turns into a “brick” - what should you do?

You never know what happens... Like today, for example, a colleague bought himself the same Nexus 4 and gave it to me so that I could install custom firmware. “No problem,” I said and went to follow my own instructions written above. A strange thing happened - all the data (zip file of the firmware image, for example), which I uploaded to the internal drive for subsequent firmware after the reset, they were deleted, self-destructed for some unknown reason.

In short, the phone turned into a brick, i.e. It won’t turn on, but something needs to be done. Therefore, the easiest way is to download Factory Image to your phone, i.e. factory image so that the phone looks like what you saw when you first opened the package. And here are the instructions:

It is assumed that you have already installed the drivers and the phone connects to the computer when it is in fastboot mode. And also the bootloader is unlocked. In short, all the steps under the heading “Installing drivers and unlocking” have been completed.
Now download the official image of the phone from here https://developers.google.com/android/nexus/images#occam At the moment, the current version is 4.3 (JWR66V), click Link opposite and download.
We downloaded the archive occam-jwr66v-factory-08d2b697.tgz, inside it is another archive occam-jwr66v-factory-08d2b697.tar, and inside there are several files and another archive image-occam-jwr66v.zip - this is what we need needed, take and transfer image-occam-jwr66v.zip to the folder C:\adb
Open the command line and write:
cd c:\adb press Enter;
fastboot erase boot press Enter;
fastboot erase cache press Enter;
fastboot erase system press Enter;
fastboot erase userdata press Enter;
fastboot reboot-bootloader press Enter;
fastboot -w update image-occam-jwr66v.zip press Enter and wait.
After the last operation, the phone should reboot itself and turn on.
Now your phone is like new :) And you can repeat what didn’t work. Namely, upload zip archives to the phone’s memory and try to flash them again. By the way, we didn’t touch recovery during the recovery process, so you still have TWRP, which means turn off the phone, press Volume Down + Power, select recovery and go!

Well, now that’s all for sure!

See you later, friends. And I’m sorry that I stopped writing about SEO often, I promise to improve in the near future.