If you are completely new to flashing custom ROMs and have no idea how to begin, start by downloading a TWRP image for your device from the links above and flash it using the ODIN tool (see below).

You cannot flash a custom ROM over stock recovery, so downloading a custom recovery is the first thing you will need to do.

Installation via recovery (TWRP/LineageOS Recovery)

Quote:

* Download a recent .zip file from the links above for your device.

* Reboot into recovery mode [Press Power+Volume Up+Home].

* Wipe your data and cache partition (equivalent to doing a Factory Reset)
if you are coming from a stock ROM.

* Either: Plug in your phone into your computer, copy the zip file to a location on your Internal or External Storage on a device, click Install on TWRP on your phone and locate the zip file in the phone, or:

* Plug in your phone into your computer, and open Advanced->ADB Sideload on TWRP on your phone and swipe the slider to enter sideload mode.
Then open a command prompt/terminal on your computer in the folder you put the file by Shift-Clicking (Shift+Right Click) and selecting "Open Command Prompt/Terminal Here" (you will need to have adb installed) and type:

adb sideload name_of_zip.zip

to sideload the file. Replace name_of_zip.zip with the name of the file. If you are running Linux you may need to type adb kill-server and use sudo adb sideload if you get an `Insufficient Permissions` error.

* Download and flash GApps in the same way.

How to provide logcats

Quote:

Under Windows:

Code:

* Install samsung device drivers and then
the adb utils from here:https://forum.xda-developers.com/sho....php?t=2588979* Then enable developer mode, connect your phone to usb,
and from cmd paste this command:adb logcat > %userprofile%/Desktop/logcat.txtthen try to reproduce the bug.* The logcat file will be on your desktop.

Under Linux:

Code:

* Install the adb utils from your distribution's
package manager and execute the command:adb logcat > ~/logcat.txtthen try to reproduce the bug.* The logcat file will be on your home directory.

Q: Are you taking device requests?A: If and only if the device is using an msm8916 chip, and you're willing to buy me/donate the device for testing, sure.

Q: But I don't have that kind of money! What else?A: Alternatively, if you're skilled with Linux and adb, and have an unsupported device, if you're willing to work with me as a tester, that works as well.

Q: Can you make XXX ROM as well as LOS?A: Unless more people donate, no. I simply don't have the time to maintain more than LOS nor money to hold that many ROMs on my already (tiny) struggling server.

Q: Can I throw money at you?A: Most certainly. Donations are always welcome.

You want to help?

Quote:

We need hardware power to get the builds done.
If you want to help us go faster, send a PM to @kentone or
@vince2678. Your computer will act as a client for our jenkins server.

In a perfect world, that would be all, but unfortunately no. We need money to keep the server running and keep bringing these ROMs.

As always, logcat any problem you find.

PLEASE, don't PM @vince2678, as he's busy right now, and your questions can be not answered. PM @kentone instead, write here on the post, or on the telegram group, your questions will be responded as soon as we can Understand that we have family, studies and jobs aside of this project. Thanks for your understanding

For more detailed changelog information, see the changelog on the download or jenkins servers for each specific build.

Code:

29/08/2017
* [NOTE] Shifted to using a kernel driver for disabling touch devices
when the screen is off instead of a user service for that.
* [NOTE] Updated kernel to the latest upstream AOSP and
CAF tags. There should be a noticeable performance boost.
* [NOTE] Shifted to using OSS GPS code instead of prebuilt libs.
Location applications should be getting and reporting
satellite fix information properly.
* [NOTE] Disabled cpusets support, which was slowing
down the system performance.
* [FIX] The auto time zone feature should now be working
proper, (that is, without resetting the time zone
to 0000 UTC).

Code:

08/06/2017
* [FIX] The "message not sent" bug in text messaging
app(s) should be gone.

15/05/2017
* [NOTE] Wifi driver is now built-into the kernel again.
* [FIX] The sleep issue should be fixed in the latest build.
This was due to the failure to set a critical kernel
variable at boot because the kernel init system was
not interpreting a boot command line variable correctly.

Code:

05/05/2017
* [NOTE] Wifi driver is being built as a module for now,
transitioning to a new kernel somehow broke the ability
to build it into the kernel binary.
* [NOTE] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1).
* [NOTE] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16
* [FIX] In-call audio should now work fully without having to
toggle the loudspeaker.
* [FIX] Video recording should be fully functional
* [FIX] Vibration should be working for SM-G530MU. The kernel
config now specifies the correct vibration driver.

Code:

14/04/2017
* [NOTE] Wifi driver is now built into the kernel. Should
(slightly) improve speed of enabling/disabling wifi.
* [NOTE] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.14
* [FIX] Updated RIL in-call audio fix, microphone should now
work proper after the regression from last build.
* [NOTE] Builds now use sdcardfs from Google. This should
result in faster file operations on the sdcard overall
compared to using FUSE as an overlay.
* [NOTE] There have been several other changes as well,
mostly to the underlying structure of the kernel and device trees.

Code:

07/04/2017
* [FIX] The 2-ring bug should be fixed for the SM-S920L
* [FIX] Accelerometer and magnetic sensor (compass) should
be working proper on SM-S920L

Code:

04/04/2017
*[FIX] NFC should be work for SM-G530MU as well
as SM-S920L (after today's builds).

Code:

26/03/2017
*[NOTE] G530FZ builds are working.
*[NOTE] G530MU builds are working.
* [FIX] Brightness control now works for SM-G530FZ.

Code:

12/03/2017
*[NOTE] G530FZ builds are working
*[NOTE] G530MU builds are still WIP

09/03/2017
*[NOTE] SM-S920L builds should be working now.
*[NOTE] G530MU and G530FZ builds are still WIP

Code:

16/02/2017
*[NOTE] Added device S920L
*[NOTE] Unified the T/T1/W into one image. They are essentially the same device.
This should simplify development on my part and make it easier for everyone to
get the updates. And I can also be absolutely sure about bugs
since we'll be using the same image.
*[NOTE] Decreased minimal scaling freq. to 200Mhz.
The previous scaling frequency minimum of 800Mhz was pretty high, and could quickly
kill power on mobile devices. Lowering to 200Mhz should significantly extend batery life
on the stock scheduler.

There are a lot more minor tweaks and fixes. I don't have the time to constantly be updating this; I expect you'll read the
changelogs anyways since I take my time to write the commit messages in detail.

05/01/2017
*[FIXED] Audio should be fixed across all devices on the latest builds.
*[FIXED] Device and app hanging/crashing should be fixed as well.
*[FIXED] SD storage should be detected and mounted properly.

Code:

04/01/2017
*[NOTE] First alpha builds made. All alpha builds are set to engineering mode by default.

Ore you one of the ones helping to get booting cm13 images?I am hoping to have at least a testing build for my sm-g530t1 by January/February

No, I am not a helper of this ROM xD but hopefully we see something before then, but we also need to give him time too, and here, this is exactly what he said: "Whenever I have the time to actually fix any issues and get an image booting. The time will vary depending on various factors ( my mood, how much homework I have, how well fed I am, etc.. )"

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer? | Terms of Service