Database Info

[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

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

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

[ROM][ef63][7.1.x][UNOFFICIAL] Lineage Android Distribution for VEGA IRON 2

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
KNOWN ISSUES
- Report with logs
!!! BUG REPORTS WITHOUT LOGS WILL BE IGNORED !!!
Android: adb logcat
Radio: adb logcat -b radio
Kernel: adb shell dmesg
Full Bugreport: Developer Menu -> Bugreport
HOW TO INSTALL LINEAGEOS
- Make sure your phone is running Marshmallow bootloader
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Install TWRP recovery
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- IMPORTANT: Do a Factory Reset. (Wipe data & cache)
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
DOWNLOADS
Download from AFH:
https://www.androidfilehost.com/?w=files&flid=169302
OR
Download from Github :
https://github.com/chautruongthinh/android_device_pantech_ef63/releases
Google Apps:
OpenGApps (recommended: arm, 7.1.1, nano)
SOURCECODE
Device tree: https://github.com/chautruongthinh/android_device_pantech_ef63
Msm8974_common: https://github.com/chautruongthinh/android_device_pantech_msm8974-common
Vendor for ef63: https://github.com/chautruongthinh/android_vendor_pantech
Kernel: https://github.com/chautruongthinh/android_kernel_pantech_msm8x74
HOW TO BUILD
- repo init -u git://github.com/LineageOS/android.git -b cm-14.1
- add local manifest to .repo/local_manifests/
- repo sync -j4
- . build/envsetup.sh
- brunch ef63
Local manifest:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="chautruongthinh/android_kernel_pantech_msm8x74" path="kernel/pantech/msm8x74" remote="github" revision="cm-14.1" />
<project name="chautruongthinh/android_device_pantech_msm8974-common" path="device/pantech/msm8974-common" revision="cm-14.1" />
<project name="chautruongthinh/android_device_pantech_ef63" path="device/pantech/ef63" remote="github" revision="cm-14.1" />
<project name="chautruongthinh/android_vendor_pantech" path="vendor/pantech" remote="github" revision="cm-14.1" />
</manifest>
Credits:
CyanogenMod and its contributors
CAF (aka Qualcomm)
Open GApps
The people who first brought CM14.1 to the VEGA IRON 2:
@chautruongthinh
@hoalamha
*Credits & thanks some people to help me such as:
- @futranbg (TekCafe Team)
- @HeavenAngel (TekCafe Team)
- @diszell2008 (TekCafe Team)
- @bangprovn
@LinhPhi
Sunghun
@mifl (M. Ignacio Fernández López)
And all those individual/teams who I might have missed.
SUPPORT ME
Do you like my work? Consider donating me some beer!
​
Contributors
chautruongthinh
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2017-03-25
Last Updated 2017-04-13

Sceenshot:

For me 2

Touch screen issue with this rom
I flashed this rom to my IM-910S and I had no major issues.
There is one flaw in this rom, glove touch mode is always enabled, and I couldn't disable it. Touch screen recognizes my finger even when I didn't touch the screen, which makes me frustrated. Please give us option to disable glove touch mode.

Can you fix 10px touch error?
I knew there was an touch error with it. (lineage-14.1-20180418-UNOFFICIAL-ChauTruongThinh-ef63.zip)
Here are fixed kernel on stock rom
https://drive.google.com/folderview?id=15z64YJoAhA1T5tSi1iGn-_mT25edOdNR[/url]
Can you fix it with this?
sorry about my poor english

Vega Iron 2 Call speaker problem.
Hi, I got LineageOS 16.0 (9.0 Pie ) to Vega Iron 2 IM-910S OpenGapps-ARM-9.0-Pico < Recovery - Flashify >
This phone CPU is rly good so I'm still use this phone
but 3 days ago, i got 1 important problem...
I need help with this issue (other guys too maybe.)
well this issue too have in 7.1.X upgrade device
If got call, ur call(Top) speaker sound will so much stiff sounds
but, good issue its not problem too under speaker , mike
I want fix this speaker but we can't go fix station anymore with this vega iron 2
I tried return normal rom to Vega iron 2
but still sound stiffing... so just got return again to Lineage 16.
I think any .xml is problem or idk where to problem and fix.... and I heard this phone speaker problem have some patch but I can't find that patch is where
any 1 know how to solve this? I need help rly TT_TT
and sorry to post here... I registered this site today ;6; but i need rly help with thisss

[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][Official][Nightly] LineageOS 17.1 for OnePlus 3/3T

LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.​
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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 17.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 17.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Changelog:
2019.10.24
Initial release
2019.10.25
Sync latest source
Fix bluetooth
2019.11.20
Sync latest source
Fix wifi display
Ship Snap
Fix vulkan graphics
Pass safetynet
Fix crash of some native services
2019.12.31
Sync latest source
SELiunx working in enforcing mode now
Update kernel to LA.UM.8.6.r1-02900-89xx.0
Update blobs from OOS 9.0.6
Fix suspend when AOD is on
Happy new year!
2020.1.12
Sync latest source
Fix ril of the last build
Update blobs from LA.UM.8.6.r1-02900-89xx.0
Add backuptools
Other trivial fixes
2020.4.2
Official nightlies started
Download:
https://download.lineageos.org/oneplus3
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: Android 10
Version Information
Status: Nightly
Created 2019-10-24
Last Updated 2020-06-26

Any recommendations which gapps to use?

Why not the official ones? https://sourceforge.net/projects/opengapps/files/arm64/beta/20191006/

is this with kernel 4.4?

helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
https://github.com/LineageOS/android_kernel_oneplus_msm8996/blob/lineage-17.0/Makefile#L1-L3

helderfp said:
is this with kernel 4.4?
Click to expand...
Click to collapse
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...

dianlujitao said:
Important information:
This thread is for LineageOS 16.0 builds for OnePlus 3/3T.
Click to expand...
Click to collapse
OP needs some changes its for LOS 17 instead of 16 [emoji3][emoji39]
Sent from my ONEPLUS A3003 using Tapatalk

Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.

Master_TC said:
No, 3.18.120 like all other Q roms for our phone.
Our phone doesn't support kernel 4,x. You need OnePlus 5 or above...
Click to expand...
Click to collapse
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
mady51 said:
ya i built it once but it didn't booted. after that didn't spent time on it. may be ill give it another try soon
Click to expand...
Click to collapse
Anyway amazing work @dianlujitao you're one of our heroes ???

Viper The Ripper said:
@nvertigo67 is right :good: , but there're others SnapDragon 820 devices, they've running a stable 4.4/4.9 Kernel long time ago, so it be could be possible.
https://github.com/YaroST12/Z2_Kernel/tree/4.4-eas-1.4
https://github.com/AOSiP-Devices/kernel_zuk_msm8996/tree/staging/pie-4.9
@mady51 said one time, he tried to compile a 4.X ver. for op3
Anyway amazing work @dianlujitao you're one of our heroes ???
Click to expand...
Click to collapse
https://github.com/dianlujitao/android_kernel_oneplus_msm8996 @dianlujitao did bring up a 4.4 kernel but it has issues.

Jus asked because of this

mvalda01 said:
Biggest problem I've found is Bluetooth. It connects and disconnects continuously until it crashes, so it's not usable. The status bar icons are not on the left but rather center-left once BT is activated.
Click to expand...
Click to collapse
Can you provide more info such as logs, my aptx headset works fine here.

Thanks for the effort,nice rom for nice phone.
From Op3 owner

Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Thanks, @dianlujitao, for this. Great to have Android 10 running on an encrypted phone.
I've been playing around with it all day and here's what I've found so far:
Clean install with Gapps from https://sourceforge.net/projects/opengapps/files/arm64/beta/ and Magisk 20 stable. Once I set the security patch date to 2019-08-01 I passed SafetyNet and was able to set up my credit card with Google Pay.
Missing:
- accent colours in settings>display>style>accent colour, though they are available in settings>developer options>accent colour
- battery text doesn't display
Broken:
- NFC: shows as being permanently on and can't be turned off; doesn't register on terminals
- Gallery shows album images in the Music directory (in Los 16 it ignores them). I've had to add a .nomedia file to the directory.
- settings>display>style>dark mode>Black causes LineageOS Settings to stop
- Digital Wellbeing keeps stopping (logs attached)
- BT connects/disconnects continuously when connected to my car (logs attached)
And that's all the issues I've got at the moment. Everything else is working fine.
I'll have a better idea of battery drain after tonight.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks for the report, bluetooth should be fixed in 1025 build, for Digital Wellbeing crash you should probably report to opengapps devs, I'm not sure.
NFC works fine for me, it wound be nice if you could grab related logs.

Well done @dianlujitao!

Thanks for your work @dianlujitao! I'll probably flash next build

@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.

MJPollard said:
@dianlujitao:
I've been trying to compile my own version, as part of my preparations for making the LOS17-based version of my personal custom ROM. I've got an unmodified LOS17 repo, the oneplus3 device tree, and the proprietary blobs repo from TheMuppets (which I had to modify to put WfdCommon into Android.mp and comment it out in Android.mk). It compiles up to a point, where I'm getting this error:
Code:
[ 0% 1/74451] build out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
FAILED: out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy.conf ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp neverallow -w -f out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/policy_2.conf || ( echo \"\" 1>&2; echo \"sepolicy-analyze failed. This is most likely due to the use\" 1>&2; echo \"of an expanded attribute in a neverallow assertion. Please fix\" 1>&2; echo \"the policy.\" 1>&2; exit 1 ) ) && (touch out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp ) && (mv out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows.tmp out/target/product/oneplus3/obj/ETC/sepolicy_neverallows_intermediates/sepolicy_neverallows )"
device/oneplus/oneplus3/sepolicy/hal_lineage_livedisplay_qti.te:3:ERROR 'unknown type hal_lineage_livedisplay_qti' at token ';' on line 83421:
allow hal_lineage_livedisplay_qti sysfs_livedisplay_tuneable:file { { getattr open read ioctl lock map } { open append write lock map } };
# Grant access over LiveDisplay tuneables
checkpolicy: error(s) encountered while parsing configuration
11:38:29 ninja failed with: exit status 1
I'm presuming that, since you're the developer for the oneplus3 variant, you've got things going on behind the scenes that have yet to be committed, and have already worked around this issue (if it is an issue and not something on my end). Not trying to steal your thunder or anything (my custom ROM is solely for my own use), I was just wondering if you had any insights you could offer. If there's any other information you need from me, just ask, I'll be more than happy to provide it.
Click to expand...
Click to collapse
You need to pick - at least - https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/255737 from https://review.lineageos.org/q/project:LineageOS%2Fandroid_device_oneplus_oneplus3+status:open, maybe all.
There's a good reason why OP calls it an experimental build instead of alpha or beta... Rebuilding experimental needs skilld and patience...
EDIT:
For the blobs commits (i.e. https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/260573 and https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/262330) see also https://github.com/dianlujitao/proprietary_vendor_oneplus/commits/lineage-17.0 .

BillGoss said:
- Digital Wellbeing keeps stopping (logs attached)
Click to expand...
Click to collapse
On some other Android 10 ROM, force stopping, disabling and then re-enabling solved this issue.