Google Nexus 4 - Official firmware



Rep: (467)
Google Nexus 4 - Official firmware
PictureGoogle Nexus 4 aka mako, E960
Description | Discussion | Purchase | Accessories | Marriage | Power consumption and autonomy | Firmware | Custom kernels | Custom firmware | Ubuntu touch | Cyanogenmod | AOKP | ParanoidAndroid (v3 +) | MIUI | LeWa OS 5 | Sailfish OS | Yandex.Kit | Android L firmware (OS 5.0) | Modifications of software and decorations | games and apps | LG Google Nexus 4 club |

FAQ:CHAhundred askedATpolls andABOUTanswers to them (FAQ)
Instructions for firmware / factory reset / rollback
Instructions on firmware for OS Windows (fully and in parts, problem solving)
Instructions on firmware for Windows + video .
Video 5.0 firmware manual
Instructions on firmware for OS Ubuntu Linux (13.10)
Mac OS X Firmware Manual
Instructions on firmware using Total Commander .
How to restore your Nexus 4 (including IMEI) (and memory loss) .
How to open the bootloader / get root rights without losing data / second option
Instructions for firmware through custom recovery (CWM or TWRP).
What to do if not sewn through TWRP .
How to install 4.4. * Through custom recovery (CWM, TWRP) without loss of applications and data .
Instructions. Backup EFS / IMEI .
Wug's Nexus Root Toolkit utility instructions
RestoreME for Nexus devices - Program for quick recovery / firmware of the last full image of the official firmware.
RecoveryME for Nexus devices - A program for flashing custom recovery.
Errors when flashing the full factory image via fastboot
What to do if the phone goes into Bootloop (Eternal download)
  1. Reboot the smartphone, holding the power button a little more than 10 seconds.
  2. When the screen goes out, hold down the Volume Down (volume -), get into Fastboot mode.
  3. Use the volume buttons to select Recovery mode, confirm the selection with the power button.
  4. Android appears with an exclamation mark. Press the Power button, then press the Volume Up button (volume +), it may not work the first time.
  5. Select wipe data / factory reset.
  6. Choose reboot system now.

If it does not help, we are flashing the full firmware using one of the instructions.

Official firmware
4.2 - (JOP40C; radio 2.0.1700.33; bootloader makoz10l) of 11/13/12
4.2.1 - (JOP40D; radio 2.0.1700.33; bootloader makoz10l) from 11/27/12
4.2.2 - (JDQ39; radio 2.0.1700.33; bootloader makoz10o) of 02/11/13
4.3 - (JVR66V; radio 2.0.1700.84; bootloader makoz20i) of 07/24/13
4.3 - (JWR66Y; radio 2.0.1700.84; bootloader makoz20i) 08/21/13
4.4 - (KRT16o; radio 2.0.1700.97; bootloader makoz30d) from 11/14/2013
4.4.1 - (KRT16S; radio 2.0.1700.97; bootloader makoz30d) from 11/20/2013
4.4.2 - (KOT49H; radio 2.0.1700.98; bootloader makoz30d) 10.12.2013
4.4.3 - (KTU84L; radio 2.0.1701.02; bootloader makoz30d) from 06/02/2014
4.4.4 - (KTU84P; radio 2.0.1701.03; bootloader makoz30d) from 06.20.2014
5.0 - (LRX21T; radio 2.0.1701.04; bootloader makoz30f) 11/14/14
5.1 - (LMY47O; radio 2.0.1701.06; bootloader makoz30f) 04/15/15
5.1.1 - (LMY47V; radio 2.0.1701.07; bootloader makoz30f)
5.1.1 - (LMY48I; radio 2.0.1701.07; bootloader makoz30f)
5.1.1 - (LMY48M; radio 2.0.1701.07; bootloader makoz30f)
5.1.1 - (LMY48T; radio 2.0.1701.07; bootloader makoz30f)
Official site .
Mirrors of images .
Stock firmware 5.1.1 (LMY48T) - under custom recovery.
Stock firmware 5.1.1 (LMY48I) - under custom recovery.
Stock firmware 5.1.1 (LMY47V) - under custom recovery. ( installation tips )
Stock firmware 5.0.1 - under custom recovery.
Firmware 4.4.4 (clean: odex, without root + separate radio) - under the last TWRP (there may be problems on CWM).
Firmware 4.4.4 (odex, without root and radio, ROM + Kernel) - under custom recovery.
While there is no need to sew stock deodex firmware, everyone has problems with applications and a back button.
What and where is the firmware image
Download the stock images of the firmware version you need (the image will have the extension tgz).
Unpack the downloaded archive into a folder, unpack it (for example, with the WinRAR program).
Carefully study the unpacked files: bootloader-mako - *. **. Img (bootloader), radio-mako -... img (radio), flash-all.bat, flash-all.sh, flash-base.sh (these three files are needed only for one-click firmware) and image-occam - *****. zip.
Carefully read the contents of the image-occam archive - *****. Zip, there are: android-info.txt, boot.img, recovery.img, system.img, userdata.img


