> Attention!

We strongly recommend to readRules section "Android - firmware"

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


17 pagesV  < 1 2 3 4 5 6 > »  
 
REPLY
> Google Nexus 5 - LineageOS Firmware
G3Denver
Message#1
06.12.13, 12:21
Guru
*********
[online]

Group: Friendssavagemessiahzine.com
Messages 4733
Check in: 17.09.11
Xiaomi Mi 5

Reputation:-  1213  +

Google Nexus 5 - LineageOS Firmware
PictureGoogle Nexus 5 | D820 / 821 (Hammerhead)
Description | Discussion | Purchase | Accessories | Marriage | Official firmware | Unofficial firmware | Modified and stock kernels | Modification of software and decorations | Power consumption (autonomy) | Nexus 5 Owners Club | Topics for CyanogenMod 12/13 | LineageOS firmware

Attached Image

Before posting a message, be sure to read the materials in the topic header and / or use the search on the topic.
Questions whose answers are already present here, or are not directly related to the topic, will be deleted without warning.
>>>Mini FAQ | Bugs <<<

About LineageOS firmware
LineageOS- ideological continuation of the popular aftermarket firmwareCyanogenmod.
The firmware was the result of the collapse of Cyanogen and the departure of its founder.Steve kondik.
The firmware is completely based on the work of enthusiasts, including all the achievements of CyanogenMod.
LineageOS- the new name of the whole era and its new coil with the prospect of a better future.
LineageOS official website

About CyanogenMod
CyanogenmodCyanogenMod (pronounced sigh-an-oh-jen-mod - sayanodzhenmod) - after-sales flashing of cell phones and tablets based on the open source Android OS system.
It has features not found in the official firmware of the suppliers of Android devices, including the original theme (known as “Theme Engine”), the codec for Free Lossless Audio Codec (FLAC),
compressed cache (compcache), large APN list, OpenVPN client, reboot menu, support for Wi-Fi, Bluetooth, USB modem.

Cyanogenmod- The first mobile OS, which includes the BFS task scheduler and is the combination of the experimental branch and the official Android source tree.
The developers claim that CyanogenMod improves the performance and reliability of the OS compared to the official firmware releases. As of September 27, 2012 firmware
CyanogenMod installed on more than 2 million devices.

Cyanogenmod- this is custom software distributed for various devices running on Android OS. Based on Google’s source code,
CyanogenMod is aimed at improving the performance and stability of the system, compared with the official firmware produced by various manufacturers and operators,
like T-Mobile, HTC, and so on. Also, CyanogenMod offers a number of features and improvements that are not available in these firmware.

Instructions

Before any manipulations with the smartphone, it is recommended to make a backup copy of the current firmware and data!

Everything that you do with your device is at your own peril and risk! The administration is not responsible for the damaged smartphone!


® Before installing any custom firmware, the Bootloader must be unlocked and Custom Recovery TWRP installed(AOSP + CAF, AOSP, CAF, FAQ)according toFastboot Instructions.

® In TWRP It is recommended to backup the EFS partition. This will allow you to restore IMEI, S / N, GPSID, WIFIMAC, BTMAC in case of their loss.

® When upgrading to a newer / older firmware version, you must have RADIO & BOOTLOADER from the appropriate version of Android (flashing before installing the firmware itself and then restarting Recovery).All current filesare here

When switching from any other firmware via TWRP
(You can enter it by holding the device in the off state Volume "-" + "Power", after which the volume buttons select Recovery)
  • Copy the necessary firmware and Google Apps to the internal memory of the device
  • In the Wipe menu, perform Factory Reset(all data except user files on the device’s internal memory will be erased)
  • In the Wipe menu, then Adwanced Wipe, we perform the Wipe System
  • In the Install menu, select and install the file with the necessary firmware
  • In the Install menu, select and install the file with the necessary Google Apps
  • Reboot system(we are overloaded into the system)

When updating the installed firmware
  • Copy the necessary firmware to the internal memory of the device
  • In the Install menu, select and install the file with the necessary firmware.
    It does not matter what date the update is dated, because all changes accumulate in each build.
  • Reboot system (we are overloaded into the system)

To install CAF assemblies
(the instruction is similar to simple installation, except for some moments)
  • You must make sure that the radio module firmware is up to date.
  • Special recovery is required for installation.TWRP-CAF or universal from here .
    To install LineageOS 14.1CAF Normal or Universal TWRP (not TWRP-CAF) should be used.

When switching from an AOSP assembly to a CAF assembly or vice versa
  • Ensure the relevance of the firmware of the Radio module, update if necessary
  • Copy the necessary firmware (AOSP or CAF) to the internal memory of the device
  • In TWRP, install the appropriate twrp-hammerheadcaf.img, twrp-hammerhead.img, oruniversal.
    To install LineageOS 14.1CAF Normal or Universal TWRP (not TWRP-CAF) should be used.
  • Reboot recovery(overload recovery)
  • In the Backup menu, we back up the Data section.
  • In the Wipe menu, then Advanced Wipe, we perform the Wipe System and Wipe Data
  • In the Install menu, select and install the file with the necessary firmware
  • In the Restore menu, we perform the restoration of the previously saved Data partition.
  • In the Install menu, select and install the file with the necessary Google Apps
  • Reboot system(we are overloaded into the system)
    Installing CAF on top of AOSP and vice versa, without clearing Data, in current builds is impossible.
    In order to avoid various difficulties, a clean installation or repair via® Titanium Backup.

