> Attention!

We strongly recommend to readRules section "Android - firmware"

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Google Galaxy Nexus - Firmware



Rep: (654)
Google Galaxy Nexus - Firmware
PictureSamsung Galaxy Nexus, Samsung GT-I9250
Description | Discussion | Games | FAQ | Purchase | Accessories | Firmware | Marriage | Embellishments | LineageOS | Slim bean | Paranoid Android | MIUI | Ubuntu os | Google nexus club

Important information!
Attention: There is an oral statement of Samsung SC that using programs that create a swapfile (swap file) on our device using internal memory may result in its failure.
Also, personally from myself, I do not recommend formatting the system in f2fs. Too often there are messages about memory problems after this action.
"Why only me without JellyBean 4.3?"
Dear user, if you are faced with this problem, do not panic. Just follow the following points:

    1. You need to know the name of our update provider. (There are several ways to choose from how to do this)
    a) Supplier information is contained in Google Maps.Settings->About the program->Device
    b) You can download and install the utilityGN Official Update Checker.
    c) Or you can useQuadrant standart. Go toSystem informationand see what is written next toProduct(thankDRULEZZZ )
    2. You learned the name of the supplier, namely) If the program displays the word"yakju" or "takju" then try speed up getting updates .b) If the program displays not yakju , you should set 4.3 yourself. How to do it - spoiler "Instructions" In the future, all updates will come through the air and put themselves with your permission.
Question: What isyakjuand why is everything so confusing? Answer: Galaxy Nexus phones get updates either from Google directly or from Samsung. yakju - This is a phone marking, indicating that it receives updates directly from Google, all other words (derived from yakju , eg yakjuxw ) denote getting updates from Samsung. However, Samsung for some reason rolls out the firmware much later than Google. Question: Does the update somehow depend on the place of purchase (PCT or gray)? Answer: Not. It doesn't matter where the device was purchased or even made.
Drivers and Utilities
Instructions
Basic instructions:
  1. Instructions for beginners, including:
    • Unlocking bootloader;
    • Getting a root;
    • Installing custom recovery;
    • Change the update provider;
    • Return to the factory state on any version of the firmware;
    • Manual upgrade to any firmware version.
  2. Installing the official image without erasing data (for example, 4.2, the bootloader is already open)
  3. Change vendor with Nexus Root Toolkit
  4. One-click recovery installation
  5. Full backup / system recovery for non-rooted devices with a blocked bootloader
  6. ADB Backup - Myth or Reality? (backup of user data)
  7. Installing third-party firmware / kernel / radio module / modification.
  8. Firmware backup of the official image via CWM
  9. Install OTA update
  10. Working with the Galaxy Nexus Toolkit (for example, v7.8)
  11. Route + twrp_2.3.2.1 recovery + off-firmware 4.2.1 in one click
  12. Dual boot instruction (Android + Android, Android + Ubuntu Touch)
  13. Formatting memory in f2fs
Other instructions:
  1. Add paths to adb and fastboot utilities in Path (access via command line from any directory)
  2. Recovery of the killed bootloader
  3. Accelerate the creation / restoration of nandroid backup in CWM
  4. Processor Undervoltage Information
  5. Create IMEI backup
  6. Repair IMEI
  7. Repair IMEI from backup
  8. SIM Unlock Application
  9. IMEI Repairfromtrue-satan
  10. One of the options to restore the firmware after complete data cleaningfromalsamoy
Frequently used adb commands:
    More detailed list of ADB / Fastboot commands
  1. adb install<local>// Install the application from the computer. Only valid .apk
  2. adb push<local><remote>// Copy files from computer to phone. Any files allowed
  3. adb pull<remote><local>// Copy files from phone to computer. Any files allowed<local>- path to a file on a computer, for example c: androidgamesgame.apk<remote>- the path to the file on the phone, for example /sdcard/games/game.apk.What is highlighted in green, do not need to be entered into the command line / terminal!
Firmware catalog
Official firmware
Unofficial firmware
Attention! Many references to firmware 4.1.x-4.3.x are irrelevant. Links are left for review.
4.1 - 4.1.2
4.2 - 4.2.2
4.3
4.4
5.x.x
6.x.x
Google apps

Root
Stitch through CWM or TWRP
Attached fileUPDATE-SuperSU-v1.89.zip(1.13 MB)

(SuperSU for 4.2 is preferable)
Attached filesuperuser_3.0.7_elite_update.zip(733.84 KB)
Radio modules, bootloaders, kernels, recovery
Radio modules and bootloaders
Flash img images via Fastboot
The latest bootloader ->Attached filebootloader-maguro-primemd04.img(2.25 MB)

fastboot flash bootloader bootloader-maguro-primemd04.img
zip for recovery

The latest radio module is>Attached filexxlj1.img(12 MB)

fastboot flash radio xxlj1.img

The firmware of communication modules for GSM versions have several types. The most common:
  • UG - Canada and North America
  • XX- Europe