Ota update
The main condition for successful firmware OTA, it is completely stock firmware.
The difference even in one system file will cause you an error when updating. This also applies to the presence of Root and custom recovery.

OTA from 4.2. * To 4.4. * - no (you cannot upgrade right away) .
What is checked before installing OTA.
All known PTA on nexus 4.
Mirrors on the PTA.
How OTA is sent and why you shouldn’t clean the Google Services Framework
OTA manual installation manual (in English)
OTA forcing methods
Attention!!! These methods can cause different glitches on the device and a malfunction of Google services. Therefore, these actions are at your own risk. Please note that they do not give any guarantee for the arrival of OTA. If the topic will be questions: "Why does not help me?" - these methods will be removed from the caps and topics. Before writing such a post, consider how you will be "grateful" to the forum users who did not find them in the cap.

Option 1.
1. Turn off the entire Internet (WIFI, 3G).
2. Disable location determination.
3. Delete the data from the Google Services Framework application, stop the application, if asked, prohibit determining the location.
4. Turn on WIFI.
5. We are updating.
6. Delete Google account and score it again.
7. Turn on location.
8. We rejoice.
Option 2.
1. Go to Settings-Applications-All.
2. We are looking for the Google Services Framework there and poking it, we need to clear its cache and delete its data.
3. Open the dialer and dial * # * # 2432546 # * # *
4. We are waiting for the "checkin succeeded" notification.
5. Check for updates and enjoy))
Possible problems
1) Eat changed the battery and when you upgrade get a recumbent android. RecoverSystemUI.apk and SystemUI.odex from backup or flush system from your current firmware.
2) If, after the update, you have problems with Google Play and your account, read the FAQ (FAQ).
How to flash OTA manually
Option 1: via adb sideload
1) Download OTA.zip to computer. Rename the archive file to update.zip, and move it to the folder where the adb.exe file is located
2) Connect the phone to the computer, and boot into fastboot.
3) Select “recovery mode” and click “Power”. You will see a lying android, press the "Power" button simultaneously with the "Volume up". In the menu, select “apply update from adb”
4) Open a command prompt on the computer (cmd). In it, go to the directory where the update.zip file is located, and enter adb sideload update.zip. Download will begin.
5) Reboot.

Option 2: Through custom recovery (for upgrade to 5.0 does not work).
1) Download OTA.zip and copy to your phone.
2) Boot into the recovery.
3) Sew OTA.
4) Reboot.
Wipes are not needed.

Option 3: Use the Tool Kit (program for flashing).

Drivers and Utilities
drivers
New USB driver .
Google USB Driver (required for Windows, only to run ADB)Attached filelatest_usb_driver_windows.zip(8.28 MB)

It can also be downloaded.here .
Attached fileUniversal_Naked_Driver_0.72.zip(8.28 MB)

Attached fileUniversalAdbDriverSetup6.msi(8.78 MB)
- USB driver installer from the CWM command (For all nexus and for all versions of Windows. In Windows 8, after downloading, select "More Info" and then "Run anyway").
USB driver for Win 8 Attached fileusb_driver_v8.zip(8.28 MB)

USB_driver_r06_windows Attached fileusb_driver_r06_windows.zip(8.28 MB)

ADB Drivers Attached fileadb.rar(738.28 KB)
.
tulkits (programs for flashing the whole, in parts, obtaining root rights, etc.)
Attention: before using the toolkit, make sure that it is updated and supports the selected firmware.
Wug's Nexus Root Toolkit (works with 5.0).
Nexus multitool - for OS X and Linux (works with 5.0).
SKIPSOFT ANDROID Toolkit - NEXUS 4 - Driver, Ruth, recovery. A single Android Toolkit, combines all the Nexus Toolkits.
N-Cry 4.4.4 - Analogue utility NexusToolKit, with a more simple and intuitive interface. Instruction .
Nexus 4 Mac Toolkit
Universal nexus linux toolkit - Similar to the Nexus 4 Toolkit, but only for Linux (compatible with MAC OSX).