When upgrading or upgrading a version of Android and firmware based on it
  • Upgrade Radio & Bootloader to the appropriate version of OS Android
  • In the Wipe menu, perform Factory Reset(all data except user files on the device’s internal memory will be erased)
  • In the Wipe menu, then Advanced Wipe, we perform the Wipe System
  • In the Install menu, select and install the file with the necessary firmware
  • In the Install menu, select and install the file with the necessary Google Apps
  • Reboot system(we are overloaded into the system)

Additional instructions
* Android Pay, SafetyNet and Root on LOS 14.1 (hiding root) - Manual from Yakov5890 & freetushkan
* Partition file system change from EXT4 to F2FS - Manual from G3Denver & freetushkan
* How to save system applications or mods when updating firmware - Manual from lsa_1974
* How to assemble yourself NIGHTLY CM12 / CM12.1 - Manual from members of the forum vmkogeretla & garynych2010
* How to restore IMEI in case of loss - Manual from forumchanin region98
* Activate weather display - Manual from G3Denver


Firmware
Current versions
Official support of the device by the LineageOS community has been discontinued.
Actual official assemblies are no longer and never will be, but unofficial ones remain.
For example, from the former official maineiner LineageOS for Nexus 5.
Mirrors of the latest versions can be found in the following spoiler.


Informal assemblies from razorloves
LineageOS 14.1 AOSP
Android 7.1.x "Nougat"

(monthly updates maybe)
Post onsavagemessiahzine.com
Post on XDA (source)

����������

Informal assemblies from xbcn ( phoval )
LineageOS 14.1 CAF
Android 7.1.x "Nougat"

(weekly updates)
Download site
Build status in real time
List of changes


LineageOS 13 CAF
Android 6.0.1 "Marshmallow"

(monthly updates)
Download site
Build status in real time
List of changes


����������

LineageOS with integratedMicrog :
LineageOS 14.1 AOSP
Android 7.1.x "Nougat"

(monthly updates)
Official site
Download site

Irrelevant versions
The final official assembly LineageOS 14.1

LineageOS on AndroidFileHost (mirror from freetushkan )
LineageOS on Google Drive (mirror from dimensy )

����������

Final official builds of CyanogenMod

CyanogenMod on AndroidFileHost (mirror from freetushkan )
CyanogenMod on Yandex-Disk (mirror from Marvolo )

����������

Other assemblies

CM13 CAF on AndroidFileHost (builds from Pixelase )
CyanogenMod 12.1 CAF (build from DinD_Ykt )
CyanogenMod 11 (build from DinD_Ykt )

System dumps

Google apps
The size of the Nexus 5 system partition does not allow installing OpenGApps for Android 7.x above the micro version.

Due to outdated libraries in Nexus 5, on Android 7.x firmware, the current version of Google Camera does not work correctly.
Full-featured operation and operation of HDR + in Google Camera requires version 3.2.x (for example,from here).


Attached ImageGoogle Apps FAQ (GApps)
[GAPPS] OpenGApps for Android

miscellanea
Additions / modifications of the firmware
* SuperSU (XDA) , SuperSU (savagemessiahzine.com) - Getting root-rights, alternative to the built-in super-user (installation via recovery)
* Bootloader / Radio / TWRP- Bootloader, Radio and TWRP Collection
* Chronus / cLock weather skins- a collection of weather skins for widget cLock
* [CM12 / 13] C-Apps- A set of applications from Cyanogen OS
* [CM13] Aroma-package for removing / adding applications + modifications- Mod from aldam05
* [CM13] CM13 cleaning script- Mod from patik62
* [CM12.1] Cleanup Script CM12.1- Mod from lsa_1974
* [CM12.1] Sound mode for microphone, speakers, and noise cancellation- Mod from patik62
* Icons for emulating the power button in the NavBar LOS 14.1 -Attached filepowerbutton-icons.zip(4.91 KB)

Useful applications
* CyanDelta Updater- Application for incremental firmware update LineageOS (beta)
* Lineage downloader- Another application to update the firmware LineageOS
* Callrecorder- Application to record conversations from the line
* SELinux Mode Changer- Application to change SELinux mode
* LMT Launcher- Pop-up Navbar and Gesture Control (PIE)
* Lock screen changer CM12- An application to change the image on the lock screen


* All for Nexus 5- Collection of firmware, mods, patches, kernels, themes on forum xda-developers

Survey Screenshots
Survey on 02/15/2017
Attached Image

Survey of 10/09/2016
Attached Image

Survey of 06/29/2015
Attached Image

Poll from 04/05/2015
Attached Image

Poll 13.03.2015
Attached Image

Topics Curator:freetushkan


Post has been editedfreetushkan - 12.04.19, 12:52
Reason for editing: Removed links of the official version, added mirrors of the latest version
Dobrozol
Message#22
02.08.15, 08:38
Veteran
********
[offline]

Group: Friendssavagemessiahzine.com
Messages 1957
Check in: 13.12.10
LeEco Le 2 x527

Reputation:-  294  +

The problem of installing applications is solved with the help of the lacquer patcher. Go to the tools, scroll down and in the "select installation location", select the internal memory. It helps a lot.
Probably need to add to the header. I myself have been looking for an answer for a long time.
K
In the Mini FAQ(22.02.2017)


Post has been editedfreetushkan - 22.02.17, 16:52


--------------------
And we believe in words, there is fire in our hearts, and this is OUR rock'n'roll - do not touch!
patik62
Message#23
02.08.15, 11:32
Guru
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 7200
Check in: 04.11.08
Xiaomi Redmi Note 4 3/32

Reputation:-  2010  +

