• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[UNOFFICIAL][ROM] LineageOS 13.0 for Galaxy Grand Prime [SM-S920L|G530FZ/MU/P/T/T1/W]

What device do you use?

  • SM-G530W

    Votes: 23 16.2%
  • SM-G530T

    Votes: 31 21.8%
  • SM-G530T1

    Votes: 12 8.5%
  • SM-G530P

    Votes: 7 4.9%
  • Other

    Votes: 74 52.1%

  • Total voters
    142
Status
Not open for further replies.
Search This thread

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,903


Code:
** Disclaimer
I am not responsible if flashing this ROM bricks your
   phone or causes thermonuclear war  and ends the
    world as we know it. You have been warned.


ROM Information


Device Names

Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-S920L[/B] - [COLOR="DarkSlateBlue"][B]gprimeltetfnvzw[/B][/COLOR]
[B]SM-G530MU[/B] - [COLOR="DarkSlateBlue"][B]gprimeltezt[/B][/COLOR]
[B]SM-G530FZ[/B] - [COLOR="DarkSlateBlue"][B]gprimeltexx[/B][/COLOR]
[B]SM-G530T/T1/W[/B] - [COLOR="DarkSlateBlue"][B]gprimelte[/B][/COLOR]
[B]SM-G530P[/B] - [COLOR="DarkSlateBlue"][B]gprimeltespr[/B][/COLOR]


Download




Instructions

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)
* 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

Under Windows:


Code:
[B]* Install samsung device drivers and then
 the adb utils from here:[/B]

[url]https://forum.xda-developers.com/showthread.php?t=2588979[/url]

[b]* Then enable developer mode, connect your phone to usb,
 and from [B]cmd[/B] paste this command:[/b]

[I]adb logcat > %userprofile%/Desktop/logcat.txt[/I]

[b]then try to reproduce the bug.[/b]

[b]* The logcat file will be on your desktop.[/b]



Under Linux:


Code:
[b]* Install the adb utils from your distribution's
 package manager and execute the command:[/b]

[I]adb logcat > ~/logcat.txt[/I]

[b]then try to reproduce the bug.[/b]

[b]* The logcat file will be on your home directory.[/b]

* Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.

* If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:

Code:
adb connect [ip address here]

And then the adb logcat command for windows.


Features

Code:
* The usual LineageOS features.
* All builds support over-the-air updates.

FAQ

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: Are you accepting feature requests?
A: Unless you're willing to implement it yourself, no.

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?

  • 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 :)


XDA:DevDB Information
[UNOFFICIAL][ROM] LineageOS 13.0 for Galaxy Grand Prime [SM-S920L|G530FZ/MU/P/T/T1/W], ROM for the Samsung Galaxy Grand Prime

Contributors
vince2678, minz1
Source Code: https://github.com/Galaxy-MSM8916

ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: >= 4.4 (KitKat)
Based On: LineageOS

Version Information
Status: Stable
Stable Release Date: 2017-03-27

Created 2016-11-01
Last Updated 2017-08-29
 

Attachments

  • Screenshot_20170104-142955.png.jpg
    Screenshot_20170104-142955.png.jpg
    68.1 KB · Views: 8,531
  • Screenshot_20170104-142910.png.jpg
    Screenshot_20170104-142910.png.jpg
    47.3 KB · Views: 8,373
  • Screenshot_20170104-142845.png.jpg
    Screenshot_20170104-142845.png.jpg
    55.3 KB · Views: 8,304
  • Screenshot_20170104-142803.png.jpg
    Screenshot_20170104-142803.png.jpg
    44.3 KB · Views: 8,017
  • Screenshot_20170104-142633.jpg
    Screenshot_20170104-142633.jpg
    91 KB · Views: 8,089
  • Screenshot_20170104-142617.jpg
    Screenshot_20170104-142617.jpg
    120.8 KB · Views: 8,008
  • Screenshot_20170104-142608.jpg
    Screenshot_20170104-142608.jpg
    70.6 KB · Views: 7,720
  • Screenshot_20170104-142546.jpg
    Screenshot_20170104-142546.jpg
    72.2 KB · Views: 7,517
  • Screenshot_20170104-142339.jpg
    Screenshot_20170104-142339.jpg
    98.7 KB · Views: 7,525
  • Screenshot_20170104-142407.jpg
    Screenshot_20170104-142407.jpg
    88.3 KB · Views: 7,507
  • Screenshot_20170104-142452.jpg
    Screenshot_20170104-142452.jpg
    55.1 KB · Views: 7,653