Before flashing, check your version of the radio module in the Settings - About phone menu
Full list of radio modules
Kernels
Recovery
Everything for cores
Utility
Reviews
Survey Screenshots
FAQ

K
There is no curator in the subject. If there is a user in the subject who wants to become a Curator and the correspondingRequirements for candidates, he can apply in the topicI want to be curator(after having studied the topic header and all materials for curators).
Prior to the appointment of the curator, on filling caps, please contactmoderatorssection through a buttonPictureunder the messages to which you want to add links.


Post has been editedSadowplay - 29.12.18, 20:49
Reason for editing: Stock kernel for 4.3 (JWR66Y) with TTL commit support



Rep: (607)
Instructions for beginners, including:
  • Unlocking bootloader;
  • Getting a root;
  • Installing custom recovery;
  • Change the update provider;
  • Return to the factory state on any version of the firmware;
  • Manual upgrade to any firmware version.


Galaxy Nexus Toolkit instructions (for example, v7.8)
Send suggestions / suggestions / comments on the manual to the LAN or QMS
Commands marked asdonate version, will not be considered for the lack of such a version with me

Preface and details
The Galaxy Nexus Toolkit program (hereinafter GN Toolkit or GNTK), developed by mskip (not one Toolkit for various phones behind it), is a very good helper in working with the phone. She can do a lot, and you don’t have to strain yourself to install firmware or recovery, get root, make backup and stuff. You just need to install this program, and everything else can be done with a couple of keystrokes.

Main features of the GN Toolkit:
  • Automatic installation of drivers for working with adb / fastboot on Windows xp / vista / 7 32bit + 64bit
  • Save to one file and restore all applications, user data and "external memory" (sdcard)
  • Saving all "external memory (sdcard) to a computer
  • Full NANDROID system backup (Boot, Cache, Data, Recovery, System) via adb for later recovery via CWM
  • Saving the / data and / system sections in .tar format to a computer
  • Saving / Restoring partition / efs to computer
  • Save specific sections in .zip format from md5 to computer
  • Install busybox
  • Various usefulness and tips (only for donators )
  • Automatic update when the program starts (only for donators )
  • Compiling a .tar file for Odin firmware
  • Modify your phone
  • Unlocking the bootloader, getting root, installing recovery (Stoke / CWM / TWRP) and preventing the gathering of custom recovery with one click
  • Unlock / Lock bootloader
  • Downloading official firmware from Google servers for installation
  • Installing the official firmware image
  • Getting root on any public version of the firmware
  • Renaming a file Recovery Recovery to prevent the replacement of custom recovery to stock
  • Installing Recovery (Stock / CWM / TWRP)
  • One-time download CWM / TWRP without installation
  • Installing or downloading the .img file directly from the computer
  • Installing .apk applications on the phone directly from the computer
  • Download files from computer to phone
  • Downloading files from phone to computer
  • Dump logcat to computer
  • Dump bugreport to computer
  • Editing access rights for files on the phone
  • Ability to save the radio image to a computer
  • Ability to save the image of the cache in a .zip file for CWM / TWRP
  • Command line for manual command entry
  • Restarting the phone to fastboot mode from the system or vice versa
  • Restarting the phone in fastboot mode, in the rack, in the system or download (Odin) mode
  • Enable / Disable the firmware selection screen the next time you start it.

First run (Select firmware)
Attached Image

The first thing we see when we turn on the GN Toolkit for the first time is a screen with information about enabling adb and updating.
We write "yes" - the GN Toolkit updates are checked.
Attached Image

This is what we see when we go through the screen with adb and update. What is this?
This is the firmware selection screen. You must select the firmware that you are currently using. Most likely you have a European GSM phone model, so you need to choose from points 1-7. Selecting the desired item moves to the main menu ...
The note: If you accidentally choose the wrong version, then do not worry. You will be able to return to this screensaver by restarting the program.
Main menu
Attached Image

This is what the GN Toolkit main menu looks like. Let's see what it consists of.

Serial number:
Attached Image

Each phone has its own unique serial number. On this screen, you see that under the item "ADB MODE", since the phone is loaded with a system with USB debugging enabled. The number under the item "FASTBOOT MODE" is currently absent, as the phone, as I said, is loaded in a different mode. But the numbers in Fastboot and ADB are identical - they are the same number.
On the right above you can see a note from the author “If serial shows, drivers are installed”, which translates as “If you see the serial number, then the drivers are installed correctly”. But it is worth noting that you will not see the number if the phone is not connected to the computer.

Firmware Version:
Attached Image

In this part of the main menu, we can see the version of the firmware that was chosen when the program was first launched. On the right, the program version is displayed: there are FREE and DONATE versions. In the second there are some features that are not available in the FREE version, we will talk about them later.

Commands:
Attached Image

And this is the main part of the main menu (hehe). Here we can choose the actions that the program must perform with the phone. There are a lot of them here, and we'll talk about each of them separately later.
It is necessary to pay attention to the fact that to the right of some commands are indicated the modes in which the phone must be located to execute these commands.