Minimal ADB and Fastboot - A handy program (install the ADB driver itself, create a shortcut on the desktop to enter the command line (CMD).
15 seconds ADB Installer - Program for quick installation of all drivers (usb, adb_fastboot).
Android ADB - Plugin for Total Commander.
Flashify - Kernel firmware, recovery, zip, kernel backup, etc. from the phone (need root).
Flash Image GUI - A utility for firmware recovery and kernels directly from the phone (you need a root).
Boototlocker - Program for opening / closing the bootloader without losing data (root is needed). Also allows you to remove Tampered Flag (boot tag hacking mark on 30d).
Video instructions for installing drivers on Win 7 .
How to disable driver signature verification on Windows 7
How to disable driver signature verification in Windows 8
Windows 8 does not see the phone.
How to fix Code ** errors.
For Windows XP
For Windows XP users

Only for Windows XP:
1. Connect your Nexus to the Computer (USB Debugging must be enabled on the device).
2. Go to My Computer>Right click>Properties>Device Manager and double click on MTP device.
3. Go to the information tab and copy the similar code - USBVID_18D1 & PID_4EE2 & MI_00) (you can also copy it from here if they match).
4. Disconnect the Nexus from the computer.
5. Go to C: WindowsInf (the Inf folder is hidden, configured in the control panel).
6. Find the file wpdmtp.inf and open it in any text editor, even in Notepad.
7. Edit the wpdmtp.inf file, inserting into it what you copied in step 3 as shown below:
; Device is identified by Microsoft OS descriptor
; If your device doesn’t support it, use specific VID & PID for identification
;
[Generic.NTx86]
% GenericMTP.DeviceDesc% = MTP, USBMS_COMP_MTP
% GenericMTP.DeviceDesc% = MTP, USBVID_18D1 & PID_4EE2 & MI_00

[Generic.NTamd64]
% GenericMTP.DeviceDesc% = MTP, USBMS_COMP_MTP
% GenericMTP.DeviceDesc% = MTP, USBVID_18D1 & PID_4EE2 & MI_00

8. Save and close the file.
9. Connect Nexus to computer
10. In the device managerupdate MTP drivers
Next, unzip them into a separate folder (for example, in the c: driver disk)
We go to my computer ->Properties
select the service tab ->equipment ->Device Manager.

