ads
Google Nexus 4 - Official firmware
Google Nexus 4 - Official firmware
Google 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 пїЅ |
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)
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.
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:
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
Post has been editedvaalf - 25.05.17, 20:45
Google Nexus 4 aka mako, E960Description | 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
If it does not help, we are flashing the full firmware using one of the instructions.
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)
- Reboot the smartphone, holding the power button a little more than 10 seconds.
- When the screen goes out, hold down the Volume Down (volume -), get into Fastboot mode.
- Use the volume buttons to select Recovery mode, confirm the selection with the power button.
- Android appears with an exclamation mark. Press the Power button, then press the Volume Up button (volume +), it may not work the first time.
- Select wipe data / factory reset.
- 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.
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
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.
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))
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).
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).
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)
latest_usb_driver_windows.zip(8.28 MB)
It can also be downloaded.here .
Universal_Naked_Driver_0.72.zip(8.28 MB)
UniversalAdbDriverSetup6.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 8usb_driver_v8.zip(8.28 MB)
USB_driver_r06_windowsusb_driver_r06_windows.zip(8.28 MB)
ADB Driversadb.rar(738.28 KB)
.
Google USB Driver (required for Windows, only to run ADB)
latest_usb_driver_windows.zip(8.28 MB)It can also be downloaded.here .
Universal_Naked_Driver_0.72.zip(8.28 MB)UniversalAdbDriverSetup6.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
usb_driver_v8.zip(8.28 MB)USB_driver_r06_windows
usb_driver_r06_windows.zip(8.28 MB)ADB Drivers
adb.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).
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
; 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.
PhilZ Touch 6 Recovery CWM Advanced Edition 6.x
TWRP Holofied - Able to flash img files, you can change themes.
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
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
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:revert-recovery-disabler_signed.zip(142,02 KB)
This archive removes the protection of Recovery from overwriting.
for the rest: you need after installing Recovery without rebooting, go into Recovery and flash this archive:
revert-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.
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.
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
soundfxfix.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.
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
soundfxfix.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
 |
 |
 |
Post has been editedvaalf - 25.05.17, 20:45
Reason for editing: deleted broken links
vdo2000 @ 23.09.19, 16:03
Karandash,
becoming the latest stock - will not go wrong
becoming the latest stock - will not go wrong
I tried several firmware. All custom raw ...
He returned to the stock. Principle bearable, except that the absence of Russian T9 much prejudice. It is very uncomfortable to search for the desired contact.
Can have the treatment? And how can it be bolted to the drain dialer search for Russian letters with T9?
Posted 09/27/2019, 9:49:
Extreme Firmware 5.1.1
Custom rekaveri. Ruth did not set. If you need ready to install solutions for problems with dialer
Please tell me how to remove the button called and the camera from the lock screen to 5.1.1, all clambered can not find.
M
Topic locked due tolong absence activity.
If you need to add something to the topic, you can contact any section moderator.Android - Firmware
If you need to add something to the topic, you can contact any section moderator.Android - Firmware
©savagemessiahzine.com2005-2020 All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement