• EQUIPMENT
    Smartphones
    News, announcements, recommendations
    Laptops
    News, announcements, recommendations
    Audio
    News, announcements, recommendations
    Devdb
    Device Catalog
    TV and Monitors
    News, announcements, recommendations
    Appliances
    News, announcements, recommendations
    Pc iron
    News, announcements, recommendations
  • REVIEWS
    Smartphones
    Choosing, testing, telling
    Tablets
    Choosing, testing, telling
    Smart watch
    Choosing, testing, telling
    Accessories
    Choosing, testing, telling
    Laptops
    Choosing, testing, telling
    Audio
    Choosing, testing, telling
  • GAMES
  • FORUM

    • Google Nexus 4 - Official firmware
    19.11.12, 17:43 | #4221
    ●
    infernal85ᵥ


    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)
    Many useful and interesting. Here are the answers to most questions.
    I know: Android 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
    Method One + Video
    Second method
    Method three
    Method Four

    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
    All versions TWRP here
    2.8.7.0 For firmware through modified recovery.
    TWRP 2.8.5.2 Russian version
    Also TWRP can be flashed throughGomanager by installing it from google play.
    At 5.0, TWRP stores a backup here.
    XDA thread

    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
    Big collection from Yuk11 a continuation
    System Dump firmware from jockjoint
    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
    16.11.14, 17:06 | #4222
    ●
    pincher65ᵥ


    Rep: (879)
    FastReg1 @ 11/16/2014, 15:49*
    how to make the visible folder TWRP in which there are backups
    It can be seen in Data / Media / 0 / TWRP. To make the SDCard visible on (as usual) you need to enable MTP in TWRP settings.

    Posted on 11/16/2014, 17:06:

    Titann @ 11/16/2014, 16:52*
    Put CWM Recovery, and through it SuperSU, but SuperSu writes that it can not update the binary how to cure
    what firmware?

    Rostman_RK @ 11/16/2014, 13:53*
    All who have Error: Update Package Missing System.img. Follow the source in the Topics header for the Windows firmware + video. Next FastBoot -W update image-occam-jdq39.zip Instead, to calculate the contents of Image-Occam-LRX21T to the same folder (folder where ADB and FastBoot), then we write in the FastBoot Flash Boot Boot.img console, then Fasboot Reboot- FastBoot, make such manipulations for all archive files, replacing both BOOT words in the file name.

    I do not advise you to do so if there is a problem it must be solved, and not bypass. Then it will be worse.

    for those who flies custom rekaveri (first rally after mod firmware boot.img is fine, just re-sew): go to the system, find the recovery-from-boot and remove it (or just add bak in the title)

    Post has been editedpincher65 - 24.11.14, 22:55
    16.11.14, 17:40 | #4223
    ●
    TiTaNnᵥ


    Rep: (6)
    [QUOTE NAME = "PINCHER65" DATE = "16.11.2014, 17:06" POST = 35800801] ...
    DATA / MEDIA / 0 / TWRP

    Posted on 11/16/2014, 17:06:

    ...
    what firmware?

    5.0 Android ...
    16.11.14, 17:43 | #4224
    ●
    pincher65ᵥ


    Rep: (879)
    * Titann
    And where did you see such a way to get root on 5.0?
    16.11.14, 17:55 | #4225
    ●
    TiTaNnᵥ


    Rep: (6)
    Pincher65

    I always put it up .... Starting with 4.0 android like ... And now the binary can not update .... Visapka has such a method in the instructions !! And now I decided to try on 5.0

    Post has been editedTiTaNn - 16.11.14, 17:57
    16.11.14, 18:07 | #4226
    ●
    yakov :)ᵥ


    Rep: (2)
    Good evening everyone is interested in such a question. All who received the root on 5.0 did you spend the testing of the root he works? The fact is that when receiving the root by any of the 2 ways (everything passes without errors and hemorrhoids, there is a complete flashing flashing) Superwasher provides root programs but does not work, RutExplorer after the rights granted to him can not open the root folders, although it has a super-superstere . It seems that SuperSU does not open access, but emit it
    16.11.14, 18:10 | #4227
    ●
    pincher65ᵥ


    Rep: (879)
    Titann @ 11/16/2014, 17:55*
    Visapka has such a method in the instructions
    In the header there is separately for 5.0

    yakov :) @ 11/16/2014, 18:07*
    It seems that SuperSU does not open access, but emit it
    you are not right:
    Attached Image


    Post has been editedpincher65 - 16.11.14, 18:14
    16.11.14, 18:35 | #4228
    ●
    Kolhossnikᵥ


    Rep: (14)
    Good evening. 1 time ago, there were terrible stupids, such as described on the forum earlier, stupupuck WiFi at first loading, informing the interface, etc. (stood custom recovery + root. Sent standard, Cmd + Flash-all.bat). I think some kind of garbage, it was completely the second time, there were almost no problems described before. But there is some general ploying. What do you think can make a complete wipe from the standard recovery and has sewn again or a sense of it? Thank you.
    16.11.14, 18:43 | #4229
    ●
    pincher65ᵥ


    Rep: (879)
    Kolhossnik @ 11/16/2014, 18:35*
    can make full wipe from standard recovery
    You can simply reset to the factory in the phone menu (it is better than the wipe in the recovery). And please use normal Russian.
    16.11.14, 18:44 | #4230
    ●
    tviko7.ᵥ


    Rep: (0)
    Installed Lolipop from an official image. Quickly sit the battery and once every five minutes pops up the message "Wait ..." and disappears. Who knows what it could be?
    16.11.14, 19:12 | #4231
    ●
    st.R1keᵥ


    Rep: (84)
    Tviko7 @ 11/16/2014, 21:44*
    Installed Lolipop from an official image. Quickly sit the battery and once every five minutes pops up the message "Wait ..." and disappears. Who knows what it could be?

    Wipe to help.
    And desirable because it is written above.
    16.11.14, 19:42 | #4232
    ●
    TiTaNnᵥ


    Rep: (6)
    Put the root in this waymethod 2, Now such a question, can I update SuperSU through Custom Recovery CWM ???

    Post has been editedpincher65 - 16.11.14, 20:01
    Reason for editing: removed violation 4.15
    16.11.14, 19:59 | #4233
    ●
    pincher65ᵥ


    Rep: (879)
    Titann @ 11/16/2014, 19:42*
    Can I update SuperSU through Custom CWM Recovery?
    Code will come out - then we will find out. Perhaps the method will change, because Now there are problems.

    PS: New came out - you can.

    Post has been editedpincher65 - 17.11.14, 19:41
    16.11.14, 20:21 | #4234
    ●
    tviko7.ᵥ


    Rep: (0)
    ST.R1KE @ 11/16/2014, 20:12*
    ...
    Wipe to help.
    And desirable because it is written above.

    Made Wipe through the recovery, nothing has changed
    16.11.14, 20:25 | #4235
    ●
    Maksim anatolichᵥ


    Rep: (2)
    It is impossible to flash Android L, tell me what is the problem.
    Attached Image
    Attached Image
    Attached Image


    Post has been editedMaksim anatolich - 16.11.14, 20:29
    Reason for editing: screen under spoiler
    16.11.14, 20:29 | #4236
    ●
    pincher65ᵥ


    Rep: (879)
    Maksim Anatolich @ 11/16/2014, 20:25*
    tell me what the problem is.
    As usual, unwillingness read the instructions and faces - you can not flash the body with a blocked bootoder.

    * tviko7 Maybe you still bother to write as you sewed and after which. Programs extra raised after the firmware?

    Post has been editedpincher65 - 16.11.14, 20:33
    16.11.14, 20:40 | #4237
    ●
    PWStealᵥ


    Rep: (5)
    KKGMIG29 @ 11/16/2014, 16:59*
    Who happened to upgrade from this ota, which is higher to post? I will give immediately an error:
    Package EXPECTS Build Fingerprint of Google / Occam / Mako: 4.4.4 / KTU84P / 1227136: User / Occam / Mako: 5.0 / LRX21T / 1576899: User / Release-Keys; This Device Has Google / Occam / Mako: 4.3 / JWR666V / 737497: User / Release-Keys.


    I have on the device 4.4.4


    It was the same. If there is a custom recovery, then the problem, as I understand it, it is in it. You must roll back to the stock, made items 1-4on this manualAnd then in the same program Nexus root toolkit, you need to select the "Sideload Update" item and follow the instructions.

    It all loaded long enough, but it was successful. The new truth design is not very pleased, until no problem noticed.
    16.11.14, 21:28 | #4238
    ●
    Maksim anatolichᵥ


    Rep: (2)
    Unlocked a bootloader, the same mistakes, I re-read the fact, I did not miss anything more important.

    Posted on 11/16/2014, 21:28:

    * pincher65
    Through adb and official firmware from Guglosight
    16.11.14, 21:31 | #4239
    ●
    Alexkur95ᵥ


    Rep: (0)
    Good day to all) Now I have a native 4.4.4, Booth is unlocked, recovery - CWM, there is a root, I can flash OTA manually if you delete the root with a cap from the header? Because I understand that it is the root that is the main obstacle to OTA firmware (if any system files did not change, but I did not change), right? + Do I need to update CWM to the latest version?

    Thank you in advance)
    16.11.14, 21:35 | #4240
    ●
    pincher65ᵥ


    Rep: (879)
    Maksim Anatolich @ 11/16/2014, 21:28*
    Unlocked a bootloader, the same mistakes,
    one out of two; Or did not unlock or another error. And via ADB cannot be glued.


    * Alexkur95 In 5.0 you need to stock recovery even (at least yet).

    Post has been editedpincher65 - 16.11.14, 21:37
    16.11.14, 21:36 | #4241
    ●
    Mniopᵥ


    Rep: (1)
    Good day
    Decided to flash with the help of adb
    I downloaded the file from the site, unpacked, executed ADB Sideload, writes on the TLF screen:

    E: footer is wrong
    E: signature verification failed
    Installation aborted

    What to do?

    Thanks for attention



    Full version    

    Help     rules

    Now: 15.01.21, 03:55
    ©savagemessiahzine.com2005-2021 All rights reserved.
    savagemessiahzine.com®- registered trademark.
    Terms of Use   |   Denial of responsibility   |   Advertising placement

    Forum IP.Board © 2021   IPS, Inc .