* Dobrozol
From Market both got up easily. Faster even than the same PowerAMP. I do not know why you and the rest are not put. Bootloader, stock recovery, etc. I always try to flash with each release of the new Android. And I'm stitching without any hacker tricks, but as Google recommends (flash-all.sh). It is possible for you to sin only on this - for example, the last runoff from Google was 4.2.2 and you installed cm12.1 on it. Bootloader, recovery, userdata, because the same is changing, that something new is being introduced there.
P.S. Try the command line:
adb shell
su
pm set-install-location 0

Digit Zero - default software installation
The number One - only in the internal memory
Number Two - only on SDcard
Maybe Zero will return everything as it should be and the phone itself will distribute where to install it.
K
In the Mini FAQ(22.02.2017)


Post has been editedfreetushkan - 22.02.17, 16:52
patik62
Message#24
17.08.15, 21:33
Guru
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 7200
Check in: 04.11.08
Xiaomi Redmi Note 4 3/32

Reputation:-  2010  +

The program is capable of doing something with noise cancellation through the recovery for Nexus 5

You are welcome:
Attached fileNexus5_5.1_LMY47D_v1.1_audiofix_RUSaroma.zip(1.07 MB)


What it does:
1. Noise reduction audio camcorder, you can choose 6 dB, 12 dB, the default we have 20 dB. That is, by simply disconnecting the second microphone in build.prop, the interlocutor can hear the sound of all the cars passing with a crash during the call. By default, the sound of the environment is taken to be cut by 20 dB, and with these settings we can adjust to our own way -what to say, everyone's voices are different: timbre, power, tonality ... Maybe part of the voice and fall under these 20 dB limits.
2. Microphone amplification during a call (but something, like there are already very high values ​​added) Recommended for all instructions no more than 97
3. The ability to turn on the second microphone during video recording. Gives the effect of stereo sound when viewing the captured video. Of course, this is a pseudo stereo, but better than the default.
4. The quality of audio recording video. The higher the bit the better the sound, but the size of the captured video file increases.
5. What are the tips, instructions in aMGC. I do not know
6. Stereo when listening to audio through the speakers - turn on the top speaker. And the ability to choose which side will be the left / right channel stereo. Landmark USB socket when it is either right or left
7. and 8. Sound amplification in headphones and in dynamics. Just do not be greedy at the maximum values ​​do not put.
9. An interesting setting. Decrease the volume of your own voice during a call through the headphones, and the microphone is used by the phone. Immediately limit the volume of your voice (secondary background) in the headset and phone. Personally, when I call in my headset, I hear myself almost stall and try to speak more quietly. It turns out that the interlocutor does not hear me well. And of course, we swear at a bad phone :-) Nexus 5 or firmware.
Put this mod on a clean firmware, not friendly with any other sound mods !!!
Backup before necessarily !!!
Picture



Post has been editedG3Denver - 12.07.16, 08:32
Riverlions
Message#25
07.11.15, 19:08
Guru
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 2925
Check in: 13.12.11
Apple iPhone X

Reputation:-  628  +

I started Google camera with hdr + on firmware without gapps)) The method is elementary.

- copied the entire data / app folder into user memory.
- installed the firmware
- in the recovery I mounted the system and threw the folder with the camera file and the libs into the app, immediately set the permissions for 755 to the main folder and the camera file
ps It is better to throw it into the data / app folder so that when updating the firmware, do not do this every time.
Attached Image
Attached Image
Attached Image

K
In the Mini FAQ(22.02.2017)


Post has been editedfreetushkan - 22.02.17, 16:51


--------------------
patik62
Message#26
08.11.15, 14:46
Guru
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 7200
Check in: 04.11.08
Xiaomi Redmi Note 4 3/32

Reputation:-  2010    +

For fans of Multi. Starting with cm-13.0-20151105, you can put cm13 on the Multi as the second.
Open META-INF \ com \ google \ android \ updater-script as text. The lines marked in blue are deleted:

assert(getprop("ro.product.device") == "hammerheadcaf" || getprop("ro.build.product") == "hammerheadcaf" || abort("This package is for device: hammerheadcaf; this device is " + getprop("ro.product.device") + "."););
assert(getprop("ro.bootloader") == "HHZ12k" || abort("This package supports bootloader(s): HHZ12k; this device has bootloader " + getprop("ro.bootloader") + ".");); download