In the device manager, we are looking for a device with an exclamation point. This is our nexus.
Click on it with the right mouse button and click Update driver.
Click Run driver search on this computer.
In the Search for drivers line in the following place: drive the path to the folder where our drivers extracted (In my case, this is c: driver)
Put a tick in front of Including subfolders
Click Next
11. Done
If the drivers are not installed
Recovery
Easy way to install custom recovery without a computer
RecoveryME for Nexus devices - A program for firmware recovery.
ClockworkMod Recovery (CWM) 6.0.4.7
For firmware through recovery :
Touch version
Without tach.
For firmware via fastboot :
With that.
Without tach.
Also ClockworkMod can be flashed throughROM Manager by installing it from google play.
Where is the backup made in CWM stored?
XDA thread
Team Win Recovery Project (TWRP

PhilZ Touch 6 Recovery CWM Advanced Edition 6.x
TWRP Holofied - Able to flash img files, you can change themes.
What should I do if after the reboot the installed Recovery flies?
For 5.0.
for the rest: you need after installing Recovery without rebooting, go into Recovery and flash this archive:Attached filerevert-recovery-disabler_signed.zip(142,02 KB)
This archive removes the protection of Recovery from overwriting.


Root Rights / Root
The process of receiving rutprav data does not delete (if you have an unlocked bootloader). .
Kingo Android Rootgets root and unlocks the bootloader "in a couple of clicks" (with data loss)
Getting root without a computer
We get the root of the rights to 5.0: flash through the SuperSU custom recovery version above 2.27.
Instructions from green-08 and nazgul_ssm
RootME for Nexus devices - a program for obtaining root rights (works on 5.0)..
Removing root rights
SuperSU on4 PDA.
Superuser on4 PDA.

Useful
The last radio is 2.0.1701.04, the last bootloader is 30f .
Theme "Perezalete" .
Nexus 4 bootloader collection .
Collection of radio modems for Nexus 4
Kernels under custom recovery .
What and where is in the full image of the firmware.
ADB and all that can be done with it
Rar for android - unpacking / creation / treatment of archives.
Firmware in parts and in its entirety
Pharmacy (drugs, vitamins)
At 5.0, poor performance of WiFi on 11-13 channels was noticed on some devices - install others .
Speed ​​up mobile chrome .
Diskdigger - restore deleted images and videos.
wi-fi speed and range increase
help with changing the MAC address when rebooting and problems with pairing via bluetooth .
wifi connection troubleshooting
Attached filesoundfxfix.zip(265.07 KB)
- fix stuttering sound when listening through BT headset (worked on 4.3, on 4.4 they say fixed).
New dalvik and bionic patches for 4.4. * .
After installing these patchesbe sure to cleancache ( wipe cache partition ) and dalwick cache ( advanced - wipe dalvik cache ). To rollback, use backup or flush system.img . What do they give .
New Qualcomm GPU Drivers - tested on runoff 4.4.2 and higher.

Survey Screenshots
Attached Image

Attached Image

Attached Image


Post has been editedvaalf - 25.05.17, 20:45
Reason for editing: deleted broken links



Rep: (879)
TWRP updated again (removed the problem from those who use data encryption)Attached fileOpenRecovery-TWRP-2.8.3.2-mako.zip.(8.99 MB)



Rep: (39)
Pincher65 @ 12/23/2014, 21:00*
This does not happen, lay out the screen CMD.

Yesterday there were mistakes, I remember exactly, just did not curse.
In FastBoot Devices it was, and not stitched.
Now it became screenshots to do - everything was stitched. o.o.
Attached Image

Attached Image




Rep: (198)
Wug's Nexus Root Toolkit utility instructions


Are common
How exactly does NRT root my device?
Answer : This software does not use an exploit to root your device; instead, it relies on low-level access gained from unlocking the bootloader.
Essentially, the main steps involved in the rutting of any Nexus device are as follows:
1. Unlock the bootloader (bootloader)
2. Downloading / flashing alternative (custom) recovery
3. Use this recovery to flash Superuser recovery.zip
That being said, in addition to those fundamental steps, the NRT performs some additional actions that can be considered as complementary in the process of rutting. More specifically, when opting for NRT, you should also flash custom recovery for you, while rutting - the script also takes care of renaming a specific system file that (if available) can prevent the home recovery from sticking properly.
This file is located on the path:
/system/recovery-from-boot.p
In addition, with this proven feature (flashing custom recovery), Tulkit also installs a simple superuser application called QuickBoot, which provides an easy way to reboot your device right into the bootloader, recovery or system. This is very useful when you are trying to change the device without a computer at hand. Although this application is extremely small and does not work in the background, you can of course remove it if you don’t want it.

In addition, when using NRT to root your device, it also installs the superuser application, the BusyBox installer, which automatically installs and configures all the latest essential applets for you. Busybox is not technically required, but most root applications require applets to work properly.

Incredible Magic NRT is currently able to fulfill all the above tasks in full automatic mode. To achieve this goal, I had to use other, slightly complex, methods. More specifically, the NRT makes it possible to use (modified) boot.img, which I changed and re-compiled for each assembly (and each device); By temporarily downloading these modified boot.img's (kernels) allows you to run privileged commands. More specifically, getting access to the adb root.nrt shell uses this increased access to the shell to push a specialized temporary script - file, the program automatically generates a file called "OpenRecoveryScript" on your device. This "OpenRecoveryScript" file that is currently located in your device along Cache / Recovery Cache / TWRP recovery and ultimately directs it to perform certain tasks. In the case of the routing of your device, the script orders TWRP to flash a number of ZIP files that Perform basic tasks. More specifically, it stitches another SuperSU from chainfire or SuperUser from KOUSH (To rush the device, installing the application and the corresponding SU binary files.), I packed Zip to install the BusyBox application and other ZIP files, I packed for QuickBoot installation And the periments of the system file about which mentioned earlier (also if the user checked the option of firmware of custom recovery.)

When the script finally completes its work, it will provide some information about how to install Busybox applets and confirm the root.

What windows versions does NRT work on?
NRT works on all versions of Windows - XP and above. On 32-bit and 64-bit systems and OS architectures. This means 32-bit and 64-bit versions:
Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1 Preview, Windows 8.1, Windows 10 Technical Preview, Windows 10 Enterprise Preview
I personally tested it on several computers, on two desktop PCs and laptops. And I was able to configure the drivers successfully on all of them.

Repair / fix Nexus devices
The device is showing incorrect internal memory.
Answer: This can happen after flashing the stock firmware. The solution is to reset the factory settings in the recovery. If you want to save user data, you can simply clear the cache.

Help!!! My nexus device does not work completely. What should I do?
Answer: If you have ever experienced unexplained complications with your device, or you want to restore it back to the state to which you just bought it, then use the “Flash Stock + Unroot” function. This function completely wipes your device (including the contents on the internal memory). ), so make sure first of all that you have made a full backup of all your important data, and it will flash all the factory img files for the appropriate partitions. This means that he:
Sews the stock kernel (boot.img)
Sews stock bootloader (bootloader.img)
Will sew the stock image of the radio (radio.img)
Will repair stock recovery (recovery.img)
Will sew the stock file system android (system.img)
Sew user data (userdata.img)

My device does not have a recovery! How to fix it?
Answer: Do not have the recovery very unlikely if you deliberately entered the command: remove recovery or format the recovery. Interesting all you are confusing the pre-screen of the stock recovery, which shows the sign that the recovery is missing. This is understandable, because the pre-screen of the stock recovery is very misleading. This is a picture of android on the back with an open chest and a red exclamation mark with soaping over him. Do not be scared! This is a preliminary screen of the stock recovery. For the call of the stock recovery:
While holding the power button, briefly hold the volume up button
Now you can navigate with the volume keys and select with the power button.
So in order to reboot the device simply select reboot the system and press the power button.