Entry field:
Attached Image

I think there is nothing to explain here. Here you enter the number of the command you want to execute.

Team # 1 - install / uninstall drivers for GN on computer
Attached Image

What you need to do in the very first place to work with the phone? Right! Install the driver on your computer.
Having chosen the first command, we see a lot of text in front of us and a choice of the version of the Operating System (installed on the computer, of course).

Read before you begin (a brief translation of the text in team # 1, above the choice of OS version):
This command will install adb / fastboot drivers for your Galaxy Nexus on your computer.
This must be done before you start working with the phone and execute various commands from the GN Toolkit.

You must have administrator rights to install drivers!
Make sure the phone is turned on (the system is loaded)!
Do not connect your phone via a USB cable until you install the driver!
After installing the adb drivers, you must load the phone into fastboot mode to install fastboot drivers.
If you have any other drivers installed, then remove them yourself before installing these.

OS version selection:
It is very simple. You know what your OS version is? Select point 1 or 2 and get into the choice of Install / Delete / Return to the first command screen.
Attached Image


If the automatic installation from points 1 or 2 did not work, then use point 3 to manually install
Team # 2 - Saving and Restoring Data
Attached Image

By selecting this command, we get to the screen for choosing to save and restore data on the phone.
All commands require enabled USB debugging!

Preservation:
1. Saving applications. This command has the ability to save only user applications, as well as system ones (not separately, together). There is also an option to save only data (without .apk) and data with .apk.
After you start the process of saving, a notification will appear on the phone about the execution of this action. You need to confirm the data is saved, the password is optional.

2. Saving a specific application. After selecting this item, a notebook will automatically open on your computer, with a list of installed applications. You need to choose one of them and copy its name exactly into the program.

3. Saving files with sdcard. This command will save all files located on the sdcard. After selecting this option, you will be asked if you are using a Custom ROM or unsecured boot image. If you just have a stock, then you answer no, the program will sew you a special kernel with the possibility of issuing administrator rights for adb.

4. NANDROID backup. This is a full backup of the system, for later recovery via CWM.

5. Saving the / data partition (excluding / data / media) to the computer. This section stores user data.

6. Save partition / system to computer. This section contains the firmware files.

7. Save / efs section. This section stores information about IMEI. It is recommended to keep this section, as there were cases when IMEI flew.

8. Save the radio image to the computer.

9. Saving selected partitions to a computer. Available sections:
Attached Image


Recovery:
10. Restore applications from the backup made by paragraph 1.

11. Restore sdcard files from backup made by clause 3.

12. Restore partition / efs.

13. Restore partition / factory.

14. Restoring the system from NANDROID backup via custom recovery (you need to install it yourself).
Team # 3 - Working With Bootloader
Attached Image

There is nothing to explain.
The first item is unlocking the bootloader.
The second is blocking the bootloader.
Team # 4 - Getting Root
Attached Image

A program without any screens with options immediately gets down to business, asking us one single question: is the phone loaded in fastboot mode or should the program do this?
After answering the question, the program will do everything itself. At the end, the phone will be loaded into fastboot mode, boot into the system yourself.
Team # 5 - If custom recovery flies
Attached Image

As in the previous team, we are immediately asked one question: is the phone loaded in fastboot mode or not?
This command is needed to prevent overwriting custom recovery.
It works only on rooted phones.
If the program has produced the error "failed - No such file or directory", then you can safely install custom recovery, despite this error.
Team # 6 - Installing Recovery (Stoke / CWM / TWRP)
Attached Image

This command will install you one of the three recovery. 1 - Clockworkmod Recovery, 2 - Team Win Project Recovery, 3 - stock.
Team # 7 - Installing Busybox
Attached Image

And again one question: do you use Custom ROM or Unsecured boot. If you have a full stock, then answer no.
What is Busybox for?
Team # 8 - Execution of commands # 3- # 7 in one click
Attached Image

If the previous commands (3-7) were executed very easily, then this one will make them even easier. 1 click - and you have a bootloader opened, a root is received, the latest version of CWM Touch custom recovery (securely installed) and busybox are installed. Convenient, right?

Team # 9 - Download, unpack and flash the official firmware image
Attached Image

This command will install the official firmware on your phone. First we need to choose one of two points: downloading the firmware and installing or installing right away if you have already downloaded it before.

Download and install:
First you need to select the version of the firmware you want to install. Do not forget that you need to choose from GSM<YAKJU-MAGURO>(because most likely you have such a model). After selecting the firmware, the download will start, and then the installation.

Installing an existing image with firmware:
Must putone and only one firmware image with extension .tgz to the put_google_factory_image_here folder (and it is in the folder where the GN Toolkit was installed before).
Team # 10 - One-time custom recovery
Attached Image

This command will allow one-time boot into custom recovery (CWM / TWRP). This is necessary for those who want to do something with the help of custom recovery, but do not want to replace the stock recovery.
Team # 11 - Install or load your .img file
Attached Image

With this command, you can install some of your .img image or run it (for example, your CWM / TWRP image).
Files must have an extension.img . You need to put in the put_img_files_to_flash_here folder. I advise you to call the files short names, as you have to enter them manually.
After selecting a file from the list, it will be offered to download the image (1) once or install it (2).
Team # 12 - Install Applications
Attached Image

This command can install selected or all applications on the phone. You need to put them in the put_apks_to_install_here folder
The first question the program asks us is: "Install one or all applications?"
Selecting one or another item, the program will display a list of all applications in the folder.
For a single installation, you must enter the name of the application with the extension; when installing all applications, simply confirm your action.
Team # 13 - Uploading files to the phone
Attached Image

Throw the files you need to transfer into the put_files_to_push_here folder, enter the file name in the program - that's it.
The downside is that you can’t select everything at once for serial transmission.
Team # 14 - Downloading files from your phone
Attached Image

Enter the full path to the file to download it from your phone.
In order to download files from system folders, adb must have administrator rights.
Files are put in the folder pulled_files_are_put_here
Team # 15 - Editing file permissions
Attached Image

If you need to change the access rights of the application, this command will help you with this. I think you should not explain why to do it. If you need, then you know why.

Rights are divided into 3 categories:
“User” - (u) file owner;
“Group” - (g) a member of the same group to which the owner belongs;
“World” - (o) all others.

You can set permissions on:
r - the right to read data;
w - the right to change the content or record, but not delete;
x - the right to execute the file.

For folders, permissions have attributes:
r - the right to read the folder;
w - the right to change the contents of a directory, you can create and delete objects in this directory;
x - the right that allows you to enter the directory.
Each digit covers all three attributes: rwx, so you need to write only 3 digits (644, for example)
Team # 16 - Packing images in the .tar archive for Odin firmware
Attached Image

If you are a fan of Odin or you were simply asked by a fan friend to make a pack for him, then this team will help you. Files to put in the folder INPUT, the pack will be in OUTPUT

Terms of Use:
1. Files must have clear names for Odin (boot.img, recovery.img, radio.img, system.img)
2. Images should be no more than 10 in the folder

Team # 17 - Logcat
Attached Image

The logcat team will help us see what is happening "inside" Android. We will be able to observe which programs work, which services are running and how they work, whether there are any errors in their work. A very useful feature of logcat is that you can watch the Android boot process literally from the very start of the device with Android.

Saving the LogCat file to the computer:
1. Save the standard (full) log LogCat;
2. Saving the log with a certain priority. Certain events will be recorded to the file;
3. Save the log from the selected buffer: 1) radio buffer; 2) event buffer; 3) the main buffer (separately from the first two).
A little about the radio buffer and event buffer
The radio buffer is what the Radio module generates during operation, namely what is read from the RAM block of the body to which Radio is writing. A very necessary thing when looking for problems with the radio module. only triggers. Log of different triggers of events.