Last edited:

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,903
Reserved

Changelog

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

Code:
[B][U]29/08/2017[/U][/B]

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


Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The "message not sent" bug in text messaging
  app(s) should be gone. [/B]

Code:
[B][U]01/06/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and prima (wifi)
   driver to the latest caf branch LA.BR.1.2.9_rb1.18[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] The reboots caused by errors in the
  prima kernel driver should be gone.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
   Updated F2FS code from upstream kernel sources and enabled
   security extended attribute support (for SElinux) to fix
   android support.[/B]

Code:
[B][U]15/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Wifi driver is now built-into the kernel again.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] 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.[/B]

Code:
[B][U]05/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] 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.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
  J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]  
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] In-call audio should now work fully without having to
  toggle the loudspeaker. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should be fully functional [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Vibration should be working for SM-G530MU. The kernel
  config now specifies the correct vibration driver. [/B]

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

Code:
[B][U]07/04/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] The 2-ring bug should be fixed for the SM-S920L [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] Accelerometer and magnetic sensor (compass) should
be working proper on SM-S920L [/B]

Code:
[B][U]04/04/2017[/U][/B]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] NFC should be work for SM-G530MU as well
 as SM-S920L (after today's builds). [/B]

Code:
[B][U]26/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] G530FZ builds are working. [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] G530MU builds are working. [/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] Brightness control now works for SM-G530FZ. [/B]

Code:
[B][U]12/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] G530FZ builds are working [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] G530MU builds are still WIP [/B]


Code:
[B][U]12/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Unified SM-G530P.[/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Built TWRP 3.1.x for all devices.[/B]

Code:
[B][U]09/03/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] SM-S920L builds should be working now.[/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] G530MU and G530FZ builds are still WIP [/B]

Code:
[B][U]16/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added device S920L [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] 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. [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] 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. [/B]

Code:
[B][U]12/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.9_rb1.11 ] [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated kernel source [ to LA.BR.1.2.9_rb1.11 ] [/B]

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.


Code:
[B][U]06/02/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Changed to a new kernel source [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Refactored device trees [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Monthly security fixes from Google [/B]

Code:
[B][U]25/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added G530MU [/B]

Code:
[B][U]25/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Changed sources to LineageOS [/B]

Code:
[B][U]17/01/2017[/U][/B]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Reboot bug should be fixed. [/B]

Code:
[B][U]16/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Updated wifi driver [ to LA.BR.1.2.7_rb1.7 ] [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Removed ViperFX [/B]
*[B][[COLOR="Blue"]FIX[/COLOR]][/B][B] Screen timeout bug should be fixed [/B]

Code:
[B][U]07/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added KSM and ZRAM. These have to be enabled manually by
   setting "ro.config.ksm" and "ro.config.zram" in the build.prop to true. [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added Snap Camera [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Disabled engineering mode. [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Minor kernel tweaks. [/B]

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

Code:
[B][U]04/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] First alpha builds made. All alpha builds are set to engineering mode by default.[/B]

Code:
[B][U]02/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Added SM-G530P device [/B]

[B][U]01/01/2017[/U][/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Brought up kernel code [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] Built TWRP 3.0.x images for all devices [/B]
*[B][[COLOR="Blue"]NOTE[/COLOR]][/B][B] built cm-13.0 image for SM-G530W [/B]

Code:
[B][U]01/11/2016[/U][/B]
* [B] [ [COLOR="Red"]ALL[/COLOR] ][/B] [B] Created DevDB project [/B]



Known Issues
Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] None. [/B]
 
Last edited:

jdoggawesomex900

Senior Member
Nov 29, 2014
90
22
21
Modesto
If you go to his FAQ, he answers your question [emoji3]

Sent from my SM-G530W using XDA-Developers mobile app

How do I get to his FAQ?

---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------

you shouldn't right now since the CM-13 Images aren't uploaded yet or in other words, don't downgrade until they are uploaded, then you can downgrade;)
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
 
  • Like
Reactions: [email protected]
J

joe_5579

Guest
How do I get to his FAQ?

---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------


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.. )"
 
J

joe_5579

Guest
Yep, we are fixing small bugs on cm12.1, doing final builds and preparing the environment for the cm13, also we are improving the telegram channel and other things. Give us time :cool:
Very hyped and looking forward to this, Thank you all maintainers[emoji85] [emoji91]

Sent from My SM-G530W using XDA Developers app :)
 

kentone

Senior Member
Nov 29, 2012
119
51
Xiaomi Mi A3
  • Like
Reactions: kderb01 and leoon0
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 29


    Code:
    ** Disclaimer
    I am not responsible if flashing this ROM bricks your
       phone or causes thermonuclear war  and ends the
        world as we know it. You have been warned.


    ROM Information


    Device Names

    Verify your device codename before downloading any firmwares or recovery images!
    Code:
    [B]SM-S920L[/B] - [COLOR="DarkSlateBlue"][B]gprimeltetfnvzw[/B][/COLOR]
    [B]SM-G530MU[/B] - [COLOR="DarkSlateBlue"][B]gprimeltezt[/B][/COLOR]
    [B]SM-G530FZ[/B] - [COLOR="DarkSlateBlue"][B]gprimeltexx[/B][/COLOR]
    [B]SM-G530T/T1/W[/B] - [COLOR="DarkSlateBlue"][B]gprimelte[/B][/COLOR]
    [B]SM-G530P[/B] - [COLOR="DarkSlateBlue"][B]gprimeltespr[/B][/COLOR]


    Download




    Instructions

    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)
    * 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

    Under Windows:


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



    Under Linux:


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

    * Create a bug report at https://bugs.msm8916.com/ and paste the logcat there.

    * If you cant connect the device through adb on windows because the drivers, connect the device over wifi, enable adb over network on the quick setting tiles, and type:

    Code:
    adb connect [ip address here]

    And then the adb logcat command for windows.


    Features

    Code:
    * The usual LineageOS features.
    * All builds support over-the-air updates.

    FAQ

    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: Are you accepting feature requests?
    A: Unless you're willing to implement it yourself, no.

    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?

    • 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 :)


    XDA:DevDB Information
    [UNOFFICIAL][ROM] LineageOS 13.0 for Galaxy Grand Prime [SM-S920L|G530FZ/MU/P/T/T1/W], ROM for the Samsung Galaxy Grand Prime

    Contributors
    vince2678, minz1
    Source Code: https://github.com/Galaxy-MSM8916

    ROM OS Version: 6.0.x Marshmallow
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: >= 4.4 (KitKat)
    Based On: LineageOS

    Version Information
    Status: Stable
    Stable Release Date: 2017-03-27

    Created 2016-11-01
    Last Updated 2017-08-29
    4
    I thank you

    I know that they discarded the FZ because there was already a developer who was ahead with CM 13.1 for this terminal but anyway agradesco vince for taking this to develop a roms for this terminal since nobody cared for him, last a time with CM 12.1 and walked well in my FZ but now I run CM 13.1 of the other developer I believe it but a thousand thanks vince and your team for making a rom for this terminal thousand Thanks.
    3
    i am very very glad to see this!! i will be willing to test out builds for sure
    3
    yah any new here or is this thread just there for nothing

    If I wanted, I could just as well go and build cm-13.0 anyways, but it still would not work. I am working on bringing up (updating) the kernel code, and you will have to be patient since the kernel code is several thousands of lines and the Samsung kernel is largely out of date, but If you'd rather, I could go ahead and make builds that will never boot anyways.
    3
    I did a advanced wipe first, I wiped everything but it still wouldn't patch system image

    I'll issue odin builds as well for the next updates in the event something like that happens to a lot of people.