The key combination to call the menu may not match all devices. If it does not work to call the menu, try simultaneously while holding all three buttons (zoom / reduction button + power button), the same thing and repeat it several times until it earns. If you want custom recovery (TWRP or CWM) then you can use additional fulk functions The recovery firmware button, or you can simply use the root button again with the proven custom recovery. If you use the Ruta button for the firmware of custom recovery Try to make your choice (TWRP / CWM) in the main menu in the first queue. Also you can use advanced features>Download temporary custom recovery to enter custom recovery without flashing it. Or you can fully automate the flashing process using the “Flash Zips” button (file on this computer).


Device connection
How do I enable USB debugging on android 4.2 (developer options are absent in the menu)
Answer: At 4.2, the developer options in the menu are hidden.
1. Enter the settings - about the phone
2. Go to the build number at the end of the list
3. Click on the build number 7 times. On the third click, you will see that you have 4 clicks left to become a developer.
4. Continuation: 4 clicks left
5: You are now a developer!, Return to the setup menu
6. Now you will see the developer options in your list of settings.
7. Open the developer options and check the debug mode via USB - enabled

How to fix adb device if it is displayed offline?
Answer: New security improvements in Android 4.2.2 assemblies (and higher) requires the end user to provide ADB access to all connected computers Before the plug-in can successfully issue any ADB commands to your device. Android 4.2.2 connections and above the device to Your computer (with a debug-on via USB). You will be prompted to confirm the message to allow or prohibit a USB debugging. This message will be displayed on your computers "Unique RSA fingerprint key" and provide a check box to always allow you to enable from this computer. Check this box and click "OK" your device will no longer be displayed offline (off).

If you do not see this reminder, then you should try the following:
With the device connected via USB and the toolkit turned on, switch USB debugging on / off in the developer options and see if a prompt appears.
Also try disconnecting and reconnecting the USB device.
Use advanced utilities advanced utilities>quick tools>List of devices adb mode (list of devices -adb mode) to check the connection of the device. If everything successfully agrees with the unique fingerprint key and your device will still remain offline (not connected) then go to additional suggestions in the program manual.

Drivers
I am having difficulty installing drivers on windows 8, what should I do?
Answer: Enable security mode to allow the use of unsigned driver files:
Method number 1: Through the settings of the interface Windows 8
1.) Winkey + C>Settings (gear icon)
2.) Change PC settings
3.) General>Advanced Run>Reboot now
4.) Elimination>Extra options
5.) Windows boot settings>Reboot
6.) Wait for the computer to restart ...
7.) Select disable driver signature verification
8.) Now you can start installing these drivers.
Method number 2: Via command line cmd:
1) Run the command prompt as administrator and enter the following commands:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON

2) Now, reboot your computer, or if you want to enter the command in cmd to reboot:
shutdown / r / t 1
3) Then use any driver installation.
4) After you’ve done everything, if you want to go back to the standard windows 8 drivers and turn off safe mode, open the command prompt as administrator and enter the following commands:
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
Then, just restart your computer.