View LogCat files saved on your computer:
You can view the LogCat files that you previously saved on your computer. Just enter the full file name.
Although it's easier to go into the backups folder and open the file yourself

Clearing the LogCat file on your phone:
The log grows to large sizes very quickly, so it can be cleared to make it easier to find the information you need.

Saving the BugReport file to a computer:
Saving the BugReport file, which stores information included in any bug report: firmware version, information about the iron filling, system log (logcat), system information, and much more.

Viewing BugReport files saved on your computer:
You can view the BugReport files that you previously saved on your computer. Just enter the full file name.
Although again, it's easier to go into the backups folder and open the file yourself.
Team # 18 - Utilities for Developers
Attached Image

This section contains various utilities for developers.

Cache ripper:
This utility allows you to work with the image cache.img. It repacks the image in a .zip archive, with which it will be possible to work, as well as flash it through custom recovery
Team # 19 - Quick Pick (in development,donate version)

Team # 20 - Modifications Section
Attached Image

This section includes various modifications.

Modifications:
1. Change the density of the screen;
2. Modification of action confirmation in CWM. Instead of a few "No" items, there will be only one;
3. Turn on / off camera sounds;
4. Changing camera settings (bit rate, quality settings)
5. Changing the interval between WiFi scans;
6. Enable / Disable butanimation;
7. Color correction (change of gamma, screen brightness)
8. Reboot phones to apply modifications.
Team # 21 - Tips, recommendations (donate version)

Team # 22 - Phone Reboot Options
Attached Image


Options:
1. From fastboot to fastboot;
2. From fastboot to the system;
3. From system to fastboot;
4. From the system to the recovery;
5. From system to system (normal reboot);

6. Run the Odin program for flashing the phone
Team # 23 - Command Line
Attached Image

Run the command line to enter your commands (if you want to do something yourself, not through the program)
Team # 24 - Information and Help
Attached Image

Some GNTK Program Information
The screen displays only a portion of the text.

Team # 25 - Updating the program interface
Attached Image

If you have something not displayed in the main menu or is displayed incorrectly, use this command. It will "restart" ("update") the main menu.
Team # 26 - GN Toolkit Settings
Attached Image


