Cyanogenmod 13 for LG G Pro 2 D838, CM14.1

Cyanogenmod 13 for LG G Pro 2 D838, CM14.1 - LG G Pro 2

Other stuffs:
1. Increase volume on older cm13 builds - https://drive.google.com/file/d/0B0LH2ajSZjDpY3JuSm9ERmkyLWs/view?usp=sharing
I also try to fix lineout but not test lineout.
2. Remove black rectangle on incoming call photo in dialer( tested on CM13) - https://drive.google.com/file/d/0B0LH2ajSZjDpeWpwbFdkWFZmMGs/view?usp=sharing
CM14.1 08.12.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://mega.nz/#!IEt2hAwT!d8muFzv47Ot7a8aMWn59wGLdrUWG9iuGWAj4r7JIFuc
i don't test this Rom - only build.
CM13 08.12.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://mega.nz/#!MNNQWABB!tsc_dxAW8_WWvfyVOGflOoQRJjk3l3z6mqMro8_cojQ
Kernel, devtree, cm updates.
i don't test this Rom - only build.
CM14 19.09.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpelFkNE92MVBzVWs/view?usp=sharing
First build, only for testing. Now i don't have device on the hands.
i don't test this Rom - only build.
Small CM14 russian screencast - https://drive.google.com/file/d/0B0LH2ajSZjDpcGNSbmlEdElNZEU/view?usp=sharing
Now i update device sources and add cm 14.1 tree.
Manifest for cm 14.1
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="xenius9/android_device_lge_d838" path="device/lge/d838" remote="github" />
<project name="xenius9/android_device_lge_b1w-common" path="device/lge/b1w-common" remote="github" />
<project name="xenius9/proprietary_vendor_lge_b1w" path="vendor/lge" remote="github" />
<project name="xenius9/android_kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" />
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" />
<project name="CyanogenMod/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
</manifest>
Old Manifest:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="xenius9/android_device_lge_d838" path="device/lge/d838" remote="github" revision="cm-14.0"/>
<project name="xenius9/android_device_lge_b1w-common" path="device/lge/b1w-common" remote="github" revision="cm-14.0"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.0"/>
<project name="xenius9/android_kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="cm-14.0"/>
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.0"/>
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-14.0"/>
<project name="xenius9/proprietary_vendor_lge_b1w" path="vendor/lge" remote="github" revision="cm-14.0"/>
</manifest>
CM13 build instruction:
1. Install ubuntu
2. We start with setting up the build environment:
First, start with installing this:
sudo apt-get install bison build-essential curl flex git gnupg gperf libesd0-dev libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-
utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev
lib32readline-gplv2-dev lib32z1-dev
3. Once that is done, we go about installing JDK-7 since that's the one that works for lollipop
sudo apt-get install openjdk-7-jre
sudo apt-get install openjdk-7-jdk
4. Then we install the Android SDK for some useful stuff:
sudo apt-get install android androidsdk-uiautomatorviewer android-copyright android-src-vendor android-emulator android-tools-adb android-headers
android-tools-adbd androidsdk-ddms android-tools-fastboot androidsdk-hierarchyviewer android-tools-fsutils androidsdk-traceview
5. Once all that is dealt with, we can move on to the repo tool. That's what will get your CM repos syncing:
mkdir -p ~/bin
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
and then, reboot to apply the changes.
Now for the interesting part
Not really, actually.
Time to yank the CM source code.
Create a working directory where you're going to sync all the sources and do the dirty stuff.
For this guide, we'll call the working directory "cm13"
Create the directory by running
mkdir cm13
enter your working directory by typing
cd cm13
6. Inititialize the repo by throwing in:
repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0
Wait for all the activity in the terminal to cease. And then type in:
repo sync
if needed post user information when promted
while the stuff is downloading, grab a ginger ale, or a cup of coffee and admire your handiwork. If you're the impatient type, find a generous
dose of your favourite sedative, and knock yourself out for a few hours. When you're up again, you'll be faced with one of two things. Either
your repos have synced successfully (yay!), or you get some nasty fetch errors. If it's the latter, then, Voila! You've just faced your first
ever compiling frustration. Take some time out and break a few things, drive the neighbours crazy and then return to the PC and knock in:
repo sync -j1
This should (hopefully) work perfectly as long as you have an internet connection worth paying for. If not, then compiling probably isn't for you
anyway.
7. Once all that stuff's over, create a folder called
local_manifests
in the .repo folder, and then make a new file in that folder called
roomservice.xml
open roomservice.xml using gedit, and add the following:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="xenius9/android_device_lge_d838" path="device/lge/d838" remote="github" revision="cm-13.0"/>
<project name="xenius9/android_device_lge_b1w-common" path="device/lge/b1w-common" remote="github" revision="cm-13.0"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0"/>
<project name="xenius9/android_kernel_lge_msm8974" path="kernel/lge/msm8974" remote="github" revision="cm-13.0"/>
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0"/>
<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-13.0"/>
<project name="xenius9/proprietary_vendor_lge_b1w" path="vendor/lge" remote="github" revision="cm-13.0"/>
</manifest>
Then cd back to your working directory
cd ~/cm13
8. YOU'RE READY TO ROLL!
Finally, to build, type in:
. build/envsetup.sh
brunch d838
9. Wait for the build to compile. Usually takes about 2-3 hours on an okay PC. You'll find your completed build in cm13/out/target/product/d838.
The next time you want to build, run:
make clean
repo sync
. build/envsetup.sh
brunch d838
.. and so on.
Happy Building!
CM13 24.10.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpV1BGVjNycFBwSzg/view?usp=sharing
news: CM updates, kernel updates
i don't test this Rom - only build.
CM13 19.09.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpZFFKaXJ4V0tWems/view?usp=sharing
news: CM updates, kernel and devtree updates
i don't test this Rom - only build.
CM13 24.08.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpTUFGVkRQbGlmb2s/view?usp=sharing
news: CM updates, kernel and devtree updates, possible fix offline charging
i don't test this Rom - only build.
CM13 22.08.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpbGJqVnI5aEpDbDA/view?usp=sharing
news: CM updates, kernel and devtree updates, possible fix some errors
i don't test this Rom - only build.
CM13 18.08.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpZFF6NG50RGwtVjA/view?usp=sharing
news: CM updates, kernel and devtree updates.
i don't test this Rom - only build.
CM13 21.07.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpS0JFMGdDeGhzUDA/view?usp=sharing
SuperSu Kernel with voltage control for 19-21.07 builds - https://drive.google.com/file/d/0B0LH2ajSZjDpeDA5RTdnSWFBT1k/view?usp=sharing
Kenel with voltage control for 19-21.07 builds - https://drive.google.com/file/d/0B0LH2ajSZjDpSHdxOTExOFRQUEk/view?usp=sharing
news: CM updates, voltage control in kernel.
i test this Rom - boot - ok, calls - ok.
Older builds and info:
CM13 19.07.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpbmRHN2IxSk5STG8/view?usp=sharing
SuperSu Kernel - https://drive.google.com/file/d/0B0LH2ajSZjDpMVpmd24yXzNuQzg/view?usp=sharing
news: CM updates, cosmetic fix for charging speed, fix wakeup when proximity covered, fix errors in voice and gps config, try to add line_out.
i test this Rom - boot - ok, calls - ok.
CM13 13.07.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpUGxCSWR3cDFWYkk/view?usp=sharing
news: CM updates, wifi and BT mac from misc partition, increased audio volume, viper4android preinstalled(enable root in dev options and use selinux mode changer for set selinux to permissive), other camera wrapper(from g3) and added 2160p profile for video recording, fixed fstab.
i test this Rom, mac`s reading from misc and set ok for me - no random mac.
CM13 04.07.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpdmlwMkNzUG5KdkE/view?usp=sharing
news: CM, devtree and kernel updates
i don`t test this Rom, only build(with no errors)
CM13 6.06.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/open?id=0B0LH2ajSZjDpdHRJOXo2OEF2dVE
Advanced ROM (integrated SuperSu, Viper4Android) - https://drive.google.com/file/d/0B0LH2ajSZjDpdVNYODVXTXplOUk/view?usp=sharing
Patched kernel for SuperSu - https://drive.google.com/file/d/0B0LH2ajSZjDpeFNnMGlzTFkwU28/view?usp=sharing
A-GAPPS - see here - http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606 (need internet connection for setup, you must flash gapps immediately after flashing ROM)
news: CM and kernel updates
CM13 26.05.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpWER6dHZpcFl3ZjQ/view?usp=sharing
news: CM and kernel updates, added quickcircle from g4 - for testing.
CM13 25.05.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpTDJBRUFVYVZEekU/view?usp=sharing
news: CM updates, added echo reference to mixer_patchs, fixed double tape to wake -now it`s worked)))
ROM tested - boot normal, sounds play , calls - calling, Double Tap to Wake worked Oooo )))
Patched kernel for SuperSu - https://drive.google.com/file/d/0B0LH2ajSZjDpeTA1OUdUS2JNSVk/view?usp=sharing
For China`s users - all SDCard filesystem types supported, not only fat32
CM13 24.05.2016 build
Stock ROM (as is, no loaders, modem, etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpeDczM1JWeDBrSk0/view?usp=sharing
news: CM updates, kernel updates, mixer_patchs levels up, try to add dt2wake(not tested by me - for devs)
i build this ROM only, not test - no time.
CM13 10.05.2016 build
Advanced ROM (integrated SuperSu, Viper4Android, A-Gapps(you need flash modem and loader if you on kitkat rom now)) - https://drive.google.com/file/d/0B0LH2ajSZjDpNFg0TWJxd1VNamc/view?usp=sharing
Full ROM (for flashing over any ROM)(modem, rpm, kk loader included) - https://drive.google.com/file/d/0B0LH2ajSZjDpc0VETkk3dk5zX3M/view?usp=sharing
Stock ROM (as is, no loaders, modem,etc..) - https://drive.google.com/file/d/0B0LH2ajSZjDpYWkyMnVEZXpodzA/view?usp=sharing
Modem and loader only (only modem, rpm and kitkat loader) - https://drive.google.com/file/d/0B0LH2ajSZjDpeXNnRFhFRlFGbHc/view?usp=sharing
Supersu kernel - https://drive.google.com/file/d/0B0LH2ajSZjDpWjBYRW5hcmp3ZUk/view?usp=sharing (flash after you flash Supersu installer)
news: CM updates, some kernel updates, revert mixerpath config
CM13 04.05.2016 build - https://drive.google.com/file/d/0B0LH2ajSZjDpYmh4bEFCSG1RNEE/view?usp=sharing
Full ROM (for flashing over any ROM)(modem, rpm, kk loader included) - https://drive.google.com/file/d/0B0LH2ajSZjDpNjJoZS1LWFo0QW8/view?usp=sharing
news: CM updates, some devtree and kernel updates, audio policy updates
CM13 29.04.2016 build - https://drive.google.com/file/d/0B0LH2ajSZjDpMTA1RG45cko4d0U/view?usp=sharing
news: CM updates, some devtree updates
TWRP 3.0.2-0 Recovery (port) for LG G Pro 2:
https://drive.google.com/file/d/0B0LH2ajSZjDpalVsQmpoTDBfTUE/view?usp=sharing
CM13 21.04.2016 build - https://drive.google.com/file/d/0B0LH2ajSZjDpWnlzVEg5WjZUMk0/view?usp=sharing
news: CM updates, 32 dip navbar
if you want selinux permissive - install supersu and kernel for SuperSU
if you want to use SuperSu, download it from https://download.chainfire.eu/927/SuperSU/RC-SuperSU-v2.70-20160314191951.zip and AFTER you flash SuperSu flash this:
Kernel for SuperSU https://drive.google.com/open?id=0B0LH2ajSZjDpUDYwV2JsOWFGTWM (bumped kernel patched for supersu)
CM13 18.04.2016 build - https://drive.google.com/file/d/0B0LH2ajSZjDpT2piYVRyeXpOSm8/view?usp=sharing
news: NFC fixed, kernel and devtree updates, possible ir blaster working too.
if you want to use SuperSu, download it from https://download.chainfire.eu/927/SuperSU/RC-SuperSU-v2.70-20160314191951.zip and AFTER you flash SuperSu flash this: https://drive.google.com/file/d/0B0LH2ajSZjDpZGVTeTV1N1pZX3c/view?usp=sharing (bumped kernel patched for supersu)
ROM link - https://drive.google.com/file/d/0B0LH2ajSZjDpZkZDSU5sUzlReFk/view?usp=sharing
FOR KK BOOTLOADER!!!
What's not working: NFC, you tell me)))
What's working: microsd(fat32), charging, camera, bluetooth, GPS, sound, phones, calls, sensors.
How to flash(you need recovery - TWRP is better(marshmallow support)):
1. MAKE BACKUP!!!
2. Push baseband and ROM to sdcard (copy cm13 zip and LP Baseband to sd card)
3. Make WIPE dalvik, data,cache(from recovery)(advanced wipe in twrp)
4. Install lollipop baseband
5. Install ROM
Additional links:
KK Baseband and kernel - https://yadi.sk/d/nVx3rb7MpheN9
LP Baseband and kernel(bumped)+KK bootloader - https://yadi.sk/d/_hz4jdQhpheNn
How to Restore previous ROM:
1. if you have KK based Rom - flash KK Baseband and restore ROM from Recovery
2. if you have LP based Rom - flash LP Baseband and restore ROM from Recovery

hell yeah, it amazing fast ever, testing now on f350s, seems everything good but nfc, will report later.
update: i think this rom can daily use for me live without double tap and nfc/IR, no fc and very fast on f350s.
update 2: few days gone, everthing good battery good no any fc. @xenius9, can you add IR remote in ROM further?
http://forum.xda-developers.com/lg-g3/themes-apps/app-quickremote-port-aosp-t2929146

BUG: double tap screen and nfc.
Testing on d838.

Also testing on D838, for now, only NFC and DT2W doesn't works.

if I'm on KK
i just flash the KK Baseband and kernel then flash your rom???

ares. said:
if I'm on KK
i just flash the KK Baseband and kernel then flash your rom???
Click to expand...
Click to collapse
Flash lollipop baseband and rom.

i just installed it..noob question where can i download gapps for cm13? i tried open gapps its not working when i flash it tnx..what gapps did you use guys? tnx
.i would never imagine we will have a cm13 marshmalow for lg g pro 2! awesome xenius9

pato2015 said:
i just installed it..noob question where can i download gapps for cm13? i tried open gapps its not working when i flash it tnx..what gapps did you use guys? tnx
.i would never imagine we will have a cm13 marshmalow for lg g pro 2! awesome xenius9
Click to expand...
Click to collapse
You can download gapps below
http://opengapps.org/
Sent from my LG-D838 using XDA-Developers mobile app

stevenhehe said:
You can download gapps below
http://opengapps.org/
Sent from my LG-D838 using XDA-Developers mobile app
Click to expand...
Click to collapse
tnx..no wonder it cant install my gapps for 5.0 not 6.01 heheh..downloading gapps for 6.01 now
---------- Post added at 03:41 PM ---------- Previous post was at 03:12 PM ----------
how to turn on root for this cm13 rom... i installed super su..binary cant be updated..im i doing wrong here? sorry as this is my first cm rom

pato2015 said:
tnx..no wonder it cant install my gapps for 5.0 not 6.01 heheh..downloading gapps for 6.01 now
---------- Post added at 03:41 PM ---------- Previous post was at 03:12 PM ----------
how to turn on root for this cm13 rom... i installed super su..binary cant be updated..im i doing wrong here? sorry as this is my first cm rom
Click to expand...
Click to collapse
You can enable root in development option
Sent from my LG-D838 using XDA-Developers mobile app

and lastly anyone tried installing xposed on this?

xposed work perfect.

xenius9 said:
Flash lollipop baseband and rom.
Click to expand...
Click to collapse
Lg camera knock code touch keys white background and small keys plzz
Sent from my LG-D838 using XDA-Developers mobile app

mydoom said:
xposed work perfect.
Click to expand...
Click to collapse
may i ask what xpose version did you use? 80?
---------- Post added at 09:28 PM ---------- Previous post was at 09:22 PM ----------
how did you install super su...everytime i install super su from playstore run binary it fails ...already turn on rooted on developer option..what shall i do tnx

pato2015 said:
and lastly anyone tried installing xposed on this?
Click to expand...
Click to collapse
i am using 81
pato2015 said:
may i ask what xpose version did you use? 80?
---------- Post added at 09:28 PM ---------- Previous post was at 09:22 PM ----------
how did you install super su...everytime i install super su from playstore run binary it fails ...already turn on rooted on developer option..what shall i do tnx
Click to expand...
Click to collapse
gone system>about phone>built number>10 time>develo mode>root access> open

Does cm13 support slimport/hdmi?
Sent from my LG-D838 using XDA-Developers mobile app

When using cm 13 ROM do we need to install super su or we can use the cm built in root app to handle rooting accept deny thing on our phone..?
---------- Post added at 02:12 AM ---------- Previous post was at 02:01 AM ----------
mydoom said:
i am using 81
gone system>about phone>built number>10 time>develo mode>root access> open
Click to expand...
Click to collapse
Thanks care for the link of xpose 81..how did you install? Just install apk alpha 4 and flash 81?
Updated...it works so well with cm 13

Im on LP5.0.1
Should i return to stock 4.4 before start? or i can start now

pato2015 said:
When using cm 13 ROM do we need to install super su or we can use the cm built in root app to handle rooting accept deny thing on our phone..?
---------- Post added at 02:12 AM ---------- Previous post was at 02:01 AM ----------
Thanks care for the link of xpose 81..how did you install? Just install apk alpha 4 and flash 81?
Updated...it works so well with cm 13
Click to expand...
Click to collapse
Why you guys love using xposed?
For me, I had used it several times and it just made my phone lag!
Sent from my LG-D838 using XDA-Developers mobile app

I think you need add kikat bootloader and lolipop baseband to your rom for anyone don't know how to flash it

Related

[ROM][CM] KitKang Rom CM11 Kangs (**Building Guide Now Included!!)

Welcome to KitKang ROM!
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* or you getting fired because the alarm app failed. Please do
* some research if you have any concerns about features included
* in this ROM before flashing it! YOU are choosing to make these
* modifications, and if you point the finger at us for
* messing up your device, we will laugh at you.
Click to expand...
Click to collapse
Description:
KitKang ROM is a ROM built from the CyanogenMod 11 source, with some cherrypicks added for features and functionality.
Bugs List:
Code:
-???
Current CherryPicks
Code:
#56346 LockScreen: allow long-press actions from hardware keys (1/2)
#56357 LockScreen: allow long-press actions from hardware keys (2/2)
#55209 Forward port Status Bar interface (1/2)
#55211 Forward port Status Bar settings (2/2)
How To Flash:Coming From a Different ROM?
1. Make sure you are unlocked and running the latest version of ClockworkMod Recovery (Either Touch or Non-Touch is fine). If you do not know how to unlock your bootloader or install recovery, follow these steps.
2. Make sure you are running the latest firmware version. If you do not know what firmware version you are running, you can check in Settings in the "About Phone" tab. Currently, the latest firmware is VRBMF1, and a recovery flashable of the firmware can be found here. To install, simply reboot to ClockworkMod and flash the zip file.
3. Backup everything you need. All of your files will be deleted! To backup your apps, I recommend using Helium. It is very easy and straightforward.
4. Download the ROM and G-Apps from the links provided and copy them over to your phone via USB cable.
5. Reboot to recovery. To do so, either use the built in reboot option to recovery in ROMs such as CyanogenMod, or power down and hold Power + Home + Vol Up and you should be in recovery.
6. Wipe the data, system, cache, and dalvik cache partitions in recovery. (Dalvik wipe is located in Advanced Settings)
7. Install the ROM and G-Apps files
8. Reboot and setup your phone!
Click to expand...
Click to collapse
Updating From A Previous KitKang Nightly?
1. Download the ROM and G-Apps from the links provided and copy them over to your phone via USB cable.
2. Reboot to recovery. To do so, either use the built in reboot option to recovery in ROMs such as CyanogenMod, or power down and hold Power + Home + Vol Up and you should be in recovery.
3. Wipe the cache and dalvik cache partitions in recovery. (Dalvik wipe is located in Advanced Settings)
4. Install the ROM and G-Apps files
5. Reboot!
Click to expand...
Click to collapse
Download Links
ROM DOWNLOAD
(Note: This is a folder, and has all of my builds. Download the one you want. If you don't know what to download, use the latest.
G-APPS DOWNLOAD
KANGED G-APPS DOWNLOAD
Not supported or recommended because of stability issues. However, this does include the new dialer with Google Search support. Use with caution. If you do not know which G-Appps package to use, use the first link.
Enjoy?
If you enjoy the ROM, please consider sending me a donation

XDA:DevDB Information
KitKang Rom CM11 Kangs, a ROM for the Verizon Samsung Galaxy S III
Contributors
dmeadows013, XRaptor29, cammykool, tvall
ROM Kernel: Linux 3.4.x
ROM Firmware Required: VRBMF1
Based On: CyanogenMod
Version Information
Status: Testing
Created 2013-11-14
Last Updated 2014-01-01

Guide to Building
Guide for Building KitKang on Mac OSX
This is a guide demonstrating how to build KitKang for yourself on Mac. I am not responsible for anything you do to your computer or your phone as a result of following this guide. Before building, I would recommend that you have at least a little knowledge of Terminal, and a powerful computer. AOSP takes up a lot of resources, and even my i7 Ivy Bridge build with 16GB RAM and an SSD takes almost an hour to build. The AOSP code takes up a lot of space, so I recommend AT LEAST 150GB free space, just to be safe. This guide involves installing specific packages to build AOSP. To install these packages, we will use Homebrew. You will also need XCode to build. If you do not have these installed, refer to the beginning of the guide. If you already have these installed for some reason, skip the first section for installing XCode and Homebrew.
Click to expand...
Click to collapse
Installing XCode/Homebrew
Download and install XCode from the Mac App Store. You will need an Apple account to do this.
After downloading and installing XCode, you will need the Command Line Tools. These can be installed by opening a Terminal window and entering:
Code:
xcode-select --install
After entering this, hit return and a box should pop up asking you if you want to install Command Line Tools. Click yes, and wait for it to install.
Now, make sure you have the latest Java Runtime. You do this in Terminal by entering a command and going through an installation process. Enter the command
Code:
java
With the Command Line Tools and Java installed, we can now install Homebrew. To do so, open Terminal again and enter the following:
Code:
ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go/install)"
Make sure Homebrew is installed and works correctly by running
Code:
brew doctor
If you got errors in the previous command, try googling to see if there is something else you need. If you can run the command without errors, you are good to go!
We must now move the SDK so the build recognizes what to use. To do this, run the following commands in Terminal
Code:
sudo mkdir /Developer
Code:
sudo mkdir /Developer/SDKs
Code:
sudo cp -r /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk /Developer/SDKs/MacOSX.sdk
NOTE: You need superuser permissions to run the previous 3 commands.
Now, in Terminal, type
Code:
nano ~/.bash_profile
If you get a no file found error, then run
Code:
nano -w ~/.bash_profile
You should get a screen with some text. Scroll to the bottom using the arrow keys until there's just blank spaces, and paste the following code
Code:
export BUILD_MAC_SDK_EXPERIMENTAL=1
Save the file using ctrl-x and clicking yes and enter
Restart Terminal to make the changes take effect
With Homebrew now installed, we can continue to downloading required build packages!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installing Required Packages
Now we will install packages required to build the AOSP source. This can be done with the Terminal command
Code:
brew install git coreutils findutils gnu-sed gnupg pngcrush repo
With these packages installed, we need to make some symlinks so that OSX knows which files to use, and doesn't mess up the build. To do this, enter
Code:
ln -s /usr/local/bin/gfind /usr/local/bin/find && ln -s /usr/local/bin/gsed /usr/local/bin/sed
With these packages installed, we are now ready to create a build environment and download the AOSP source.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Preparing the Build Environment and Downloading the Source
First, we need to create a dedicated workspace for our AOSP code. This can be done in Terminal by entering
Code:
hdiutil create -type SPARSE -fs "Case-sensitive Journaled HFS+" -size 120g -volname "android" -attach ~/Desktop/Android
This will create the workspace image on our desktop. To move it, simply drag and drop in Finder to the location you want.
Now, locate the workspace in Finder and double click it to mount it
NOTE: If you moved your workspace to a different directory, you will have to use the path to that directory in the previous step.
Next, from within Terminal, locate the directory by typing
Code:
cd /Volumes/android
Now that we are in the working directory, it is time to download the Android Source. This is done by entering the following command
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0 && repo sync && say 'finished'
Wait for the download to finish. Depending on your connection, it can take a long time, so get comfortable.
When the download finishes and you can see all of the source folders in your directory, it is time to download the S3 specific files. To do this, we need to edit the roomservice.xml. However, this file is hidden. We can access it by entering the following in Terminal
Code:
open -a TextEdit .repo/local_manifests/roomservice.xml
You should get a blank file in TextEdit. Enter the following code as is here
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_d2vzw" path="device/samsung/d2vzw" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_d2-common" path="device/samsung/d2-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_d2" path="kernel/samsung/d2" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
Save and close the file, and again run
Code:
repo sync
With the S3 specific files downloaded, we need to download the CyanogenMod specific app files. This can be done by running
Code:
./vendor/cm/get-prebuilts
With this done, we need to download the cherrypicks specific to the S3. Eventually, these will not be needed, but as CyanogenMod 11 is still in beta, it is needed for now. Because the cherrypicks are often being merged, and new ones created, the kind folks at CyanogenMod have created a Google Document with a list of the latest commits. This is located here. NOTE: This document does not include any cherrypicks that I may include for features. By using these cherrypicks, you are installing everything needed to make the ROM as stable as possible. I may occasionally include other cherrypicks that I find enhance features. Inside the document, scroll down to the '# repopicks' section and continue scrolling past the commit messages. At the bottom, you will see a section titled 'Combined'. This will have a command such as
Code:
repopick -s s <List of commit hashes>
You could simply copy this command and paste it into a Terminal window, but that would put the cherrypicks on new branches of the source, which could cause problems with resyncing the source. I would recommend copying only the commit numbers.
In Terminal, run the command
Code:
. build/envsetup.sh
Run the repopick command, adding the commit numbers to the end. Here is an example
Code:
repopick 53075 53131 53302 53309 53356 53445 53528 53595 53603 53604 53637 53964 54197 54198 54219 53468 54251 54274 54277
If the commits do not all merge correctly, you will get what is called a merge conflict. This is because one or more of the commits does not play nice with the CyanogenMod code. Make sure you have the latest code by resyncing, and also make sure you have the latest cherrypicks. If the command still fails, wait a few hours because the document probably just hasn't been updated.
Once you get all of the commits merged correctly, it is time to build!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Building the Source
Before building, if you have extra space on your hard drive, you can optionally use CCache to speed up your build a bit. Enable this from inside the working directory by using
Code:
export USE_CCACHE=1 && prebuilt/darwin-x86/ccache/ccache -M 20G
You may also need to change the ulimit to support building. On OSX 10.9, I experienced errors stating that I had too many files open, and I had to change the ulimit amount. NOTE: If you have issues, you will need to do this every time you build! Change the ulimit amount by running
Code:
ulimit -Hn 8192
and
Code:
ulimit -Sn 8192
Make sure your working directory is clean by running
Code:
make clean
Next, initiate the build by running
Code:
brunch d2vzw
If all goes well you should have a flashable zip in the out/target/product/d2vzw/ folder. Enjoy!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Updating the Source
Later on, you may decide to build another file to see with new changes to the CyanogenMod code. Think of this as a ROM update. To do this, you will need to follow some steps. All of these steps have been completed already in this guide, so I will just be outlining them, and will not be listing everything. If you forget how to do something, consult the guide.
Repo sync
Apply cherrypicks
Enable CCache (Optional)
Set the ulimits
Clean your working directory using
Code:
make clean
Build the code using
Code:
brunch d2vzw
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Reserved

reserved

Recognized Developer - OP
OP hmmm OVER POWERED
Finally i can choose between sspencer10,tvall and cammykool and now you!
---------- Post added at 01:06 AM ---------- Previous post was at 12:41 AM ----------
Same Gapps? PA?

Is the 4.3 or the 4.4 camera included in this rom? If it is the 4.4 camera, is the quality of the photo better than the initial builds? Thank you.

-External SD Card May or May Not Work
It does work

markdapimp said:
-External SD Card May or May Not Work
It does work
Click to expand...
Click to collapse
The reason why he posted that is because one thing gets fixed another is broken. Every Device is different kinda thing.

XRaptor29 said:
The reason why he posted that is because one thing gets fixed another is broken. Every Device is different kinda thing.
Click to expand...
Click to collapse
I have 3 S3's my mom's dads and mines SD works perfectly on all 3

markdapimp said:
I have 3 S3's my mom's dads and mines SD works perfectly on all 3
Click to expand...
Click to collapse
Well thats a good thing lol :good:

Anyone know of a fix to get the apps from the Play Store that say sd card storage is insufficient to install? Root Explorer did it to me, but that's all I know of so far. Not a big deal, can use other apps. Thanks for the builds!

mds96 said:
Anyone know of a fix to get the apps from the Play Store that say sd card storage is insufficient to install? Root Explorer did it to me, but that's all I know of so far. Not a big deal, can use other apps. Thanks for the builds!
Click to expand...
Click to collapse
Do a clean wipe in CWM and flash the FULL PA Gapps
---------- Post added at 02:22 AM ---------- Previous post was at 02:12 AM ----------
Some screenshots for OP

mds96 said:
Anyone know of a fix to get the apps from the Play Store that say sd card storage is insufficient to install? Root Explorer did it to me, but that's all I know of so far. Not a big deal, can use other apps. Thanks for the builds!
Click to expand...
Click to collapse
seems to be a bug to only paid apps. free ones work for me. weird.

XRaptor29 said:
seems to be a bug to only paid apps. free ones work for me. weird.
Click to expand...
Click to collapse
I see what you mean

Thanks Markdapimp! I kinda figured a clean wipe would solve the problem, but guess I wanted to be lazy, lol

markdapimp said:
I see what you mean
Click to expand...
Click to collapse
Pretty sure this is because of the SD card problem. Hopefully there is a fix soon

Downloading!! Quick question before I flash..... I am running tvalls build from a few days ago, can I dirty flash or no? Also I love your builds it reminds me of when CM9 was built for the ReZound!! Props bro!
Sent from my SCH-I535 using Tapatalk 2

WeThePeople13 said:
Downloading!! Quick question before I flash..... I am running tvalls build from a few days ago, can I dirty flash or no? Also I love your builds it reminds me of when CM9 was built for the ReZound!! Props bro!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would just do a clean flash just to be sure

WeThePeople13 said:
Downloading!! Quick question before I flash..... I am running tvalls build from a few days ago, can I dirty flash or no? Also I love your builds it reminds me of when CM9 was built for the ReZound!! Props bro!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yes dirty flash should be fine, but idk for sure. I've got homework to do but when I get time I'll make a new build and upload/put more stuff in the OP. Maybe tonight but probably not.
Screenshots in screenshots tab thanks @markdapimp

Yea that is what i was thinking. I just am lazy lol and I really hate doing that whole process of getting art enabled.
Sent from my SCH-I535 using Tapatalk 2

[RECOVERY] TWRP 2.8.7.0 touch recovery for Mi4i

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Use it carefully, i didn't tested it very well... At least, installing my CM works
I'm not responsible if you transform your phone into a brick!
I've decided to compile own TWRP.
FEATURES
- Latest cm kernel (https://github.com/dh-harald/android_kernel_xiaomi_ferrari)
- upstream repository from (https://github.com/omnirom/android_bootable_recovery)
- native 64bit / QCOM_BSP / QCOM HW disk encryption
- f2fs enabled (to use it, you need 20150916 or later CM of mine -- if you're using different CM version, contact to your maintainer)
COMPILE GUIDE
Soon...
DOWNLOAD
twrp-2.8.7.0-ferrari.img - 30.15 MB
INSTALL
- Install fastboot drivers
- Download it to your computer
- Reboot your device into bootoader mode
- fastboot flash recovery twrp-2.8.7.0-ferrari.img
BUGS
You tell me...

HOW TO COMPILE
1. you need to use my minimal repo to create the build environment:
Code:
repo init -u git://github.com/dh-harald/twrp_android.git -b cm-12.1
2. add a xml file to local_manifests:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" />
<project path="device/xiaomi/ferrari" name="dh-harald/android_device_xiaomi_ferrari" />
<project path="kernel/xiaomi/ferrari" name="dh-harald/android_kernel_xiaomi_ferrari" />
</manifest>
3. sync the repository
Code:
repo sync
3. (optional - I don't know is it still need or not) You need to patch external/sepolicy
use this link, what do you need to change: http://review.cyanogenmod.org/#/c/89474/
4. compile it
Code:
$ . build/envsetup.sh
$ lunch cm_ferrari-userdebug
$ make -jX recoveryimage
X is based on your nr of CPUs
If you have a synced CM working tree, you can try to replace CWM to TWRP, and compile it, but last time it breaks my CM build... -> I use this method

What's different from current TWRP build in Mi Toolkit?

haikalizz said:
What's different from current TWRP build in Mi Toolkit?
Click to expand...
Click to collapse
I don't know... I've no spec for old recovery...
At least, it's supporting f2fs filesystem That's why I compile own version

Any compilation guide?

haikalizz said:
Any compilation guide?
Click to expand...
Click to collapse
Like I said: soon

TWRP 2.8.7.0 work :good:
I am on miui 7 5.8.28

@dh.harald when you say " fastboot boot flash fastboot flash recovery twrp-2.8.7.0-ferrari.img"
It really means " fastboot flash recovery twrp-2.8.7.0-ferrari.img"
correct?
just got confused with the initial "fastboot boot flash "

candiesdoodle said:
@dh.harald when you say " fastboot boot flash fastboot flash recovery twrp-2.8.7.0-ferrari.img"
It really means " fastboot flash recovery twrp-2.8.7.0-ferrari.img"
correct?
just got confused with the initial "fastboot boot flash "
Click to expand...
Click to collapse
Yes, you've right... Thanks!
I've fixed it

at last update to recovery

IIRC, we can just simply push the recovery to its corresponding partition/folder in /dev/block/ using Android's Terminal Emulator using dd, right? Does anyone have a detail of this phone's /dev/block? CMIIW

How can I enable f2fs filesystem?

jelennn said:
How can I enable f2fs filesystem?
Click to expand...
Click to collapse
Go to Wipe/Advanced Wipe
Select Data/Cache
Select "Repair or Change File System"
Select "Change File System"
Select "F2FS" (Swipe to change will format the filesystem.)
So, if you want to use /data as f2fs, you need to backup everything (sdcard/data)

Can I change to f2fs only this 2 partitions (cache & data)? What about the rest?

jelennn said:
Can I change to f2fs only this 2 partitions (cache & data)? What about the rest?
Click to expand...
Click to collapse
Yes, only 2 partitions... You've no advantage on /system

haahaaah said:
TWRP 2.8.7.0 work :good:
I am on miui 7 5.8.28
Click to expand...
Click to collapse
sir can you elaborate what you mean by working?
can i flash newer miui rom with this recovery?
that is 5.9.16?
what you have checked in 5.8.28??

milav said:
sir can you elaborate what you mean by working?
can i flash newer miui rom with this recovery?
that is 5.9.16?
what you have checked in 5.8.28??
Click to expand...
Click to collapse
Always use the stock recovery to flash ota... Custom recovery won't work, I've tried..

I dont flash ota i use full rom only and i can flash with custom recovery can this recovery flash full rom or take backup of miui rom?

Can i flash this with flashify?

Djojorahardjo said:
Can i flash this with flashify?
Click to expand...
Click to collapse
yes. works

[ROM][OMS7][Experimental]LineageOS 14.1 with extra open commits

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This thread is no longer supported or updated! You can maybe still find new builds on my AFH, but no guarantees! I will let the original first post only for information.
Important information:
I made this thread in order to avoid the off topic in the official LineageOS thread by @dianlujitao (http://forum.xda-developers.com/oneplus-3/development/rom-cyanogenmod-14-1-oneplus-3-t3496850).
The ROM that I propose is an experimental build using the official LineageOS 14.1 commits with some extra stuff that are not yet merged for testing. In order to avoid issues with repopicking, I use my own repos that are forked from the official repos. You can find them at the end of the post.
The commits that are included which are not merged are:
Kernel modification in order to pass SafetyNet CTS check
OMS / Substratum (fully included using n-mr1 tree)
160327 160328 (kernel) --> Postponed
160726 163935 (device)
161956 (OMS extra stuff)
161709 (hardware_cyanogen)
Please be aware that I might be missing some commits, the easiest way is for you to check the repo commits
All new builds will be in LineageOS_OOS4.0.3_OMS. I will keep including basic OMS functionality until issues arrive. At that time, I will remove and stop supporting OMS.
Please be aware that this is for advanced users!
I share all of my building information in order to help the users know what is included and how to reproduce. However, if you share your builds, please quote this thread in order to give the correct credits to the correct persons.
New builds (after 2017/1/15) uses F2FS backported from 4.10 kernel, you may meet compatibility problems such as deadlocks. If you do, flash the modified TWRP from @arter97 or from @dianlujitao and choose "Wipe -> Format Data" to format (not just wipe) your /data partition. This will clean the entire /data partition, including the emulated sdcard, so don't forget to backup your data!. After that, your data partition will be formatted into ext4, if you want to keep using f2fs, just convert fs type normally in TWRP.
It is highly recommended to use the modified TWRP from dianlujtao because the TWRP kernel is the same as the Android kernel, including 4.10 F2FS, which keeps 100% compatibility with LineageOS 14.1. There's no guarantee that other TWRP author will use the right kernel. Btw, NEVER choose the outdated OFFICIAL TWRP, it's out of maintenance!
The following will not be supported here:
Custom kernels
Mods
Xposed
I am not a dev, I only build the ROM. This can be read by the real dev, @dianlujitao. If you find a bug, please attach a logcat. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Known bugs:
F2FS ROMs can have deadlocks or other issues, please use the new TWRP
Some OMS themes apparently don't work, can be linked to missing root for masquerade or substratum app (use SuperSU, not in-built root, uninstall and install Substratum app again)
Built-in root removed by LineageOS, flashable addon exists (https://download.lineageos.org/extras), only needed once apparently
Wifi calling doesn't work after reboot or airplane mode --> Need to toggle the switch in Settings to make it work again
OOS Camera port doesn't work (no postprocessing, low quality photos) --> Use HAL 1 with flashable zip (https://forum.xda-developers.com/showpost.php?p=70983628&postcount=1879)
other stuff
Installation:
Download the zip
Install a compatible Recovery (Modified TWRP)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset unless you want to dirty flash
Flash LineageOS
Optional: Install the Google Apps addon package (if clean flash)
Reboot
Roomservice + Building process
Here is the roomservice.xml of this ROM:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_oneplus_oneplus3" path="device/oneplus/oneplus3" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_kernel_oneplus_msm8996" path="kernel/oneplus/msm8996" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_vendor_nxp-nfc_opensource_Nfc" path="vendor/nxp-nfc/opensource/Nfc" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_vendor_nxp-nfc_opensource_frameworks" path="vendor/nxp-nfc/opensource/frameworks" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_vendor_nxp-nfc_opensource_libnfc-nci" path="vendor/nxp-nfc/opensource/libnfc-nci" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="TeamSubstratum/masquerade" path="packages/apps/masquerade" remote="github" revision="n" />
</manifest>
Here is the rough building process (all the repo updating, repopick conflicts, etc... are not shown):
Use LineageOS roomservice
Cleaning output directory
Sync repo and prepare repopick commands
Repopick open commits from LineageOS
Clean build directory (sometimes necessary)
Generate changelog
Prepare build
Config jack server + start server
Build ROM
Copy zip file to host and cleanup
Kill jack server
Download:
https://www.androidfilehost.com/?a=show&w=files&flid=75317
Version Information
Status: Nightly
Created : 2016-12 -13
Latest build: 2017-03-05
Changelog
Code:
Project name: device/oneplus/oneplus3/
* df7c1db Revert "op3: remove highspeed recording profiles"
* 13e4b5d op3: disable wpa_supplicant log spam
Project name: hardware/qcom/audio-caf/msm8916/
* 1e33348 hal: dolby: Only set C_KEY if ACDB License is enabled.
Project name: vendor/cm/
* 3a03129 OMS: Add masquerade for Substratum OMS themes
Credits
CM team
LineageOS team
Substratum team
@dianlujitao
@ivanich
@siankatabg
@Sultanxda
@miscom
@flo071
@arter97
@piats
@nicesoni_ash
everyone else that helped me
Source Code:
https://github.com/LineageOS
https://github.com/Matssa56

Thanks loved yesterday's build downloading.

Thanks mate, downloading now!

chazey2 said:
Thanks loved yesterday's build downloading.
Click to expand...
Click to collapse
Giocarro said:
Thanks mate, downloading now!
Click to expand...
Click to collapse
Feel free to give me your feedback!

currently, I'm running CM13 on my OP3, want to update to CM14, but I can't find any issue log. What are the current knows issues? Thanks

Good work bud rom is awesome

titan1655 said:
currently, I'm running CM13 on my OP3, want to update to CM14, but I can't find any issue log. What are the current knows issues? Thanks
Click to expand...
Click to collapse
I didn't out any issue log since the build is experimental. For now, the issues are the same as the official nighties without the echo problem.
An issue that can be present concerns the volume, it goes up or down in some apps or when you change the audio of the notifications in some apps, but I didn't experience it yet.
Other than that, there was the dev option that was freezing, but it is apparently fixed, don't know if it was a oneplus3 issue or if it was multi device.
That is about it on my end, didn't take a chance to look at the logs yet. Pleas be aware that this is an experimental build, it has some fixes that are not yet merged in the official CM build, for example the echo and GPS fix.

@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?

Gave this a go, but for me after flashing there were some strange things with the home key not responding that i hadn't had in previous builds. For me the 13th nightly seemed a bit more ineffective than previous so I'm back on the official 12th for now, but will keep an eye on this thread with interest. Thanks for contributing!

ivanich said:
@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?
Click to expand...
Click to collapse
A tad curious about you mentioning NFC, I noticed there are some issues with NFC on Nougat builds in general and Android Pay, is that something that may have been fixed with the merged caf code?

ivanich said:
@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?
Click to expand...
Click to collapse
Haha it has been fixed in my build it was already ok before it seems, I saw that @dianlujitao didn't ship something that was needed.
MisterCoolBeans said:
A tad curious about you mentioning NFC, I noticed there are some issues with NFC on Nougat builds in general and Android Pay, is that something that may have been fixed with the merged caf code?
Click to expand...
Click to collapse
The issue was heating and crashing of the NfC with the N blobs, but it has been fixed by merging the new version. I didn't test Android Pay because I don't have it in my country.

matssa said:
Haha it has been fixed in my build it was already ok before it seems, I saw that @dianlujitao didn't ship something that was needed.
The issue was heating and crashing of the NfC with the N blobs, but it has been fixed by merging the new version. I didn't test Android Pay because I don't have it in my country.
Click to expand...
Click to collapse
I'm willing to give it a test! :good: I'll download your build and try it.

ivanich said:
@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?
Click to expand...
Click to collapse
Just checked the repo to be sure before changing thanks for the heads up!

I'm facing some little issue that become showstopper as they break my daily usage:
1) HOME button long-press to turn OFF the display is not working consistently; most times I have to press it twice to trigger the action;
2) BACK button long-press is not customizable?!? I want it to trigger MENU action, but the option is not present;
3) there's no way to disable capacitive keys while gaming; not a deal breaker for most people I know, but my son yesterday went as far as crying because of false touches on capacitive keys during his brief gaming time.
Well, I guess I'm writing this to show appreciation for Matssa work and to ask whether you guys see any solution to these little but important glitches.

Sounds exactly the same issues I was facing meaning I can't use as a driver for the moment

New nightly on AFH, first post was updated.
Giocarro said:
I'm facing some little issue that become showstopper as they break my daily usage:
1) HOME button long-press to turn OFF the display is not working consistently; most times I have to press it twice to trigger the action;
2) BACK button long-press is not customizable?!? I want it to trigger MENU action, but the option is not present;
3) there's no way to disable capacitive keys while gaming; not a deal breaker for most people I know, but my son yesterday went as far as crying because of false touches on capacitive keys during his brief gaming time.
Well, I guess I'm writing this to show appreciation for Matssa work and to ask whether you guys see any solution to these little but important glitches.
Click to expand...
Click to collapse
Mmmh got any logs?
For the Home button, I have the same issue, I find some fpc hall errors. @dianlujitao, you can find a log here. Best bet is that we need to wait for the updated hall and blobs from the official OOS N ROM.
For the Back button, apparently it isn't customizable yet, I suppose it is the same issue in the official nightly. If you want to trigger the menu, you can use the recent apps button.
For the disable capacitive keys, this option was never in CM before, I don't think it will appear one day. Did you try with the on-screen navigation bar? I think this disables the capa buttons and they should dissapear while gaming (not sure about that last point). It may be possible to do something like that, but I think in an Xposed module, which is still not possible for Android N :/

bay91 said:
Sounds exactly the same issues I was facing meaning I can't use as a driver for the moment
Click to expand...
Click to collapse
What issues do you have? Do you have the same issues with the official nightly without the extra blobs? If so, can you please give us some logs?

matssa said:
Haha it has been fixed in my build it was already ok before it seems, I saw that @dianlujitao didn't ship something that was needed.
Click to expand...
Click to collapse
If "Developer settings" works in your build then you using old blobs.

ivanich said:
If "Developer settings" works in your build then you using old blobs.
Click to expand...
Click to collapse
How can it be possible??? Why, WHYYYY??? WHYYYYYYYYYY?? Where do you think I may have gone wrong? In the building process? I know the commits have been taking into account since the GPS is working, it wasn't on the CM official.
EDIT///
Furthermore, when checking github, a "hax" was found by Scott Hart by removing the OEM unlock and another stuff, and it was made in android_packages_apps_Settings, which isn't touched by the commit from @dianlujitao, correct? So if my guess is correct, we should have the same issue on CM official and unofficial, even with the new blobs, what I saw from the post is that @dianlujitao didn't ship lksecapp in his build: "Nice catch, maybe OEM unlock, as I didn't ship lksecapp in my experimental build".
If you use your own experimental build, do you have the same issue?

matssa said:
How can it be possible??? Why, WHYYYY??? WHYYYYYYYYYY?? Where do you think I may have gone wrong? In the building process? I know the commits have been taking into account since the GPS is working, it wasn't on the CM official.
Click to expand...
Click to collapse
cd to your BUILD_DIR/vendor/oneplus
and show output of
Code:
git status
and
Code:
git log -n 3
Official builds doesn't have this issue because using old blobs.
I have issue with Dev options only with new blobs.

[ROM] [H830/H850/RS988] [UNOFFICIAL] Resurrection Remix 7.0.2 - Pie

ALL credit for this ROM goes to @x86cpu, the driving force behind LineageOS development for our G5. Leave him a thanks at his LineageOS 16.0 thread!
btw if anyone's wondering about the name, I changed it to Jolt151
What's working:
Same as Lineage
What's not working:
Same as Lineage
Installation
Do a full wipe (system/cache/data) if coming from any other ROM, including if you are upgrading from my RR Oreo roms.
Flash arm64 9.0 GApps and Magisk after if you want.
NOTE:
LineageOS 16.0 seems to have an issue with the camera not working when making a clean flash, and from user reports you need to flash 15.1 and then dirty flash 16.0 to get the camera working. From my initial testing, the stock camera works out of the box, but I haven't been able to get any version of Gcam working yet.
Downloads
July 4th:
h830: https://mega.nz/#!GqQFRCbb!zXac-cIImcZf1VkJJwsZQq7fnt9VB6uEars5YPXndP4
md5: 68b7a4ccda2af1d0418a8295813d117d
h850: https://mega.nz/#!vrQlSQSb!NwKIioG5exSr2WfE6uDDrqA2wQd6pxyKHoM2hHhz3Rw
md5: 3352d3732cb2d66d0e44709a44760bac
rs988: https://mega.nz/#!XiZHnYAJ!Rq6p1-fSVDW1jw96h-3tim1h8KobGypaKqSp4JvGzFQ
md5: 9d691c71bf8cf7bafea099fb8c978790
Trees:
Code:
<manifest>
<project name="x86cpu/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="lineage-16.0"/>
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_device_lge_h830" path="device/lge/h830" remote="github" revision="lineage-16.0"/>
<project name="LineageOS/android_kernel_lge_msm8996" path="kernel/lge/msm8996" remote="github" revision="lineage-16.0"/>
<project name="LineageOS/android_device_lge_msm8996-common" path="device/lge/msm8996-common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_lge_g5-common" path="device/lge/g5-common" remote="github" revision="lineage-16.0"/>
<project name="LineageOS/android_device_lge_common" path="device/lge/common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_device_lge_h850" path="device/lge/h850" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0"/>
</manifest>
+ latest repopicks by @x86cpu

Don't forget two inportant ones in: https://github.com/x86cpu/proprietary_vendor_lge/commits/lineage-16.0
acad5539c84cba1a533efce97431ad4774b6f6c9
5f93381476dc1282db8ff32dc605cd0ff413f9dd

x86cpu said:
Don't forget two inportant ones in: https://github.com/x86cpu/proprietary_vendor_lge/commits/lineage-16.0
acad5539c84cba1a533efce97431ad4774b6f6c9
5f93381476dc1282db8ff32dc605cd0ff413f9dd
Click to expand...
Click to collapse
Thanks! I actually used your repo, but I forgot to update that in the manifest I posted

Thanks @Jolt420 and @x86cpu for all your hard work and your time hoping you continue supporting our G5

Thank you for support. Will try once have time.

Awesome rom, thank you for developing for g5

Awesome!

It's very stable and smooth, thanks for the Job well done.

Tsaviouranzo said:
It's very stable and smooth, thanks for the Job well done.
Click to expand...
Click to collapse
How is your camera?

Jolt151 said:
How is your camera?[/QUO
Have no issues so far. Camera works just fine. Thanks
Click to expand...
Click to collapse

Jolt151 said:
Thanks! I actually used your repo, but I forgot to update that in the manifest I posted
Click to expand...
Click to collapse
July 4th version is not included this two repo fix right?

Arda Süzen said:
July 4th version is not included this two repo fix right?
Click to expand...
Click to collapse
If you're referring to those two that x86cpu mentioned, then those are included

Hi, i had Fullmics 5.5 on my H850 and now i installed RR7.0.2 just after wiping system/data/cache. I had to delete the asserts in this rom to avoid the error 7.
The Installation worked.
Flashlight and Camera does not work. Also cstark27_GCam_5.1.018_24_v4.2t3 closes directly. Or do i have to try a different version?
How can i check, which bootloader is installed and how can i update just the bootloader? I think i'm still on the old one (i think 7.1.2 Nougat)
P.S. is it necessarry to install to-x86cpu.zip before installing the RR Rom? What is this good for?

Ha, cool. Installed Linage 15.1. first and did the dirtyflash trick to RR 7.0.2.
Flashlight and Linage Camera works
Thanx a lot guys for this up to date firmware

loretta1980 said:
Ha, cool. Installed Linage 15.1. first and did the dirtyflash trick to RR 7.0.2.
Flashlight and Linage Camera works
Thanx a lot guys for this up to date firmware
Click to expand...
Click to collapse
Hmm, so we have the same problem, but at least we have the same solution of dirty flashing lineage 15.1. Thanks for trying that out!
As for error 7, that happens on older versions of twrp that don't have the right device version codes. You could upgrade your twrp to fix that.
Also, you should be on Nougat bootloader, which is only an issue right now for anyone who upgraded to stock Oreo at one point.

I did a clean flash of this rom in an h830, everything worked very well but after using it for a while it got too hot to the point that I felt it burned my fingers and the microphone in games did not work, nobody listened to me when I spoke, besides that the multimedia sound was a bit low, from there excellent rom thank you for your great work!

60FPS?
Tsaviouranzo said:
Jolt151 said:
How is your camera?[/QUO
Have no issues so far. Camera works just fine. Thanks
Click to expand...
Click to collapse
Do we have 60FPS recording possibility maybe? :S
Click to expand...
Click to collapse

Root + SafetyNet error ; and no photo
Hello everyone ...
I have a problem with ROOT and SafetyNet on LG G5:
mobile already unlocked under ADB / Fastboot, validated developer mode, validated Android debugging,
previously rooted nickel with a dual boot with Remix and Lineage.
Wanting to install an Android version PIE 9, I made a full backup with Titanium Backup,
then a Factory Reset, and flashed the latest TWRP 3.3.1-0
I installed the Rom H-ROM_G7_PORT found on XDA, Rooted with Magisk v19.3,
flashed 'no-verity-opt-encrypt-6.0', installed MagiskManager-v7.3.2.apk
installed open_gapps-arm64-9.0-aroma-20190706.zip,
installed Root Checker (no SuperSu installation), validated Android debugging
Bluetooth, wifi, Google account, sound: everything is OK; No screen lock chosen.
From the beginning in Rooted mode, the camera did not work, the photo icon disappeared,
no automatic rotation of the screen, no adaptability of brightness.
The Root does not work anymore, despite several flash; SafetyNet is bad ...
All the tests with parametrization of Magisk did not give anything:
Super-user, Hide, Core, Busybox and SystemLess Hosts validated, Cache cleared, Host without system.
I noticed that I have a Trust application with Root disabled (not editable), no encryption, Selinux applied, ...
I hope someone will have an answer to my concerns ... thank you in advance for your answers.

kilm13 said:
Hello everyone ...
I have a problem with ROOT and SafetyNet on LG G5:
mobile already unlocked under ADB / Fastboot, validated developer mode, validated Android debugging,
previously rooted nickel with a dual boot with Remix and Lineage.
Wanting to install an Android version PIE 9, I made a full backup with Titanium Backup,
then a Factory Reset, and flashed the latest TWRP 3.3.1-0
I installed the Rom H-ROM_G7_PORT found on XDA, Rooted with Magisk v19.3,
flashed 'no-verity-opt-encrypt-6.0', installed MagiskManager-v7.3.2.apk
installed open_gapps-arm64-9.0-aroma-20190706.zip,
installed Root Checker (no SuperSu installation), validated Android debugging
Bluetooth, wifi, Google account, sound: everything is OK; No screen lock chosen.
From the beginning in Rooted mode, the camera did not work, the photo icon disappeared,
no automatic rotation of the screen, no adaptability of brightness.
The Root does not work anymore, despite several flash; SafetyNet is bad ...
All the tests with parametrization of Magisk did not give anything:
Super-user, Hide, Core, Busybox and SystemLess Hosts validated, Cache cleared, Host without system.
I noticed that I have a Trust application with Root disabled (not editable), no encryption, Selinux applied, ...
I hope someone will have an answer to my concerns ... thank you in advance for your answers.
Click to expand...
Click to collapse
Your problem is with H-ROM or RR?

Yesterday wit RR 7.02
Today, after factory reset, and flash with Lineage 16, Pie 9,
same problem of bad SafetyNet.
All the tests with parametrization of Magisk did not give anything :
Super-user, Hide, Core, Busybox and SystemLess Hosts validated, Cache cleared, Host without system.
Root OK, photo OK (only 1 of 2) ...
All seem ok now, except SafetyNet
regards..

[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s

DESCRIPTION
Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download.
FEATURE
The following items may not be available for all versions, please use the latest build!
Click to expand...
Click to collapse
Build with user variant instead of userdebug (to reduce image size and improve performance).
CPU/GPU is overclocked with optimized voltage/bus-cci and 300 Hz/Jiffies kernel clock frequency. [16.0 +]
EAS (sched cpufreq governor from linux-3.18) CPU scheduler implemented. [16.0 +]
Full-weight NotoSansCJK fonts included (to display East Asian characters with more font weights).
High screen refresh-rate (75 Hz) support for Mi-4c with "Sharp-rsp61322 LCD" screen. [16.0 +]
Implement ZRAM with ZSTD crypto algorithm (KSM is used after 20210116) to improve I/O performance on devices with 2GB RAM. [16.0 +]
Linux kernel is built by clang-12 toolchains, with Polly + LTO + -Ofast optimization to get better performance. [17.1 +]
Pre-dex2oat with everything filter globally (sacrificing space and first-install time to improve efficiency).
Remove or disable unnecessary kernel configs and modules, also includes some other optimizations. [16.0 +]
Remove unnecessary apps/binaries/libraries/services from system. [16.0 +]
Signature spoofing support (ready for MicroG, including Chinese translations).
User-friendly controller for special features in Settings app (like CPU overclock, Edge gesture and Screen refresh rate). [17.1 +]
...
STATUS
Go to GitHub Issues for more details and give me feedback.
Click to expand...
Click to collapse
Working
Basic hardware
Baseband/SMS
Bluetooth
Camera/Flashlight
IR remote
Speaker/Microphone
Wi-Fi
Extras
Camera API2 (with patch) [17.1 +]
Edge gesture (in Settings > System > Buttons) [16.0 +]
Overclock control (in Settings > Battery > Battery saver and performance) [17.1 +]
Screen refresh rate (in Settings > Display) [17.1 +]
Not working
SELinux permissive [16.0 +]
VOLTE (won't fix because of no compatible IMS stacks) [16.0 +]
DOWNLOAD
GitHub Releases: https://github.com/BYZYB/android_device_xiaomi_libra/releases
Kernel/ROM: https://www.androidfilehost.com/?w=files&flid=287533
TWRP: https://www.androidfilehost.com/?fid=8889791610682882451
SOURCE
Device: BYZYB/android_device_xiaomi_libra
Forked from (16.0 +): android_device_xiaomi_libra + android_device_xiaomi_msm8994-common
Kernel: BYZYB/android_kernel_xiaomi_libra
Forked from: android_kernel_xiaomi_leo
Vendor: BYZYB/android_vendor_xiaomi_libra
Forked from (16.0 +): android_vendor_xiaomi_libra + android_vendor_xiaomi_msm8994-common
Custom changes: repo_17.diff + repo_18.diff
Thanks to all developers and users (Gah0 | Mortezadadgar | Xiaomi classic dev | ...) who contributed to Mi-4c/Mi-4s (including other devices shipped with MSM8992/8994 SOC) or gave me help!
Click to expand...
Click to collapse

TIPS
Here are some tips which may improve your experience or resolve some problems.
Basic quality assurance: I only have one smart phone (3+32GB Mi-4c ×1), so the ROMs here should at least satisfy my daily usage.
This project will be kept maintained even after I bought my new mobile phone (8+128GB Mi-Mix-2 ×1) in 2021. My Mi-4c is one of the most meaningful items of my own, it's not easy to leave it behind in the drawer and say goodbye. The new battery and rear cover (thanks to yipinghuang1991) will refresh this old device and make it usable again.
Even though the signal icon in status bar shows "No signal" at the first minute after boot, the device is still able to receive SMS and phone calls (so the device does have signal, but the system doesn't admit it at all).
If the free space in /system is not enough to install GAPPs, try to delete /system/fonts/NotoSansCJK.ttc to get about 100MB free space (If Chinese/Japanese/Korean is not your main language). Removing the prebuilt Webview packages (about 120MB) after installed another one is also a solution.
If you found random reboot on your device with overclock enabled (or just updated to lineage-17.1-20201216 and left overclock option unchanged), please disable this feature to see if this issue is resolved. Go to Settings > System > Battery > Battery saver and performance, enable then disable "High performance mode", and reboot your device. If you are using lineage-17.1-20210209 or newer, it's no need to do such steps after a clean install (as both persist.sys.cpu_overclock and persist.vendor.edge_touch_mode are default to false by default).
It's highly recommended to disable system logs to reduce resource consumption (for better performance and privacy), unless you're going to collect system logs. Go to Settings > System > Developer options, and set the value of "Logger buffer sizes" to off.
It's not recommended to use SELinux enforcing mode even if it's supported in some builds. Also, please consider the negative effect of I/O performance before enabling disk encryption, unless you really want to.
BUILD
As all source codes and custom changes in my LineageOS ROMs are open-source, you are permitted to build your own ROM or kernel (not only for LineageOS) with my sources for non-commercial purpose.
There are many documents about how to build custom Android ROMs in Linux/OSX, so I will not post these basic steps here to reduce redundancy. However, there are still some important things which may not be included in other documents. Here are some basic steps about what you should do (using lineage-18.1 as example), you can also take a reference to other tutorials.
Install necessary packages
There are a number of "necessary" packages listed in most tutorials, but not all of them are needed. Here are the packages you need to install manually on Ubuntu or Debian.
sudo apt install bc bison git gnupg make repo rsync unzip zip
Sync Android sources
You need to download and update your local repo with upstream sources regularly, in order to get new changes as soon as possible (just like other open-source projects).
Init repo to current directory: repo init -u https://github.com/LineageOS/android.git -b lineage-18.1 --depth=1
Sync all repos and prune unused branches: repo sync --prune
If nothing wrong happened, the LineageOS sources have been downloaded to your computer (about 100GB). Here are some commands which might be useful in the future.
Show all local changes of your repos: repo status or repo diff
Perform any operations to all repos: repo forall -c "xxx"
Setup local manifest
To sync your Android sources with upstream repos easily, it's recommended to create a local manifest in ./repo/local_manifests/. The local manifest should be a XML file like the following one, any filename is accepted (file: libra.xml).
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="BYZYB/android_device_xiaomi_libra" path="device/xiaomi/libra" remote="github" revision="lineage-18.1" />
<project name="BYZYB/android_kernel_xiaomi_libra" path="kernel/xiaomi/libra" remote="github" revision="master" />
<project name="BYZYB/android_vendor_xiaomi_libra" path="vendor/xiaomi/libra" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_xiaomi" path="hardware/xiaomi" remote="github" revision="lineage-18.1" />
</manifest>
Resolve build errors
Due to some hacks in my device configurations which are conflict with Android build rules, there might be some build errors if using all my repos directly. To resolve this issue, you need to modify project build/make/manually on your disk. After that, you should be able to prepare the necessary environment for Android build without errors.
Setup build namespace only: . build/envsetup.sh
Prepare build environment for Mi-4c with a specified build variant (xxx = eng/userdebug/user): . build/envsetup.sh && lunch lineage_libra-xxx
If you want to build the ROM in "user" build variant instead of the default "userdebug", more changes are needed to avoid build errors or potential bootloop. The following commands are some ways to build a full ROM.
Build full ROM in "user" variant: brunch lineage_libra-user
Build full ROM in "userdebug" variant: brunch lineage_libra-userdebug
Build full ROM with a specified number of threads (x ≤ physical CPU cores): lunch lineage_libra-xxx && make -jx
If you have lunch before, here is the simplest way: m
As git patch files are similar to git diff, you can always do these changes manually without using git am xxx.patch && git reset HEAD^ or other shell commands.
Kernel build toolchains
The kernel supports to be built with gcc-9+ or clang-10+. As Link-Time-Optimization (LTO) for Clang is enabled by default (config: CONFIG_LTO_CLANG), building the kernel with GCC directly will result in build errors. In conclusion, it's recommended to choose Clang as your toolchains for both faster build speed and better performance.
As VDSO compat is enabled (config: CONFIG_COMPAT_VDSO), both arm and arm64 toolchains are needed to build the kernel. Clang could handle different cross compile targets easily (thanks to LLVM), but GCC could not. Also, though the kernel sources are compiled by clang, they will be linked by LD (included in GCC toolchains -> Binutils) with LLVM plugins. In conclusion, if the ROM you are building provides legacy gcc-4.9 toolchains (like LineageOS based projects), it should be safe to go ahead without installing GCC toolchains or Binutils. Otherwise, you need to install both Binutils and Clang packages in your computer to avoid build problems.
If you are using Ubuntu or Debian on your computer, please install the following packages (choose one way).
Using prebuilt toolchains in Android repo (recommend): sudo apt install libc6-dev libgcc-12-dev
Using toolchaings in your distribution: sudo apt install clang llvm-dev
For ROMs without legacy gcc-4.9 toolchains: sudo apt install binutils-aarch64-linux-gnu binutils-arm-linux-gnueabihf
Then you should be able to build the kernel without modifying build configs.
Build kernel image only: make bootimage
Build recovery image only: make recoveryimage
Apply custom changes (optional)

This is great. Is signature spoofing enabled? If not, could it be? MicroG users would like it. Ty.
Edit: signature spoofing is enabled, but It seems LineageOS 17 locked my bootloader.
Edit2: LineageOS 17 do not support custom partition tables. After flashing, my 2.3gb "system" goes to 1.8gb and there's no space left for NanoDroid and other mods.

Flashed ok, seems to be working just fine, but can't install gapps due to "insufficient space"
Any advice?

rostopira said:
Flashed ok, seems to be working just fine, but can't install gapps due to "insufficient space"
Any advice?
Click to expand...
Click to collapse
Right, there is really no enough free space in "/system" to install GAPPs (even the "pico" version). If Chinese/Japanese/Korean is not your main language, try to delete "/system/fonts/NotoSansCJK.ttc" to save 117MB free space, which seems enough for the "nano" version.

WJXXBSH said:
Right, there is really no enough free space in "/system" to install GAPPs (even the "pico" version). If Chinese/Japanese/Korean is not your main language, try to delete "/system/fonts/NotoSansCJK.ttc" to save 117MB free space, which seems enough for the "nano" version.
Click to expand...
Click to collapse
Thanks for advice, I've removed it, but still not enough space even for pico package
Code:
/system/system # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 888.2M 176.0K 888.0M 0% /dev
tmpfs 888.2M 24.0K 888.1M 0% /tmp
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /data
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /sdcard
/dev/block/mmcblk0p42
372.0M 440.0K 363.9M 0% /cache
/dev/block/mmcblk0p41
1.8G 1.7G 178.0M 90% /system
UPD: Removed some other noto fonts, symlinked to roboto, deleted ringtones. Got 202M free
I really hope, that won't result in a bootloop
UPD2: It booted, immediately restarted, and booted again successfully
Feels good)

rostopira said:
Thanks for advice, I've removed it, but still not enough space even for pico package
Code:
/system/system # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 888.2M 176.0K 888.0M 0% /dev
tmpfs 888.2M 24.0K 888.1M 0% /tmp
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /data
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /sdcard
/dev/block/mmcblk0p42
372.0M 440.0K 363.9M 0% /cache
/dev/block/mmcblk0p41
1.8G 1.7G 178.0M 90% /system
UPD: Removed some other noto fonts, symlinked to roboto, deleted ringtones. Got 202M free
I really hope, that won't result in a bootloop
UPD2: It booted, immediately restarted, and booted again successfully
Feels good)
Click to expand...
Click to collapse
It seems you're using lineage-17.0 roms, which needs more free space than 16.0 (eg. the APEX image).
Deleting the fonts that you never used is surely a way to get more space. If you have installed "Android System Webview" (com.google.android.webview) from play store or other origins, removing the prebuilt one from "/system/product/app/webview" should be another possible solution (get another 100MB). However, make sure to choose the new webview package in "Developer settings" and prevent factory reset unless flashing the rom again, or it might result in problems.

Hello, everyone.
I use TWRP 3.1.1.0 and get error 7
When I try Flash latest official TWRP / or twrp 3.3.0 from here via fastboot I can't boot to recovery.
Which version of TWRP do I need to use to flash Lineageos 17?
Thanks

elna.nitz said:
Hello, everyone.
I use TWRP 3.1.1.0 and get error 7
When I try Flash latest official TWRP / or twrp 3.3.0 from here via fastboot I can't boot to recovery.
Which version of TWRP do I need to use to flash Lineageos 17?
Thanks
Click to expand...
Click to collapse
Try this recovery: https://androidfilehost.com/?fid=1395089523397945946
It's just the one I used on my device.

WJXXBSH said:
Try this recovery: https://androidfilehost.com/?fid=1395089523397945946
It's just the one I used on my device.
Click to expand...
Click to collapse
Yes, I already tried that after installing TWRP from your posted link I'm stuck on icon Xiaomi and the device doesn't get into recovery. It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data.
Only when I flash TWRP 3.1.1.0 from here (twrp from lollipop - nougat bootloader) I manage to get into the Recovery, the problem then I get eror 7 when I try to flash Lineageos 17.
It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data. So now I am without an operating system, only recovery.

elna.nitz said:
Yes, I already tried that after installing TWRP from your posted link I'm stuck on icon Xiaomi and the device doesn't get into recovery. It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data.
Only when I flash TWRP 3.1.1.0 from here I manage to get into the Recovery, the problem then I get eror 7 when I try to flash Lineageos 17.
It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data. So now I am without an operating system, only recovery.
Click to expand...
Click to collapse
It seems you are using the old bootloader of Android 5.x, but it doesn't support new ROMs after all. To upgrade to the new bootloader, you must have access to officially unlock your device, then flash the latest MIUI and boot one time (it will make sure you could unlock your bootloader).
Use the unlock tool here (official solution): https://www.miui.com/unlock/index.html
If you have other ways to unlock the new bootloader without the official method, it's also right. It may take you some time to get the official permission (from Xiaomi) to unlock the device, good luck!

WJXXBSH said:
It seems you are using the old bootloader of Android 5.x, but it doesn't support new ROMs after all. To upgrade to the new bootloader, you must have access to officially unlock your device, then flash the latest MIUI and boot one time (it will make sure you could unlock your bootloader).
Use the unlock tool here (official solution): https://www.miui.com/unlock/index.html
If you have other ways to unlock the new bootloader without the official method, it's also right. It may take you some time to get the official permission (from Xiaomi) to unlock the device, good luck!
Click to expand...
Click to collapse
Thanks a lot, how do I flash latest MIUI? From TWRP?
Where do I download the latest MIUI file?

elna.nitz said:
Thanks a lot, how do I flash latest MIUI? From TWRP?
Where do I download the latest MIUI file?
Click to expand...
Click to collapse
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".

WJXXBSH said:
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".
Click to expand...
Click to collapse
I can get permission to open the device only after connecting to my MI account through the device when installed on it official miui.
Therefore I seem to have previously had flash latest MIUI then log in to MI account and submit a request to open bootloader. Am I right?

elna.nitz said:
I can get permission to open the device only after connecting to my MI account through the device when installed on it official miui.
Therefore I seem to have previously had flash latest MIUI then log in to MI account and submit a request to open bootloader. Am I right?
Click to expand...
Click to collapse
Yes, if you want to unlock your device. A Mi account is needed to do this, on the latest MIUI version (if stable version "10.1.1.0" doesn't work, the develop version of MIUI is needed).

WJXXBSH said:
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".
Click to expand...
Click to collapse
Ok
I flashed latest firmware and TWRP 3.3.0, then Unlock bootloader with Mi Unlock.
Then flashed Lineageos 17 successfully.
The problem is that when I try to flash Gapps pico I get eror 70...
I tried to search for the font folder in the system path in TWRP File explorer and I couldn't find it (System Folder is empty) .
I tried reboot to system anyway, and after a long boot with the logo of the Lineageos 17, device initializing itself back to Recovery.
What else can we do?

elna.nitz said:
Ok
I flashed latest firmware and TWRP 3.3.0, then Unlock bootloader with Mi Unlock.
Then flashed Lineageos 17 successfully.
The problem is that when I try to flash Gapps pico I get eror 70...
I tried to search for the font folder in the system path in TWRP File explorer and I couldn't find it (System Folder is empty) .
I tried reboot to system anyway, and after a long boot with the logo of the Lineageos 17, device initializing itself back to Recovery.
What else can we do?
Click to expand...
Click to collapse
The latest version of lineage-17.0 could boot properly (tested my self). However, you flash the GAPPs and got interrupted halfway, which may cause some strange issues.
To fix this, format "/system" and flash the rom again. After that, mount "/system" manully in TWRP, then you could modify "/system" with the TWRP file manager.
There is another way to solve the GAPPs problem: If you're using magisk, try some modules that could install GAPPs without modifying "/system" (eg. "Weeb GAPPs"). Android 10 takes more free space in "/system" than Android 9 at present, even if without the fonts, it still has possibility that makes the GAPPs installation failed (this way works in lineage-16.0, which has 2.5× free space than 17.0).

WJXXBSH said:
The latest version of lineage-17.0 could boot properly (tested my self). However, you flash the GAPPs and got interrupted halfway, which may cause some strange issues.
To fix this, format "/system" and flash the rom again. After that, mount "/system" manully in TWRP, then you could modify "/system" with the TWRP file manager.
There is another way to solve the GAPPs problem: If you're using magisk, try some modules that could install GAPPs without modifying "/system" (eg. "Weeb GAPPs"). Android 10 takes more free space in "/system" than Android 9 at present, even if without the fonts, it still has possibility that makes the GAPPs installation failed (this way works in lineage-16.0, which has 2.5× free space than 17.0).
Click to expand...
Click to collapse
Ok, I deleted the Notosansjfk.ttc from fonts & android viwe system app, And now I am able to flash Gaaps pico and boot to system.
But when I run the system and try to get to the System User Interface Launcher course, you can't use your device. Probably happened because I deleted the font or the Android view system..
Any solutions?

elna.nitz said:
Ok, I deleted the Notosansjfk.ttc from fonts & android viwe system app, And now I am able to flash Gaaps pico and boot to system.
But when I run the system and try to get to the System User Interface Launcher course, you can't use your device. Probably happened because I deleted the font or the Android view system..
Any solutions?
Click to expand...
Click to collapse
You deleted the "Android System Webview" without installing a new one? That's not a good news after all, because every APP that contains webview will crash. The CJK font will not cause any serious problems, just make some words a "◻".
As a solution, if you could use Play Store, just install "Android System Webview" from there. Otherwise, you could still install one through ADB.
Download the webview app here (if Play Store not working): https://www.apkmirror.com/apk/googl...em-webview-78-0-3904-108-android-apk-download

WJXXBSH said:
You deleted the "Android System Webview" without installing a new one? That's not a good news after all, because every APP that contains webview will crash. The CJK font will not cause any serious problems, just make some words a "".
As a solution, if you could use Play Store, just install "Android System Webview" from there. Otherwise, you could still install one through ADB.
Download the webview app here (if Play Store not working): https://www.apkmirror.com/apk/googl...em-webview-78-0-3904-108-android-apk-download
Click to expand...
Click to collapse
Finally I installed Weeb Gapps magisk Moudle, and The majority are fine.
There are 2 problems:
1. The device feels very lag in the opening of the apps and in the transition between them.
2. After restart takes the device nearly 2 minutes to find a cellular network

Database Info

welcome