I installed the drivers, but they still indicate that no adb / fastboot devices were found! What should I do?
Answer: Just because the tulkit suggested some driver option, it does not mean guaranteed work on your system, the NRT provides several driver options, so if you failed with one method, you can try another. Imagine when it comes to the driver settings, device dispatcher - Your friend. You can run the device manager in the manual of the driver itself, or in the Start menu by typing the command "devmgmt.msc" and the input button. The deck is to configure the device so that, the ADB is able to connect to it when it is enabled ( With the enabled debug mode via USB) and also so that FastBoot can connect to it when it is in the loader mode. Here are some tips that can help:
If method 1 does not work for you, I highly recommend trying method 4. Method 4 is a manual method, so that you can directly specify the correct path to the drivers in the device manager on your computer.
If you are trying new drivers, make sure that you start with the first step:
This means you should first use USBDeview to remove any conflicting drivers and completely restart your computer.
Enable USB debugging on your device and start the NRT before you connect it. Follow this path to accept the RSA request (provided you are on andoid 4.3) When you confirm this request, do not forget to check the "Always allow from this computer" , otherwise the NRT will not be able to connect to your device without re-accepting the request.
When connecting your device, always keep an eye on the device manager. You should be able to easily determine which hardware is your device, then you can configure the driver.
This rule also applies when you boot your device into bootloader mode. Look in the device manager and make sure that the device is configured correctly in this mode.
Remember, this is an easy way to check the driver using Quick Tools (List devices' feature). Check what appears as an adb device when your device is connected with USB debugging enabled, and so that fastboot sees your device in bootloader mode. (bootloader mode)
If you have problems, try another USB port. As mentioned in the manual, try using a USB 2.0 port if they are preferable to USB 3.0 ports. Try enabling and disabling MTP, just try this with PTP.

Downloads
I have a custom firmware, which version should I choose?
Answer: Select your device, then select “Custom ROM” as the version. If you find that some procedures do not work properly, then change to the most appropriate stock version - as a rule, the latest version will be available.

If I do not see my version specified in the selection menu, what should I do?
Answer: Select Android (Select Android) *. *. * - any version of the mode for your device at the moment. Any version will work to perform the most common tasks such as: unlocking, routing, flashing the drain, and re-blocking your device, so this A great option is the right to choose when a new version of Android comes out, if I have not yet updated the toolkit for full automated support.

If my display is yakjuux (yakjuxw, yakjuux, yakjusc, yakjuzs, yakjudv, yakjukr, yakjujp, which version should I choose?
Answer: select the appropriate YAKJU build (based on the numeric version of android). For example: If you are on yakjuxw 4.0.4, then choose YAKJU-MAGURO: Android 4.0.4 - Build: IMM76D “.

OTA Update + Android Updates
Can I get OTA after unlocking the bootloader and rutting?
Answer: If your device is completely in stock condition, then you can get OTA, basically ... (most likely) you are able to get OTA without any additional steps.
To clarify what a “drain” implies more specifically: Stock Android Recovery + no changes in system files.
Regardless - there is no risk in getting OTA ... either it will work and you will get successfully updated to the latest version of android, or you will not get and go back where you started from.
If you have done more than just launching several root applications, that is, you made some changes to your device that prevents you from receiving OTA: such as:
Overclocking / lowering the voltage of your device
Firmware custom: firmware, kernels, themes, mods, hacks.
Modify system files (for example, build.prop and systl.conf)
Custom recovery firmware (such as TWRP or CWM)
Or any other system file / binary configurations
Just back up your important data and use the “Flash Stock + Unroot” button (flash stock + delete root) to return your device to stock status.
If you have a full stock, except for the presence of custom recovery, then you can use the additional features of “Restore Stock Recovery” to restore the stock recovery and try again to get OTA.
If the last factory image is available directly on Google's website for your device, the same as the latest builds that is obtained by means of OTA, then when using the Flash Stock + Unroot function (flash stock + remove root), then you can flash the last factory image, To refreate directly to the latest version - there is no need for an OTA. Only lack of such an option for updating your device, this is what it erases (Vaipet) your device. So what you have to return to the factory state. This is not less if you You are going to flash stock, in such a way to get an OTA, then you can also simply flash the latest available factory image and directly update to the new version. It makes sense in the firmware of the older version of the flow, and then update the OTA.

I unlocked the bootloader / rutted, but OTA does not work - how can I upgrade to the latest version of the android (without losing my user data / or root)?
Answer: There are several ways to solve this problem, so I will explain each of them and their respective advantages and disadvantages:
Method number 1 Using “Flash Stock + Unroot” (firmware update + root deletion), without “No Wipe Mode” (without wipe mode) and the “Sideload Update” button.
Instructions:
Toolkits options menu (toolkit options menu)>Flash Stock>Enable ‘No Wipe Mode’ (enable no wipe mode)
Then m “Flash Stock + Unroot” (flash stock + delete root) and select the latest available image.
After completing these steps, if the latest version available in the toolkit you requested is not the latest version available from the Google website, via OTA then:
Use Google search to search for “OTA Update Zip” for your specific device and the version to which you want to upgrade (For example: ‘KOT49E OTA Update Zip for Nexus 10 ′)
Download the correct “OTA Update zip” update for your device (For example: ‘bab270d1d4d935e31f61b1dcf2e66600006c87f7.signed-mantaray-KOT49E-from-KRT16S.bab270d1.zip’)
Then use the advanced features of "Advanced Utilities">button "Sideload Update" and follow the instructions on the screen.
Use the toolkit to root again (if you want) by selecting “Any Build Mode” and if your device is not listed in the toolkit as described herecry
Manually reconfigure any system settings that caused the reboot.
Enjoy!
Advantages:
Allows you to upgrade to the latest version of android without losing your user data
Relatively simple and the ability to correct any previous failed attempts related to OTA.
Uses only stock official files directly from Google.
You do not have to wait for Google to release the latest factory image, all you need is an “OTA Update zip”.
Disadvantages:
It can restore some system parameters of “Flash Stock + Unroot” with “No Wipe Mode” that saves only user data and cache, not your system partition. However, flashing the system partition is exactly what makes this method work, that is, it fixes any conflicting issues that prevent the updating of the OTA and the successful reset of the system partition to the factory state.
Using the "No Wipe Mode" may potentially lead to undesirable problems, since it is not a real "cleaning". If you have seen included in Google script "Flash.all.bat", in their factory images, you probably noticed What they are written with the "-w" switch included by default, which means that these are their "recommended" firmware settings for the firmware firmware, suggest data cleaning (Wiping Data). It is, as they say, in many cases using "No Wipe "(Without wipe), such a way can work perfectly, and if, for some reason it does not work - you can always make a backup copy of your data and repeat" Flash Stock + Unroot "(flash stock + Delete root) with data cleaning .

Method # 2: Pending the last official stock stock image, back up and then use “Flash Stock + Unroot”

Instructions:
Develop some patience and wait for Google to release the update in the official stock image.
Save all your data using any method you prefer:
If you are root, you may want to try the purchased Titanium Backup application from the Google Play store.
If you are using Titanium Backup, the recommended backup is only your user applications and data (non-system applications), because when you are updated to a later version of Android, system applications are most likely updated, so the recovery of the backup of the old version of the application will be overwritten on your New system application with an old version, and if you had to restore only data, they may be incompatible with new versions of system applications). There are some exceptions to this rule - you may have been able to return with the restoration of some system data, however, if You decide to go on this path, attention you just restore the data (not applications), you do it selectively (one system application at a time), and you know how to delete application data if it does not work properly (settings>applications>everything>go to specific application>clear data>reboot the device).
Make sure that all the reserved data is stored on the computer - not only on your device, this means if you are using a third-party application like Titanium Backup to back up all your applications, then you should make sure that you have made a full backup of the Titanium Backup folder from the internal the memory of your device to your computer (or your cloud storage) before flashing a drain.
You can of course also use the toolkit to make a backup, however, you can find a third-party application, such as Titanium Backup, which is much better than Google’s adb backup.
Make sure you back up everything that is in your device’s internal memory that you want to keep (such as music, pictures, video) or synchronize with the cloud storage.
If you can, make multiple backups or use more than one backup - so you can be sure you save your data.
Use "Flash Stock + Unroot" and select the version to which you want to upgrade in the drain firmware menu and use "Autodownload / extract" (autoload and extract), or use the function "Other / browse" (others / open) if this version is not yet Listed and Google has already released the assembly on its website.
If you want, re-root your device using the toolkit.
Recover your data
Manually reconfigure any system settings that caused the reset.
Enjoy!

Method number 3: Wait for an independent developer who will release the customized custom firmware of the recently released version and flash it “not clean”
Instructions:
Google is looking for a release of a routine custom firmware, a recently announced version (For example: ‘KOT49E Custom ROM for Nexus 10 ′)
Download the best optimal custom firmware for you to meet your needs, some of them will be very close to using clean stock firmware, (while others may offer some neat mods and improvements.)
Not clean firmware in custom recovery (eitheratabout using a toolkit using the “Flash Zips” button - a file on a computer or manually through a stitched / temporary custom recovery)
By "not clean firmware" - I mean - flashing rum without clearing user data (however, you might want to catch your eye on clearing dalvick ′ and cache - probably the best option)
Of course, you can flash completely clean instead - like “wipe data / factory-reset” and then flash, but in this case you should backup all your important data before doing so.
Rout your device if the firmware you are trying to use is not custom.
Manually reconfigure the system parameters that caused the reset.
Enjoy!

Detailed guide to the Wug's Nexus Root Toolkit utility: Attached fileWug's Nexus Root Toolkit.rar (5.07 MB)

Download: Wug's Nexus Root Toolkit
P.S: I ask you not to criticize strongly, if you have something to add, or if there are any inconsistencies in the translation - please write to me in QMS.

Post has been editedrobotoboy - 16.01.15, 15:55
Reason for editing: Added Guide



Rep: (879)
Stoke 5.0.1. under custom recoveryhere(without radio).



Rep: (37)
Pincher65 @ 12/24/2014, 18:27*
Stoke 5.0.1. Under custom recovery here (without radio).

Is it possible to lay out on Yandex disk, a mirror or in another convenient place? ... And then only viruses have enough!



Rep: (879)
John8520 @ 12/24/2014, 20:18*
And then only viruses grab!
There are no viruses there. But flashing back Stock recovery.



Rep: (37)
Pincher65 @ 12/24/2014, 22:56*
There are no viruses there. But flashing back Stock recovery.

I managed to download (I will have to reinstall 2 hours), two hours a test. The feast is not smooth, the camera lags, there was a reboot. Little TWRP, with a full wipop and removal of all data. I have not liked it yet, the shell did not like it, returned to CM11-SNAPSHOT M12.
Not much not in the topic. The second day gives an error to the "cyan" of the second day! ...

Post has been editedjohn8520 - 25.12.14, 00:35



Rep: (1)
I ask the Council! Ruilt 5.0.1, there was a TWRP and Ruth recovery, I returned the stock recovery began to flash, the phone went down to the install-recovery.sh file, I change it to the correct via ES conductor, pre-pulling it out of stock firmware 5.0. Run the update, everything went to be updated and after the bootlup. I made wipes, Bootlup, I decided to flash the backup of two years ago (which was), I was loaded, the phone was loaded, the network found, but I stopped turning on WiFi and BT and began to slowly slow down. I decide to flash the stock firmware according to the instructions, I download 5.0.1 and I can not find the Flash-All.Bat file in the archive, I shake 5.0, 4.4.4, 4.4.3, 4.4.2 The same, I find the ego only 4.3 and below (after I found the reason for the lack of files in the archive, the culprit was WinRar an old version, but it was too late). I firm 4.3, the phone loaded, the brakes are disappeared, WiFi and BT turned on, and the network does not catch, noticed the absence of having and serial number ;-(, the hands dropped and at 4 am I went to bed. In the morning I called a friend who was engaged in professional phones repair and all him He said, he recommended no longer tormented the phone, and transfer it to him to restore on the Octopus Box programmer, which I did. The result is that I have been restored, but there is no serial (the programmer does not support it), without it, the phone behaves as well as Without having, that is, calling where either refuses.
Maybe someone had already faced and solved the problem with the restoration of the serial number, help the right advice !!!



Rep: (33)
* olomutsky, Did you look at the header at all? Did you see there?
LG Nexus 4 - Official firmware (post # 24350856)



Rep: (253)
V014nd @ 12/23/2014, 20:55*
Question to experts: Is it worth expecting in principle zip with 5.0.1 under custom recovery? I just do not know how it is on the drain, I am a passenger from Ciana, came to the stock while they saw there.

There are many images of ZIP with stock firmware for all (almost) Nexus devices, the author is the MULTIROM developer for Nexus Av. TASSADAR,you can add to the header

https: //s.basketbuild....vs/tassadar/stock_zips.

Post has been editedEvgenyouk - 25.12.14, 14:03



Rep: (1)
Dondrew29 @ 25.12.2014, 01:59*
* Olomutsky, Did you look at the header at all? Did you see there?
LG Nexus 4 - Official firmware (post # 24350856)


Of course I saw, but there is no information about the restoration of the serial number.



Rep: (3)
What if the bootlup on all firmware? As a drive through a TDPP recovery works.



Rep: (661)
AkastealThassasin @ 25.12.2014, 13:21*
What if the bootlup on all firmware? As a drive through a TDPP recovery works.

Make a backup of data! Speak on full stock 4.2.2 via fastboot.
Try to sew through the reservoir version of the version newer, byte by flashing boot and radio



Rep: (0)
After all attempts to update with the help of the phone itself, I tried to flash through the ADB-FastBoot (all the same all the data erased) according to the instructions
https://developers.google.com/android/nexus/images#nakasi.
factory manner 5.0.1https://dl.google.com/dl/android/aosp/occam-lrx22c-factory-86c04af6.tgz....
AND ABOUT! Miracle!!! No mistakes! And everything works (it seems, although I haven't checked everything yet)!
Attached Image

Fuch! So here is such garbage - updated, but with a loss of data ...



Rep: (103)
The camera is still lagging ... 5.01



Rep: (3)
olomutsky
Helped, then something needs to be done?
UPD updated OTA to 4.3, again bootlup ...

Post has been editedakastealthassasin - 25.12.14, 18:16



Rep: (879)
AkastealThassasin @ 25.12.2014, 17:50*
Helped, then something needs to be done?
The same thing that had to be done immediately - read the header.

Posted on 12/25/2014, 19:03:

Olomutsky @ 25.12.2014, 02:44*
Help the right advice !!!
Pass hot hello to your master-firmware, let him return everything to the place.

Posted on 12/25/2014, 19:04:

Silverhead_igo @ 25.12.2014, 16:15*
ABOUT! Miracle!!!
Yes No - people who do not read the cap of this topic, a lot.

Another stock under the caste of the recovery (from the same author, what was before in the header)Tymts.

Post has been editedpincher65 - 25.12.14, 22:17



Rep: (1)
Restore IMEI on the N4 16GB on the manual from the cap "How to restore your Nexus 4 (including IMEI) (and with memory loss)", everything went well, but as a result 5.0. * It goes into the bootlup, all the earlier versions are set and updated without problems. , incl. By air, and the OTA is updated to 4.4.4 and it says that there is no more updates. She also tried to put OTA in manual, still Boutlup.
Is it possible to somehow win, or already everything?



Rep: (72)
* Banzay ©, If the castor recovery is installed, you can flash 5.0 through it (specifically under CWR), making a complete wipe. Ruth Get SUPESU Firmware Some latest version.



Rep: (514)
Enmas @ 12/26/2014, 00:14*
Restore IMEI on the N4 16GB on the manual from the cap "How to restore your Nexus 4 (including IMEI) (and with memory loss)", everything went well, but as a result 5.0. * It goes into the bootlup, all the earlier versions are set and updated without problems. , incl. By air, and the OTA is updated to 4.4.4 and it says that there is no more updates. She also tried to put OTA in manual, still Boutlup.
Is it possible to somehow win, or already everything?

You can, flash everything by file. Radio, bootlider, System, Cache, etc.

Post has been editedfroll67 - 26.12.14, 06:44


Full version    

Help     rules

Now: 21.01.21, 21:39