Settings:
1. Go to the firmware selection screen;
2. Enable / Disable the download of the firmware selection screen at the start of the program;
3. Changing the background color and text in the GN Toolkit;
4. Activate donate version



Run ADB and Fastboot without moving to the folder with them (XP / Vista / 7)
Probably, everyone had a moment when he was bored to introduce the notorious
cd% path%
where% path% is the path to the folder with the ADB and Fastboot utilities.
I want to open the command line and immediately start working with these utilities. Why am I doing this? And besides that there is a way to do it.

There are two ways, more precisely, but one of them is not very beautiful: throw all the necessary files into the Windows folder. He is ugly because he creates an unnecessary mess in the system folder. Suddenly you will want to delete ADB and Fastboot, but you have forgotten the file names. Surely something will remain in the Windows folder after deletion.

The second method is much more beautiful. Its essence is probably known to everyone, but does everyone remember about this opportunity?
reddyboy remembers exactly. It was he who proposed this method of quick access. Run the command line anywhere and immediately start working with ADB and Fastboot. For this you need nothing at all.

Opens "My Computer", right-click in the free area and in the drop-down list select "Properties"
Attached Image

Next, select the item "Advanced system settings". In Windows 7, it is on the left in the list.
Attached Image

In the open window "System Properties" at the bottom we find the button "Environment Variables" and click on it
Attached Image

Now we see the "Environment Variables" window, in which there are two working areas. We need to find the variable "Path" in the second, lower area. Select it and click the "Edit" button below
Attached Image

So this is the final step. Before us is the window "Change system variable", whose name is "Path". In the field "Variable value" we need to add a line containing the path to your folder with ADB and Fastboot utilities. I have it
C: \ Android \ Tools
Add it to the very end, not forgetting to put a semicolon before it (this sign serves as a separator)
Attached Image


That's all. Now you just need to call the command line in any folder, either using the Win + R key combination, or from Start, or any other method known to you, and immediately start working with utilities.


Post has been editedanFo - 15.11.12, 17:46



Rep: (57)
Installing third-party firmware / kernel / radio module / modification.

Attention! ClockworkMod Recovery is required.
Before flashing it is necessarysave a backup of your imei

1. Download the zip-archive with firmware and drop it on the phone (no need to unpack it!). If you decide to flash a custom kernel, also download it and put the archive in the phone's memory.
2. Boot into Recovery (with the device turned off we hold Volume UP + Volume Down + Power, in the bootloader, use the volume buttons to select the recovery item and confirm your choice with the power key).
    Management in CWM Recovery is carried out with the buttons:
  • Volume Up = up
  • Volume down = down
  • Power = Enter

3. Just in case we do backup (backup and restore ->Backup)
4. Make a wipe (ATTENTION! This will delete some data on your phone.)
    What wipe to do?
  • when upgrading the firmware version to a newer one or changing the kernel, it is enough to do wipe cache and wipe dalvik cache, but it is not always necessary
  • when switching from one custom firmware to another or from a stock firmware to a custom one, you must make a full wipe:
    - wipe data
    - wipe cache
    - wipe dalvik cache
    - mounts & storage ->format / system
  • when switching to Android Revolution HD from any other firmware, the author recommends using his scriptSuper Wipe Lite(it also needs to be placed in the phone’s memory before starting all actions)

5. In the main menu, select "install zip from sdcard"
6. Then "choose zip from sdcard" and look for the firmware file (when switching to Android Revolution HD from any other firmware, first select the archive with Super Wipe Lite, and after it install the firmware). Run the button Power.
7. Similarly (install zip from sdcard ->choose zip from sdcard ->select the required archive ->Click Power) install the kernel / radio module / modifications and any other zip archives


NOTE:
1. If the newly installed firmware does not work correctly for you, reboot into Recovery, make all three types of wipes (wipe data, wipe cache and wipe dalvik cache) + format / system in the mounts & storage tab in CWM and flash again. If this does not help, only then ask questions about the work of the firmware in this topic!
2. Some firmware (CyanogenMod, AOKP, Codename Android, etc.) do not contain Google applications (Market, Gmail, Google Talk, etc.). They need to be flashed separately immediately after the firmware in the same way via install zip from sdcard. You can download the latest gapps archivehere. Always choose the latest gapps for ICS


Post has been editedlemon174 - 15.03.12, 18:05
Reason for editing: unification of instructions for any firmware / cores



Rep: (403)
Romanista @ 12/07/2011, 00:29*
Regime Scandinavian God Odin?

ODIN - this is kind of like the Samsung flash driver used in SC. Many samsung users use it. for the Nexus S is practically useless (at least not heard of someone using it). let's see what will happen with the Galaxy Nexus



Rep: (80)
SlavaS_71 @ 12.12.2011, 15:03*
I didn’t understand humor, I can’t make the phone work in bootloader mode, the red ODIN MODE is on top. Who knows what it is?