ui_print ("Target: google / hammerhead / hammerhead: 6.0 / MRA58N / 2289998: user / release-keys");
ifelse (is_mounted ("/ system"), unmount ("/ system"));
package_extract_dir ("install", "/ tmp / install");
set_metadata_recursive ("/ tmp / install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive ("/ tmp / install / bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount ("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/ system", "");
run_program ("/ tmp / install / bin / backuptool.sh", "backup");
unmount ("/ system");
if is_mounted ("/ data") then
package_extract_file ("META-INF / org / cyanogenmod / releasekey", "/ tmp / releasekey");
run_program ("/ tmp / install / bin / otasigcheck.sh")! = "31744" || abort ("Can't install this package", please try another package or run a factory reset ");
else
mount ("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/ data", "");
package_extract_file ("META-INF / org / cyanogenmod / releasekey", "/ tmp / releasekey");
run_program ("/ tmp / install / bin / otasigcheck.sh")! = "31744" || abort ("Can't install this package", please try another package or run a factory reset ");
unmount ("/ data");
endif;
show_progress (0.750000, 0);
ui_print ("Patching system image unconditionally ...");
block_image_update ("/ dev / block / platform / msm_sdcc.1 / by-name / system", package_extract_file ("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print ("Verifying the updated system image ...");
if range_sha1 ("/ dev / block / platform / msm_sdcc.1 / by-name / system", "28,0,32770,32833,32835,33347,65535,65536,65538,98304,98306,98369,98371,98883 , 131071,131072,131074,163840,163842,163905,163907,164419,195997,196608,196610,229376,229378,229441,229443 ") ==" b970d8a6d53e1ad3e6adde4a90d5d78eede5673d,
if range_sha1 " , 98883,131071,131072,131074,131586,163328,163840,163842,163905,163907,164419,195997,196608,196610,197122,228864,229376,229378,229441,229443,229955 ") ==" aef7a-15'j'a for it
ui_print ("Verified the updated system image.");
else
abort ("system partition has unexpectedly non-zero contents after OTA update");
endif;
else
abort ("system partition has unexpected contents OTA update");
endif;

show_progress (0.020000, 10);
mount ("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/ system", "");
run_program ("/ tmp / install / bin / backuptool.sh", "restore");
unmount ("/ system");
show_progress (0.050000, 5);
package_extract_file ("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress (0.200000, 10);

Here is a ready updater-script
Attached fileMETA-INF.zip(1.27 KB)

K
In the Mini FAQ(22.02.2017)


Post has been editedfreetushkan - 22.02.17, 15:47
Nimnyl
Message#27
09.11.15, 09:30
Experienced
******
[offline]

Group: Friendssavagemessiahzine.com
Messages 597
Check in: 14.07.11
Google nexus 5

Reputation:-  40  +

* doom71,
In the system, the noise suppression speaker is off and that's it!
System - build.prop - you find the line (persist.audio.fluence.voicecall = true and you change this last (true) to (false)
Then save and reload.
It must be constantly done after updating the firmware !!!!!!
K
In the Mini FAQ(22.02.2017)


Post has been editedfreetushkan - 22.02.17, 16:53


--------------------
I appreciate the work of enthusiasts and developers!
G3Denver
Message#28
17.12.15, 19:16
Guru
*********
[online]

Group: Friendssavagemessiahzine.com
Messages 4733
Check in: 17.09.11
Xiaomi Mi 5

Reputation:-  1213    +

A small tutorial on how to enable Now On Tap on CyanogenMod13.

Who does not know what is going on, we are looking at Google. From myself I can say that the thing is useful.
Actually:
1. To begin with, of course, you must have the Google application installed and the included GoigleNow.

2. Go to the settings and select "Applications"
Attached Image


3. Tap on the gear in the action bar
Attached Image


4. Select "Default Applications"
Attached Image


5. "Assistant and voice input"
Attached Image


6. We put the tumblers as in the screenshot and go (ibid, by pressing the gear) in the Google settings.
Attached Image


7. Turn on "Context from Now"
Attached Image


8. Woah-la! We have a working Now on Tap.
Attached Image

P.S. Do not forget to give Google Apps all permissions in Privacy Guard.


Post has been editedG3Denver - 17.12.15, 20:08


--------------------
Do not put your hands where you are not a proctologist.
lsa_1974
Message#29
17.12.15, 20:41
Guru
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 3409
Check in: 17.06.12
Xiaomi Mi A1 4/32

Reputation:-  11881  +

* _Melkiy_,
I managedSo...
Further discussion of the health of applications of the corporation of good we conduct in the profile topics ...
G3Denver
Message#30
13.01.16, 10:09
Guru
*********
[online]

Group: Friendssavagemessiahzine.com
Messages 4733
Check in: 17.09.11
Xiaomi Mi 5

Reputation:-  1213  +

Instructions for changing the partition file system from EXT4 to F2FS in LOS / CM 12.1-14.1

CyanogenMod 12.1 and later for Nexus 5 now has direct support for F2FS.
The following describes how to migrate to this file system.

ATTENTION!F2FS is quite young and constantly evolving, and our device and its core, on the contrary ...
It is possible that you, like some other forum users, will encounter various bugs and will be forced to return to EXT4.
Perhaps it is not worth it .. You decide.

Briefly about the F2FS file system ...
F2FS is a young file system for nand-drives, developed by Samsung.
The developer claims that its use can extend the life of the drive and allows the data to be stored on it in a more organized way, thereby increasing the performance and speed of read / write.


Requirements:
  1. TWRP 2.8.7.1 or higher.
  2. OTG-drive or PC with installed drivers and cable.

Step-by-step instruction:
  1. We reserve all important data to third-party storage (PC or OTG, details below).
    This is important because The Data section will be completely cleared,including user datain / data / media.
  2. Go to TWRP and make a backup of the Data section. In the case of OTG, backup can be done immediately on it.
    In the case of a PC, after completion, copy / sdcard / TWRP / BACKUPS / to the computer.
  3. Next "Wipe" ->"Advanced Wipe", mark the "Data" and click "Repair or change file system" (activated when the selected section).
  4. On the screen that appears, select F2FS and confirm the formatting.
  5. Repeat the previous two points for the Cache section. System formatting does not make sense, because installing the firmware will return it to EXT4.
  6. Reboot into the system. As soon as we see the setup wizard, reboot back to TWRP.
  7. In the TWRP settings, tick the "Use rm -rf instead of formatting" checkbox.
  8. We restore the previously created backup copy of Data and user files.
  9. In the TWRP settings, uncheck the "Use rm -rf instead formatting" box.
  10. We return the files that were previously transferred to the PC or OTG.
  11. Making wipe caches and loading into the system.

Learn more about transferring files to OTG / PC
If you are using a PC, then it is necessary to mount the internal storage of the device from under TWRP ("Mount" ->"Enable MTP").
Next, we transfer the necessary files to the computer in the normal connection mode of the Media Storage.

If you have OTG-Flash, then you need to mount the OTG drive ("Mount" ->"USB-OTG").
Next, copy the files from / sdcard to / usb-otg using the TWRP file manager ("Advanced" ->"File Manager").
Alternatively, you can copy files using the built-in terminal ("Advanced" ->"Terminal").

Picture


Post has been editedfreetushkan - 08.03.17, 16:42


--------------------
Do not put your hands where you are not a proctologist.
patik62
Message#31
31.01.16, 23:22
Guru
*********
[offline]

Group: Friendssavagemessiahzine.com
Messages 7200
Check in: 04.11.08
Xiaomi Redmi Note 4 3/32

Reputation:-  2010  +

Script cleaning CM 13

Attached fileCleanCM13.0.zip(124.85 KB)

Plus added that the wipes would do Dalvik and Kesh.

Information on self-tuning list of applications to be deleted Google Nexus 5 - CyanogenMod 11/12/13 Firmware (Post lsa_1974 # 39387614)
Picture



Post has been editedG3Denver - 12.07.16, 08:38
Reason for editing: Added a topic in the header !!!
treffer
Message#32
10.02.16, 08:10
Old resident
*******
[offline]

Group: Friendssavagemessiahzine.com
Messages 925
Check in: 04.07.12
Google nexus 5

Reputation:-  69  +

Question to those who use AICP: is this ROM updated through CyanDelta?
M
Check outForum Rules!
4.18. It is forbidden to deviate from the topic (offtopic).


Post has been editedMorgan - 10.02.16, 08:22
G3Denver
Message#33
24.02.16, 11:32
Guru
*********
[online]

Group: Friendssavagemessiahzine.com
Messages 4733
Check in: 17.09.11
Xiaomi Mi 5

Reputation:-  1213  +

a lot of offtopic about cables.
* patik62,
Everything is very simple here. Cut the cable at the microUSB connector, leaving a ~ 15mm tail on the connector, so as not to lose pinout on the connector itself. Parse,unsolder this tail and solder the old, observing pinout.It is even better to bathe the connector in pure alcohol (without any impurities at all!) Or in an ultrasonic bath (for the most perverts).
Similar can be done with USB. I did not rewrite USB, there was no need.
That's all.

Attached Image

Cheated. Soldering is not necessary. It is self locking.
I messed with something, apparently. This job.
Specially disassembled. Everything for you. : D
Attached Image


U.P.D.
I shortened the cable to 885mm and once again transplanted the wires, but I bare them. The connector is bathed in alcohol.
Ready connector.
Attached Image


And, actually ...

profit
Attached Image



P.S. charge current For Li-Ion, currents of about half the rated capacity of the battery are recommended, i.e. For a battery with a capacity of 2000mAh, the charging current is about 1A, and for a battery with a capacity of 700mAh, the charging current is ~ 350mA. A battery charge with too high a current can lead to rapid degradation, and a too low one will take a long time;

We have 2300mA / h. The charge current should be ~ 1150 / 1250mA, which I achieved.
The rated current on our Adaptere- 1.2A = 1200mA +/- 5-10% of the nominal.

Post has been editedG3Denver - 24.02.16, 12:40


--------------------
Do not put your hands where you are not a proctologist.
noteMASTER_11
Message#34
10.05.16, 00:14
Mike zexter
*********
[online]

Group: Curators
Messages 2069
Check in: 10.02.12
Xiaomi Redmi Note 5 Pro

Reputation:-  706  +

thehennz,

Iheredescribed his understanding of CAF and AOSP. The choice is always yours, anyway.

Cyanogenmod Code Aurora Foundation (CAF)- This is the basis of AOSP + Cyanogenmod + base using the latest libraries for the periphery of the smartphone.

Who careshere is the main project site. They are not only firmware Andriod sawed.

Materiel (mnogabukaf!)
Aurora, in general, means the very first stage of software development - the introduction of the latest developments at the conceptual level with a minimal chance of stability - if only it were launched. Any software has two basic design concepts: product status and specific product assembly status. Development status: Alpha, then Beta, then RC (there may be many, for example, RC4 and RC11 have the same chance of becoming releases), only then Pre-Release and Stable Release. Also, any of the statuses can be “intermediate” and carry the “Pre-” prefix: Pre-Alpha 3, Pre-Beta 2, etc. But this is only a superficial, partial classification. Build status: there are "snapshots" - SNAPSHOT, there is Milliestone, there is a Developer Preview, there is the aforementioned Aurora - it all depends on the specifics of the build, because not every software product is made for% username%, we, in fact, are basically Nightly testers of assemblies, since Stable CAF is truly a rarity.

And the fact, the presence of which will blow up the brains of any inexperienced user : some large projects assign their classes to the products being developed, and it is necessary to study their individual understanding of the developments. We are relatively lucky: Cyanogenmod strictly adheres to Google's jargon, the same one, in turn, largely took designations from Linux and all various open-source projects. Aurora appeared thanks to the project "Firefox Browser" from the Mozilla Foundation - it is their concepts of the Ognelis builds that carry this name.

Against the background of this development, any of the versions, whether Beta or RC, can receive nightly builds - i.e. assemblies with a couple of fixes and a couple of new or old bugs + the same number of planned conceptual changes. These changes are called "commits" in the developer slang and are brief descriptions of changes in the program code. In large projects there are certain frames responsible for the description -committers. But this is not about CM CAF - its audience is small, although it will give odds to most Android-based projects.

CAF has a slightly different meaning - in it the stability of the work of all the latest libraries is brought, so the word Aurora should not scare you. Here the whole essence lies precisely in the pros of Aurora - that is, in svezhachka.


Subjectively: I like a clearer and stronger sound, more detail. I listen on non-budget IE-60 and I can judge. The battery does not go away so fast. There are no apps from Google (I’ve fun them on AOSP, but many of them are low-level tied to the functionality of the firmware, and their absence can cause crashes and bugs). The last two facts are closely interrelated - hello GAPPS-am, which is why I do not install. More custom kernels, although custom kernels and on AOSP before the light bulb already. In general, as they say, if you are satisfied, then you can leave everything as it is. The question of individual needs.

Post has been editednoteMASTER_11 - 10.05.16, 00:56
Reason for editing: Add-ons.


--------------------
Whyred 6/64 -% customromname% 9.0.0 + Magisk 18.1
Gaming laptops
G3Denver
Message#35
11.05.16, 12:27
Guru
*********
[online]

Group: Friendssavagemessiahzine.com
Messages 4733
Check in: 17.09.11
Xiaomi Mi 5

Reputation:-  1213  +

Turning on the weather display on CyanogenMod 13 / 14.1.


Easy way.
In order to activate the display of weather with standard CM tools, you need:

1. Install the pluginYahoo CM Weather ProviderorWU CM Weather Provider
2. In the main settings, find the item "Weather" and activate the plugin. There you can also select the units of measurement of temperature.
Clearly.
Attached Image
Attached Image


3. In the application "Clock", by calling the menu (via the "3-dot" in the lower right corner of the screen), select the "Widget Settings" section. There you can customize the weather.

Clearly.
Attached Image
Attached Image

After the above actions, the set weather values ​​will be applied to all display methods (Widget "cLocK" and notification panel).

The activation of the weather on CM14.1 is no different, except for the second paragraph, namely:
You need to go to the "Applications", tap on the gear in the upper right corner of the screen, find the item "weather" (weather).
Further, all steps are similar to the instructions above.


Just in case, I mirror apk plugins here:
Attached fileYahoo Weather Provider.apk(1.13 MB)

Attached fileWeather Underground.apk(1.16 MB)

Picture


Post has been editedfreetushkan - 08.03.17, 15:02
Reason for editing: Weather Underground and apk


--------------------
Do not put your hands where you are not a proctologist.
hoopoepg
Message#36
27.05.16, 10:32
Old resident
*******
[offline]

Group: Friendssavagemessiahzine.com
Messages 1237
Check in: 17.11.14
Honor 8 FRD-L19

Reputation:-  78  +

sort of won.
So, success story:
preamble: if you encoded / encrypted the phone, then when you flash the cyan a surprise awaits you: boot loop at the twrp stage

Ambula: it seems that unlocking the boot does not format some partitions in Fat / ext / etc ... as a result TWRP cannot format something there (unfortunately, I did not have time to read everything he writes) and goes to reboot, and the reboot is again in TWRP, and so on a circle ... was tested on different TWRPs - the result is the same, the firmware of the system image itself did not reach the firmware.

I managed to win by installing a stock firmware (referring to the header) and repeating the TWRP firmware. It seems that a simpler recipe is to format the userdata and system partitions via fastboot, but I did not check it already (it was midnight, I wanted to sleep).

the experiments were carried out under the close supervision of G3Denver, for which he bowed deeply.

I would strongly recommend adding information about encrypted sections to the manual, so that people with weak hearts would not fall from a heart attack, realizing that instead of a telephone they had a cyclic tamagotchi :)

P.S.
G3Denver @ 05/26/2016, 10:23 PM*
After that, you need to format Data from TWRP. Today I faced this with a friend on the device

This is harmful advice, or rather not feasible, since TWRP does not do anything at all, only fastboot helps (fortunately I have a linux home)

Post has been editedhoopoepg - 27.05.16, 10:34


--------------------
Honor 8
DinD_Ykt
Message#37
01.06.16, 13:08
a guest
*******
[offline]

Group: Friendssavagemessiahzine.com
Messages 730
Check in: 10.05.13
ZTE Nubia Z17 6 GB RAM

Reputation:-  209  +

CyanogenMod / LineageOS 11

Attached Image

with latest google patches


Due to the fact that I changed my device for a long time (may the kingdom of heaven be) and finally got back the machine for assemblies (with less performance than the previous one), the assemblies may be non-working (I collected them blindly, without the device itself ). So, if you are going to flash these assemblies (starting from LineageOS 11, 11.03.2017), then you do it at your own peril and risk.


Security Update: February 1, 2017

Requirements:
- Device: hammerhead (not hammerheadcaf)
- Bootloader:AnyFrom 11.03.2017 - HHZ11k / HHZ12d
- Radio: preferably from KitKat
You can get the required versionshere.

What's new ?
- Latest google patches
- Fixes to December / 14 - March / 17
- Well, that's it.

Sources:
- Device
- Kernel
- Proprietary blobs
- local manifest

Download:
- dropbox.com(Obsolete)
- AndroidFileHost.com (CM 11 / LOS 11)
- Yandex.Disk (CM 11 20160611)
Picture


Post has been editedfreetushkan - 18.06.18, 20:16
Reason for editing: In the header.


--------------------
CEO DevelopedInside
Lenovo Legion Y530-15ICH - 81FV0027RU (Win10Home / Linux Mint 19)
ZTE Nubia Z17 - LineageOS 15.1-dev-test
Oneplus one - LineageOS 11-continue-support
freetushkan
Message#38
25.06.16, 21:48
Stupid tester
*******
[offline]

Topics Curator
Group: Curators
Messages 764
Check in: 27.12.11
Xiaomi Mi A1 4/64

Reputation:-  126  +

Collection Radio, Bootloader and TWRP.

On24.10.2018current are:
Bootloader:HHZ20H |Radio:M8974A-2.0.50.2.30 |Recovery:TWRP 3.2.3-0

These components and their previous versions are assembled into universal aroma-installers for convenient firmware from recovery.
Archives include universal (AOSP + CAF) images TWRP and MultiROM-TWRP. After installationreboot requiredrecovery


Actual
(latest versions of Bootloader, Radio and current TWRP)
Attached file20180503-Flasher-Actual.zip(48.11 MB)
AndroidFileHost.com

Marshmallow
(all versions of Radio, Bootloader, released for 6.x, and current TWRP)
AndroidFileHost.com

Lollipop
(all versions of Radio, Bootloader, released for 5.x, and current TWRP)
AndroidFileHost.com

Kitkat
(all versions of Radio, Bootloader, released for 4.4.x, and current TWRP)
AndroidFileHost.com


Matching Android builds
Attached Image

Name Ver. Build bl radio
KitKat 4.4 KFS78N * 1 HHZ10X M8974A-1.0.25.0.12
KitKat 4.4 KQS81M * 2 HHZ11A M8974A-1.0.25.0.13
KitKat 4.4 KRT01B * 3 HHZ11B M8974A-1.0.25.0.15
KitKat 4.4 KRT16M HHZ11D M8974A-1.0.25.0.17
KitKat 4.4.1 KOT49E HHZ11K M8974A-1.0.25.0.23
KitKat 4.4.2 KOT49H HHZ11K M8974A-1.0.25.0.23
KitKat 4.4.3 KTU84M * 4 HHZ11K / N M8974A-2.0.50.1.13
KitKat 4.4.4 KTU84P HHZ11K M8974A-2.0.50.1.16
KitKat 4.4.4 KTU84Q * 5 HHZ11K M8974A-2.0.50.1.17
Android L DP 5.0 LPV79 HHZ11K M8974A-2.0.50.2.08
Android L DP 5.0 LPV81C HHZ11K M8974A-2.0.50.2.08
Android L DP 5.0 LRX13D HHZ12D M8974A-2.0.50.2.21
Lollipop 5.0 LRX21O HHZ12D M8974A-2.0.50.2.21
Lollipop 5.0.1 LRX22C HHZ12D M8974A-2.0.50.2.22
Lollipop 5.1.0 LMY47D HHZ12F M8974A-2.0.50.2.25
Lollipop 5.1.0 LMY47I HHZ12F M8974A-2.0.50.2.25
Lollipop 5.1.1 LMY48B HHZ12H M8974A-2.0.50.2.26
Lollipop 5.1.1 LMY48I HHZ12H M8974A-2.0.50.2.26
Lollipop 5.1.1 LMY48M HHZ12H M8974A-2.0.50.2.26
Android M DP 6.0 MPZ44Q HHZ12H M8974A-2.0.50.2.26
Android M DP 6.0 MPZ79M HHZ12H M8974A-2.0.50.2.26
Android M DP 6.0 MPA44G HHZ12I M8974A-2.0.50.2.27
Android M DP 6.0 MPA44I HHZ12I M8974A-2.0.50.2.27
Marshmallow 6.0 MRA58K HHZ12K M8974A-2.0.50.2.27
Marshmallow 6.0 MRA58N HHZ12K M8974A-2.0.50.2.27
Marshmallow 6.0.1 MMB29K HHZ12K M8974A-2.0.50.2.28
Marshmallow 6.0.1 MMB29S HHZ12K M8974A-2.0.50.2.28
Marshmallow 6.0.1 MMB29Q HHZ12K M8974A-2.0.50.2.28
Marshmallow 6.0.1 MMB29V HHZ12K M8974A-2.0.50.2.28
Marshmallow 6.0.1 MMB29X HHZ12K M8974A-2.0.50.2.28
Marshmallow 6.0.1 MOB30D HHZ20B M8974A-2.0.50.2.29
Marshmallow 6.0.1 MOB30H HHZ20F M8974A-2.0.50.2.29
Marshmallow 6.0.1 MOB30M HHZ20F M8974A-2.0.50.2.29
Marshmallow 6.0.1 MOB30P HHZ20G M8974A-2.0.50.2.29
Marshmallow 6.0.1 MOB30Y HHZ20H M8974A-2.0.50.2.29
Marshmallow 6.0.1 MOB31E HHZ20H M8974A-2.0.50.2.29
Marshmallow 6.0.1 M4B30X HHZ20H M8974A-2.0.50.2.30
Marshmallow 6.0.1 M4B30Z HHZ20H M8974A-2.0.50.2.30

* 1 - LGD821 factory FW
* 2 - LGD820 factory FW
* 3 - B - means Buggy, graphical glitches in HHZ11B
* 4 - LGD820-late was shipped with HHZ11N
* 5 - LGD821 - New Zealand / Australia / India

Screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image

Information
Unnecessary elements can be freely removed from the archives, as well as adding while maintaining the file structure - the list will be generated automatically upon launch.
  • Compatibility guaranteedonly with TWRP(any versions). CWM / PhilZ / CM Recoverynot supported.
  • In the root of each archive are prop-files in which you can change the assembly information, their presencenecessarily.
  • The presence of spaces in the names of directories and in the values ​​of prop-filesis unacceptable.
  • Directory names (img, bootloader, radio, recovery) must be in lower case.
  • Each version is stored in a separate directory, whose name is the name in the list.
  • In the directory of each version there is an "info.txt" file that serves as the description in the list.
  • MultiROM-TWRP is quite outdated and may be incompatible with current distributions. Tassadar and Captain_Throwback have ceased operations.

Build 20180503 - ~ 700 downloads.
Past builds - ~ 7318 downloads.


Change history
    03.05.2018
  • TWRP updated to 3.2.1-1.

    27.06.2017
  • TWRP updated to 3.1.1-0.
  • MultiROM-TWRP updated to 3.1.0-0.

    11.03.2017
  • TWRP in all packages replaced by a new version 3.1.0-0.
  • M8974A-2.0.50.2.26 and HHZ12H, released for Lollipop, but also used in Android M, have been added to the Marshmallow package.
  • HHZ11K has been added to the Lollipop package, released for KitKat, but also used in Android L.
  • Mega package abolished.

    14.02.2017
  • Extension of the TWRP version list.
    More details
    Added versions TWRP-3.0.3-0 and MultiROM-TWRP-3.0.3-0. TWRP-3.0.2-0 also remained (except for the "Actual" package).
    All images are self-made, suitable for installing both CAF and AOSP firmware. The actual base is AOSP, default.prop has been changed in ramdisk to pass updater-script checks.
  • Changes in the package.
    More details
    Packages "Minimal" and "Actual" are combined into one. Now "Actual" contains bootloader and radio images one at a time, as well as the universal TWRP 3.0.3-0 (+ MultiROM version).
  • Use the "busybox" binary to improve compatibility.

    06.11.2016
  • Fix firmware recovery.

    06.10.2016
  • New radio M8974A-2.0.50.2.30 (all packages).
  • Updated list of assemblies in packages.
  • Minor edits.

    04.10.2016
  • New radio M8974A-2.0.50.2.30 (Actual only).

    04.09.2016
  • Fix for Minimal, Marshmallow and Mega packages.
    (dated 02092016)


    02.09.2016
  • Replacing decompression processing listing "IMG /". Removed the need for "info.txt". Category directory names must begin with a capital letter.
  • Added check for "generated_form".
  • Transferring list generation to the beginning of the aroma script.
  • The order is "new first" as it was before.
  • Larger font in build information.
  • Tip in the description of the backup bootloader option "(VolUp + VolDown + Power)".
  • Removed the Material Darkgreen theme. "
  • The names of the directories with the versions of recovery are similar to the directories of the bootloader and radio.

    13.08.2016
  • Dynamic generation of a selection list in the installer, depending on the contents of the archive. Easier build packages, without the need to manually edit the file list.
    More details
    Aroma Installer’s standard tools cannot dynamically compile a list, so you need to call a shell script that runs through the archive and generates a form that Aroma picks up. If suddenly something goes wrong, a window will appear prompting you to independently install the current recovery, reboot and repeat the installation, or use the Minimal package, in which there is no generation.
  • Added forgotten bootloader HHZ12I (Android Android M-D).

    08.08.2016
  • The first build includes more than one version for each type of image.
  • Correction of dialogue in the topic Material.
    More details
    The dialog used in the used theme does not work. The phone completely hangs when you open the information about the build, exit and save the log. Helps only hold the power button.
    First, OpenGApps came to this rake in their Aroma-package, from where I got the theme. The original theme developer has subsided somewhere in Belarus and does not show signs of life for more than a year.
    Corrected. OpenGApps developerstook note and also correct.
  • Backup bootloader firmware function (VolUp + VolDown + Power) (carefully).

Past versions
20170627
Attached file20170627-Flasher-Actual.zip(49.24 MB)

The rest of the archives can be found atAndroidFileHost.com.

Picture


Post has been editedfreetushkan - 25.10.18, 02:14
Reason for editing: TWRP 3.2.3-0 released - I will update the builds whenever possible.


--------------------
Purely not where they clean well, but where they do not litter.
CollectionRadio, Bootloader and TWRPfor Nexus 5
patrad
Message#39
09.07.16, 19:36
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 87
Check in: 17.10.14
Xiaomi Redmi Note 4X Snapdragon 3/32

Reputation:-  16  +

Bomj_unskull @ 07/09/16, 19:25*
Began to notice that over time, the phone starts to podglyuchivat. After a reboot, everything becomes good for a while.
What could it be ? Can this be solved without swapping the firmware?

Try to executefstrim.
K
In the Mini FAQ(22.02.2017)


Post has been editedfreetushkan - 22.02.17, 16:53
igorvain1
Message#40
13.07.16, 17:04
a guest
*
[offline]

Group: Users
Messages 7
Check in: 12.04.14
Xiaomi Mi 6 6/64

Reputation:-  0  +

mogno pogalusto poluchiti LINK?
danie ne udalitsia?
M
Read theForum Rules- Check outForum Rules!
3.1.The official forum language - Russian. The official language of the forum is Russian.
3.2.All posts must be written in Cyrillic. All messages must be written in Cyrillic.
Recommended to use the translation services.


Post has been editedMalfurion - 13.07.16, 17:11
TTe4oPuH
Message#41
17.07.16, 12:12
Student • Physicist
********
[offline]

Group: Friendssavagemessiahzine.com
Messages 1487
Check in: 21.10.14
Google Nexus 5X

Reputation:-  1804  +

System dump cm-13.0-20160717-NIGHTLY-hammerhead
Picture



Post has been editedG3Denver - 17.07.16, 12:38


--------------------
N5X- Dark Rom 7.1.2
Google
 

17 pagesV  < 1 2 3 4 5 6 > » 


 mobile version    Now: 04/18/19, 15:18