I figured out that the phone gets into this mode if you press the sound reduction and power buttons, and if you press the sound reduction buttons on the center (as if + and -), then you get into the normal bootloader mode. At least in my case. : D

And in order tojust flash recovery, dancing with unlocking bootloader need to be repeated?

Post has been editedSlavaS_71 - 07.12.11, 05:43



Rep: (57)
Instructions on the firmware of the radio module via fastboot:

Due to the fact that for the new revolution you need another radio I am writing how to flash it.
1. Downloadfrom hereunpack, rename to radio.img, throw in the root folder on drive C:
2. Turn off the phone, connect the lanyard, hold down both the volume buttons and the power button.
3. Open the command line and write the following:
cd C: /
cd root
fastboot-windows flash radio radio.img
after each command, press Enter
4. Done, now you have a new radio, in our case XXKK6.

Post has been editedlemon174 - 16.12.11, 15:01
Reason for editing: at the request of the author



Rep: (403)
ErvSed @ 12/21/2011, 01:51*
So I could not download anything not OTA, not unlock to do.

Try flashing OTA through standard recovery:
1. Download the archive with the firmware, put it in the root of the memory card and rename it to update.zip
2. Turn off the phone via USB and enter the bootlader mode (hold Volume Up + Volupe Down + Power)
3. Go to the recovery. In it, select the item apply update.zip
on the Nexus S running. on the Galaxy Nexus should be similar
ErvSed @ 12/21/2011, 01:51*
Is it possible to flash OTA through ODIN?

can

ErvSed @ 12/21/2011, 01:51*
Writes waiting for device and does nothing.

try to enable USB Debugging mode (Settings - For Developers - USB Debugging)

and the last option:
downloadthis archive, unzip, run run.bat, follow the commands. unlocks the bootloader, installs CWM Recovery, gets root. continue to do whatever you want

Post has been editedlemon174 - 20.12.11, 23:23



Rep: (954)
on xdalies and silent very good compact adb-driver purely for GN. maybe, in his hat, so that people wouldn’t cradle all the packs of all-in-one drivers in vain?
Attached fileNaked_Samsung_1.7.zip(3.53 MB)


***
On the topic of updating: it was unlocked, received a root, tried to provoke a PTA update for a long time, but did not wait. threw my hands into / caсhe fileyakju-icl53f-factory-89fccaac.tgzhowever, the recovery only noticed it after renaming toupdate.zip
however, this is obvious, of course.
but failed to update:signature verification failed
- Install / cache ...
Finding update package ...
I: Update location: /tmp/sideload/package.zip
Opening update package ...
I: 2 key (s) loaded from / res / keys
Verifying update package ...
I: verify_file returned 1
E: signature verification failed
Installation aborted.


in the end, I installed the custom recovery cwm, again stupidly renamed the update in update.zip, but even then a failure hit me: an errorCan't open /sdcard/update.zip (bad)

I stumbled on something. I'll go google.

update: I did not have to go far. here is the manual - everything worked out. I was for this instruction with xda started acting but the team adb devices did not issue the serial number of the device ( list of devices attached ), and this method with fastboot turned out to be on top.

to all: How to understand the tireless reminders of an advanced guy with Google Groups about the need to lock the boot? What kind of danger are we talking about and why leave the "bad idea" open?

"Don't forget that after flashing back to a factory state, your
bootloader is still unlocked. Don't forget to lock it back in order to
secure your device ("fastboot oem lock"). "

from here

"-However, if you keep your bootloader unlocked at all times
(which is a bad idea) "
from here

Post has been editedkrasnoff - 22.12.11, 20:02



Rep: (57)
Emiljohn @ 12.26.2011, 21:37*
If yes, then I do not go, a robot appears with an exclamation point in the red triangle

volume up button + power button.



Rep: (403)
There is no folder like cache.

Guys, it is very difficult to advise something without having an apparatus on hand, but I will still try. by analogy with the Nexus S: there we update to the root of the memory card. in all file managers, it is defined as the / sdcard folder. try to find the / cache folder using Root Explorer or File Expert
Emiljohn @ 12/28/2011, 01:15*
it (/ cache) will not be in the / sdcard folder (this folder is opened when connected to a computer), since it is located in the directory on the same level as / sdcard.

right thought
lemon174 @ 12/28/2011, 01:20*
And unless after the update, fixing the bug with the sound, the version of the android should not be 4.0.2?

not. VolumeBug is fixed in ITL41F firmware version based on Android 4.0.1.
4.0.2 is ICL53F

updates may be suspended for now. version 4.0.3, which first appeared on the Nexus S, was taken over by a buggy, so the OTA mailing was stalled. for a similar reason, the Galaxy Nexus update might have been suspended. Perhaps Google is now working on fixes and is preparing the next update.

Emiljohn @ 12/28/2011, 01:15*
Yes, please tell me how to put the OTA without root and third-party recovery.

we are all looking for the answer to this question. so far nothing but ODIN comes to mind.
Instructions in English

Post has been editedlemon174 - 27.12.11, 22:34



Rep: (2)
the_dimmer @ 12/28/2011, 12:49 PM*
Ruth is needed.

But getting a root without losing data is not how. So while a bummer.



Rep: (56)
Emiljohn @ 12/28/2011, 16:27*
the_dimmer
And how to do this is not very clear) please explain.

Firmware for OTA updates manually without root and custom flashing recovery:
1. download the update from the link from the header, copy it all to the root / sdcard on the phone
2. download clockworkmod
3. copy the img file of the recovery to fastboot, renaming to cwm.img
4. boot the device into the bootloader (at the same time the volume is more + less + power)
5. connect to computer
6. Check that everything works correctly (drivers, connection, mode) by typing in the command line from the sdk folder with fastboot: fastboot devices. Make sure that the phone is displayed in the list of connected devices.
7. boot into custom recovery (this is not firmware, only download): fastboot boot cwm.img
8. The phone will load into custom recovery, update the menu from it.

Who will try - accomplish your goal, please, by results.



Rep: (3)
Thank you all for your efforts and attempt to understand how to flash OTA for drain and without root, but for now there is only one way - ODIN. Somehow it turns out to be funny, but after all, on the previous nexus everything was convenient and without problems, it is very strange that for the next nexus, and this is how much a developer’s phone is, everything turned out to be a chore. I will wait while arriving through the air, the benefit has managed to update the bug with the sound. As soon as something arrives or get it, I will definitely accomplish my goal.



Rep: (403)
Instructions for firmware backup of the official image via ClockworkMod Recovery

This instruction is suitable for restoring the phone to its original state, as well as for those who do not receive OTA updates.

    What we need:
  • ClockworlMod Recovery
  • Backup of the official image for firmware via ClockworkMod Recovery

  1. Download the backup archive and unpack its contents to a memory card in the memory card \ clockworkmod \ backup \ folder
  2. Rebooting to recovery mode
  3. In the recovery, select the item Backup and restore - restore and select our backup. Use the power key to confirm your choice.
  4. After recovery, restart the phone by selecting reboot system now


Post has been editedlemon174 - 29.12.11, 14:47



Rep: (403)
How to install the official update:

Before downloading the update, check the type of your machine usingGN Official Update Checker (Mirror) and only then download OTA for your type of Galaxy Nexus
All OTA updates on XDA
Note:
1. Updates should be installed sequentially, i.e. if the firmware version is ITL41D, you first need to flash ITL41F, and only after that ICL53F
2. The second and third methods assume that you have installed drivers and fastboot
3. Methods 3a and 3b require assuming that your device has busybox and ABD installed on the PC

1 way - using ClockworkMod Recovery
  1. Download the official OTA-update
  2. Open the OTA archive and delete the recovery folderUPD:Do not delete this folder., if you bet OTA 4.1 and higher
  3. We copy archive OTA on phone
  4. Reboot to Clockworkmod Recovery
  5. Select "install zip from / sdcard", then "choose zip from sdcard" and look for the update file. Run the button Power.
  6. After installation, in the main recovery menu, select the reboot system now

2 way - Stock recovery, bootloader unlocked
  1. Download the official OTA-update
  2. We copy archive OTA on phone
  3. DownloadingClockworkMod Recoveryin the folder with fastboot and rename the file to cwm.img (for convenience)
  4. Reboot to bootloader
  5. Open the command line and write:
    cd C: / root
    fastboot boot cwm.img

    Note: From: / root - the location of the folder with fastboot. Be careful, it may be different with you. CWM Recovery will not be installed, this command will only download it on your phone.
  6. On the phone, use the volume keys to select "install zip from / sdcard", then "choose zip from sdcard" and search for the update file. Run the button Power.
  7. After installation, in the main recovery menu, select the reboot system now

3 way - Stock recovery, bootloader is locked, there is root
    Method 3a
  1. Download the official OTA-update on the phone and rename it to update.zip (for convenience)
  2. Open the command line and write:
    cd c: / adb
    adb shell
    su
    cp /sdcard/update.zip /cache/apdate.zip
    exit
    exit

    Note: С: / ADB - folder location with ADB. Be careful, it may be different with you. With the help of this command, the update file will be transferred from the / sdcard folder to the / cache folder - to the place where it is downloaded when updated over the air.
  3. Turn off the phone and enter the bootlader mode (hold Volume Up + Volupe Down + Power)
  4. In the bootloader, use the volume buttons to select the recovery item and confirm your choice with the power key
  5. After the appearance of the green robot with an exclamation mark, we hold down Volume Up + Power, thereby entering the stock recovery
  6. In recovery, use the volume keys to select "apply update from / cache", then look for the update file. Run the button Power.
  7. After installation, restart the phone


    Method 3b (does not work yet, as the archive flesh_image.zip is outdated)
  1. Download the official OTA-update on the phone
  2. DownloadingClockworkMod Recoveryto the phone’s memory card and rename the file to cwm.img (for convenience)
  3. Downloadingflesh_image.zip, unpack and transfer to the phone's memory card
  4. Open the command line and write:
    cd c: / adb
    adb shell
    su
    cp / sdcard / flash_image / data / local / tmp / flash_image
    chmod 0777 / data / local / tmp / flash_image
    ./data/local/tmp/flash_image recovery /sdcard/cwm.img
    exit
    exit

    Note: С: / ADB - folder location with ADB. Be careful, it may be different with you.
  5. Turn off the phone and enter the bootlader mode (hold Volume Up + Volupe Down + Power)
  6. In the bootloader, use the volume buttons to select the recovery item and confirm your choice with the power key
  7. Select "install zip from / sdcard", then "choose zip from sdcard" and look for the update file. Run the button Power.
  8. After installation, in the main recovery menu, select the reboot system now


    Method 3c
  1. Download the official OTA-update on the phone
  2. Install from the marketROM Manager
  3. Go to the ROM Manager and install CWM Recovery
  4. Turn off the phone and enter the bootlader mode (hold Volume Up + Volupe Down + Power)
  5. In the bootloader, use the volume buttons to select the recovery item and confirm your choice with the power key
  6. Select "install zip from / sdcard", then "choose zip from sdcard" and look for the update file. Run the button Power.
  7. After installation, in the main recovery menu, select the reboot system now

4 way - Stock recovery, bootloader blocked, no root
Only for JRN84D and above!
  1. Reboot the phone to the stock recovery (with a lying android and an exclamation mark);
  2. We go in the recovery, holding the power button and pressing the Volume Up;
  3. Select the item "Apply update from ADB";
  4. Download the correct update and put it next to the ADB utility;
  5. Open the command prompt and go to the folder with ADB (I have this "cd C: \ Android \ tools");
  6. Enter "adb devices"to make sure that the phone is connected correctly;
  7. Enter "adb sideload name-of-file.zip";
  8. We wait, then boot into the system. Is done.

If your firmware version is lower than the JRN84D, then:
Unlock the bootloader and read the previous methods, or wait for the OTA to fly through the air

Status 7 Error
If you have a Status 7 error during the installation of the update, then first read it carefully.
In full, it usually looks like this:
assert failed: apply_patch_check ("/system/app/SystemUI.apk", "4c70c8cc085ddd25add379f025ff3cb1d8524533", "759fb06372db78643a31c61b6f075ab912f86600")
E: Error in /sdcard/f946a4120eb1.signed-yakju-JR003C-from-IMM76I.f946a412.zip
(Status 7)
Installation aborted.

This means that the fileSystemUI.apk (you may have another ) on the path / system / app / does not match the original file from IMM76I. This happens when you replace the system file with its modification or some other. In this case, it is possible to fix this problem without completely reinstalling the system, for this it is enough to replace the problematic file with the original one from IMM76I (you can take the system files from the CWM backups in the Firmware Catalog>Official firmware).

If there is something incomprehensible for you, then you should reinstall 4.0.4. This can be done, for example, by the very first instruction in the "Instructions" section.
It is worth remembering that this note describes the problem when moving from 4.0.4 to 4.1.1. But it also applies to all transitions!


Post has been editedshuric164 - 30.07.13, 09:12



Rep: (64)
Tell me why the quality of photos installed on a call in such a poor quality? How can you raise it?



Rep: (403)
Savost @ 01/08/2012, 21:22*
And how to do this if the body does not load as a firmware file to throw into the body?

flash ClockWorkMod Recovery, enter it, find the Mount & Storage item, and Mount USB storage (or something like that) in it
or according to the instructions for restoring the phone to its original state



Rep: (49)
gralexon @ 01/08/2012, 19:25*
Nothing is deleted !!! From the time of purchase and the first firmware I use Super Wipe Lite. With the transition from one assembly to another.
Apsy save AppMonsterPro., Much more convenient and not as overly wise as titanium

Do all these programs really save the main cache? It seems they only save apk and that's it ... (((



Rep: (403)
KeLeM @ 01/08/2012, 9:27 PM*
CWM makes a complete wipe of the device, because The nexus`e does not distinguish between internal and virtual cards.

does romanista lie?Samsung Galaxy Nexus - Firmware (Post # 10293036)



Rep: (49)
lemon174 @ 01/08/2012, 19:37*
it means something else should work) for example mount data or something like that
the second instruction will definitely help

Now in CWM 5.5.0.2 more than one item does not work, the smart through recovery could not be connected as a file storage to the computer.

aboutwipe
If you select wipe data / factory reset, it will delete everything from smart
if you choose
mounts and storage -format / system
format / cache
format / data
- all files, so let's say on the map, will remain

Post has been editedKelem - 08.01.12, 18:51



Rep: (56)
lemon174 @ Today, 22:37*
Quote (KeLeM @ 01/08/2012, 9:30 PM)
While this feature is not valid in the CWM for Galaxy Nexus
it means something else should work) for example mount data or something like that
the second instruction will definitely help

Adb push should work.


Full version    

Help     rules

Now: 07/01/19 03:25