FORUMS
Remove All Ads from XDA

[UNOFFICIAL][ROM] LineageOS/Go 15.1 for Grand Prime [S920L/G530H/FZ/M/MU/P/T/T1/W]

1,067 posts
Thanks Meter: 1,896
 
By vince2678, Recognized Developer on 12th November 2017, 05:46 AM
Post Reply Email Thread
Announcement from vince2678: New builds are up (03/09/2018)


LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
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.


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

Quote:

Device Names

Quote:

Verify your device codename before downloading any firmwares or recovery images!

Code:
SM-G530T/T1/W - gprimelte
SM-G530P - gprimeltespr
SM-S920L - gprimeltetfnvzw
SM-G530MU - gprimeltezt
SM-G530FZ - gprimeltexx
SM-G530M - fortunalteub
SM-G530H (XX) - fortuna3g
SM-G530H (XC) - fortunave3g


Download

Instructions

Quote:



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.






Quote:


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.txt

then 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.txt

then try to reproduce the bug.

* The logcat file will be on your home directory.
* 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.




FAQ

Quote:

Q: Are you taking device requests?
A: No.

Q: Are you accepting feature requests?
A: No.

Q: Can you make XXX ROM as well as LOS?
A: No.

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

XDA:DevDB Information
[UNOFFICIAL][ROM] LineageOS/Go 15.1 for Grand Prime [S920L/G530H/FZ/M/MU/P/T/T1/W], ROM for the Samsung Galaxy Grand Prime

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

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

Version Information
Status: Beta

Created 2017-11-12
Last Updated 2018-09-03
Attached Thumbnails
Click image for larger version

Name:	Screenshot_20180207-011657.jpg
Views:	20822
Size:	30.2 KB
ID:	4412022   Click image for larger version

Name:	Screenshot_20180207-011741.png
Views:	21416
Size:	197.6 KB
ID:	4412023   Click image for larger version

Name:	Screenshot_20180207-011747.png
Views:	21522
Size:	53.8 KB
ID:	4412024   Click image for larger version

Name:	Screenshot_20180207-011755.png
Views:	21146
Size:	45.5 KB
ID:	4412025   Click image for larger version

Name:	Screenshot_20180207-012109.jpg
Views:	21286
Size:	32.3 KB
ID:	4412027   Click image for larger version

Name:	Screenshot_20180207-012124.png
Views:	20940
Size:	48.6 KB
ID:	4412028   Click image for larger version

Name:	Screenshot_20180207-012129.png
Views:	20034
Size:	63.0 KB
ID:	4412029   Click image for larger version

Name:	Screenshot_20180207-013151.png
Views:	19044
Size:	33.7 KB
ID:	4412030   Click image for larger version

Name:	Screenshot_20180207-013155.png
Views:	18448
Size:	43.4 KB
ID:	4412031   Click image for larger version

Name:	Screenshot_20180207-013220.png
Views:	17766
Size:	40.5 KB
ID:	4412032   Click image for larger version

Name:	Screenshot_20180207-013241.png
Views:	17564
Size:	48.6 KB
ID:	4412033   Click image for larger version

Name:	Screenshot_20180207-013258.png
Views:	16926
Size:	51.0 KB
ID:	4412034   Click image for larger version

Name:	Screenshot_20180207-013409.png
Views:	16568
Size:	39.9 KB
ID:	4412035   Click image for larger version

Name:	Screenshot_20180207-022736.png
Views:	16032
Size:	57.0 KB
ID:	4412036   Click image for larger version

Name:	Screenshot_20180207-022804.jpg
Views:	15948
Size:	31.9 KB
ID:	4412037   Click image for larger version

Name:	Screenshot_20180207-022837.jpg
Views:	15708
Size:	13.9 KB
ID:	4412038  
The Following 40 Users Say Thank You to vince2678 For This Useful Post: [ View ]
 
 
12th November 2017, 05:46 AM |#2  
vince2678's Avatar
OP Recognized Developer
Flag Toronto
Thanks Meter: 1,896
 
Donate to Me
More
Important
If this is your first time flashing O, you will need to install the latest unofficial TWRP image for your device from the links above before flashing a zip image, otherwise installation of a zip will invariably fail.

For SM-G530P users, use the gprimelte unofficial twrp instead of the gprimeltespr one.
For SM-S920L users, use the gprimeltetfnvzw official twrp instead of the unofficial gprimeltetfnvzw one.
The Following 11 Users Say Thank You to vince2678 For This Useful Post: [ View ]
12th November 2017, 05:46 AM |#3  
vince2678's Avatar
OP Recognized Developer
Flag Toronto
Thanks Meter: 1,896
 
Donate to Me
More
What works

Code:

* RIL (in-call audio, messaging, data possibly)
* Bluetooth (including audio)
* WiFi
* Audio (music, etc)
* Camera (including video recording)
* Flash
* Sensors
* GPS
Known Issues

Code:
SM-G530P | SM-S920L 
* [BUG]  In-call audio is buggy (there's a persistent ring tone during calls).
Code:
All devices
* [BUG]  NFC does not work. This is indefinitely broken
* [BUG]  Encryption does not work. This is indefinitely broken
Changelog

Code:
09/02/2018
* [NOTE]  Core control has been disabled permanently, in-kernel. 

* [NOTE]  NFC may (or may not) be working this build on capable devices.
   This is Untested. 

* [NOTE]  Rebased lineage-15.1 branches in repos. This is mostly
   for our benefit; just to tidy up the repos and make commit history more descriptive,
   accurate and give proper credits to commit authors. 
   
* [FIX]  Camera recording should be working again.
   This was broken due to upstream android security change. 

* [NOTE]  Reworked zram support in ROM. There are now two zram properties:
	ro.config.zram.enabled and ro.config.zram.size
	Set ro.config.zram.enabled true to enable zram;
	and ro.config.zram.size to set the size of the zram disk.

  If you set this too large the system will slow down. You can also just use a zram
  zip from the download server to do this automatically.
Code:
08/12/2018
* [BUG]  Camera recording is broken.
   This is due to upstream android security change. 

* [NOTE]  Reworked zram support in ROM. There are now two zram properties:
	ro.config.zram.enabled and ro.config.zram.size
	Set ro.config.zram.enabled true to enable zram;
	and ro.config.zram.size to set the size of the zram disk.

  If you set this too large the system will slow down. You can also just use a zram
  zip from the download server to do this automatically.

* [NOTE]  Enabled zram by default for low-ram (1GiB) devices 

Code:
07/26/2018
* [FIX]  Camera recording should be working normally again 
* [FIX]  sdcard (vfat/fat32) should work fine in recovery 
* [FIX]  Some stutter and lag issues have been fixed 
     (tweaked core_control, among others) 
* [NOTE]  exFAT support has been restored 
* [NOTE]  Re-enabled QS transparency 
* [NOTE]  Removed go-gapps from lineage-go 
* [NOTE]  Reduced kernel logcat buffer size from 512KB to 256KB (slight RAM saving)
* [NOTE]  zram has been disabled by default. If you want this, you can set the 
    property ro.config.zram to true
Code:
06/03/2018
* [FIX]  Frequency scaling issues should be fixed (stutter after suspend/resume should be gone). 
* [FIX]  In-call audio should be fixed on multi sim devices. 
Code:
06/01/2018
* [MISC]  Go GApps are now embedded in LineageOS Go builds. 
Code:
05/28/2018
* [FIX]  Frequency scaling should be fixed (improved power savings) 
Code:
05/21/2018
* [FIX]  Thermal engine is now working proper (for better temperature control) 
* [FIX]  Hidden Wi-Fi networks should now be connectable/reachable 
* [FIX]  Power hal is now working proper (resulting in improved battery usage)
* [MISC]  RIL includes updated 
* [MISC]  Misc. kernel updates (sdcardfs, binder) 
Code:
04/27/2018
* [FIX]  Brightness adjustment should be fixed for the fortuna3g/SM-G530H
* [FIX]  In-call audio should be working for the second sim on dual-sim devices
Code:
04/24/2018
* [FIX]  Sim detection should be fixed for fortuna* devices.
Code:
04/23/2018
* [MISC]  Added fortuna* devices.
* [FIX]  Video recording now works
* [FIX]  Bluetooth audio is fully working
Code:
13/03/2018
* [FIX]  In-call audio should be working in the latest build 

* [PARTIAL FIX]  Camera flash and previews should be working, however, saving pictures or videos will not work. 
Code:
06/02/2018
* [REGRESSION]  In-call audio is broken 
Code:
20/11/2017
* [FIX]  WiFi is working
* [FIX]  RIL functions (Calling, texting, data) should be working, including in-call audio 
* [FIX]  Music and video playback should be working 
Code:
12/11/2017
* [NOTE]  First working image built. 
The Following 10 Users Say Thank You to vince2678 For This Useful Post: [ View ]
12th November 2017, 12:35 PM |#4  
Senior Member
Thanks Meter: 173
 
More
Quote:
Originally Posted by vince2678

Quote:

Important:

If this is your first time flashing O, you will need to install the latest unofficial TWRP image for your device from the links above before flashing a zip image, otherwise installation of a zip will invariably fail.

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.

Is it possible to flash your latest TWRP 3.1.1 builds without Odin?

I see the recovery.img in the tar file. What I am really asking is if it is safe to flash this over itself? (i.e. by replacing the image in an older TWRP flashable zip file)

I don't have ready access to a Windows machine.

BTW, great work! The folks in the other thread are still struggling just to get a bootable build.

== EDIT ==

FWIW, I found a simpler way:
  1. Downloaded TWRP-3.1.1-lineage-14.1_j20_20171110_gprimelte.tar from the TWRP link in the OP.
  2. Extracted the recovery.img (renaming to TWRP-3.1.1-lineage-14.1_j20_20171110_gprimelte.img for recognition).
  3. Flashed this using TWRP. Choose the Install Image button from the Install screen.
manueltimz
12th November 2017, 01:05 PM |#5  
Guest
Thanks Meter: 0
 
More
Quote:
Originally Posted by Zippy Dufus

Is it possible to flash your latest TWRP 3.1.1 builds without Odin?

I see the recovery.img in the tar file. What I am really asking is if it is safe to flash this over itself? (i.e. by replacing the image in an older TWRP flashable zip file)

I don't have ready access to a Windows machine.

BTW, great work! The folks in the other thread are still struggling just to get a bootable build.

EXCUSE US
G530H has an oreo ROM(check telegram) just that the dev doesnt want to release a ROM without RIL. calls,text and data are the sense behind having a phne
12th November 2017, 02:21 PM |#6  
vince2678's Avatar
OP Recognized Developer
Flag Toronto
Thanks Meter: 1,896
 
Donate to Me
More
Quote:
Originally Posted by Zippy Dufus

Is it possible to flash your latest TWRP 3.1.1 builds without Odin?

I see the recovery.img in the tar file. What I am really asking is if it is safe to flash this over itself? (i.e. by replacing the image in an older TWRP flashable zip file)

I don't have ready access to a Windows machine.

BTW, great work! The folks in the other thread are still struggling just to get a bootable build.

Yes.
The Following User Says Thank You to vince2678 For This Useful Post: [ View ]
12th November 2017, 03:14 PM |#7  
Senior Member
Thanks Meter: 173
 
More
Quote:
Originally Posted by manueltimz

EXCUSE US
G530H has an oreo ROM(check telegram) just that the dev doesnt want to release a ROM without RIL. calls,text and data are the sense behind having a phne

My bad, sorry for misspeaking.

I'm just glad that folks are making progress with oreo on this device!

And I just want to be ready to flash when the ROM is ready.
19th November 2017, 08:45 PM |#8  
Senior Member
Thanks Meter: 173
 
More
Good progress
Well, just for fun, I managed to build a (11/19) bootable ROM.

However, once booted the screen was black except for the bluetooth, network strength, and battery icons in the top right corner.

Futzing with the buttons and touching the screen, I got a panel "Setup Wizard isn't responding" and choosing either "Close app" or "Wait" continued with the black screen.

Interestingly, a little "LTE" text item is displaying over the network strength icon. My build includes the commit which uses the A3 RIL libraries. I'm not sure if this is relevant to progress in that direction.

Also, it should be noted that I probably haven't done everything needed to build this ROM properly. I did discover the repopicks.sh script which was needed to make the build complete but I suspect that I am missing some other patching.

Regardless, a great start!!

Thanks @vince2678 and all the other MSM8916 contributors.
19th November 2017, 09:02 PM |#9  
vince2678's Avatar
OP Recognized Developer
Flag Toronto
Thanks Meter: 1,896
 
Donate to Me
More
Quote:
Originally Posted by Zippy Dufus

Well, just for fun, I managed to build a (11/19) bootable ROM.

However, once booted the screen was black except for the bluetooth, network strength, and battery icons in the top right corner.

Futzing with the buttons and touching the screen, I got a panel "Setup Wizard isn't responding" and choosing either "Close app" or "Wait" continued with the black screen.

Interestingly, a little "LTE" text item is displaying over the network strength icon. My build includes the commit which uses the A3 RIL libraries. I'm not sure if this is relevant to progress in that direction.

Also, it should be noted that I probably haven't done everything needed to build this ROM properly. I did discover the repopicks.sh script which was needed to make the build complete but I suspect that I am missing some other patching.

Regardless, a great start!!

Thanks @vince2678 and all the other MSM8916 contributors.

You installed GApps, that's why setup wizard is crashing.
The Following User Says Thank You to vince2678 For This Useful Post: [ View ]
19th November 2017, 10:45 PM |#10  
Senior Member
Thanks Meter: 173
 
More
Quote:
Originally Posted by vince2678

You installed GApps, that's why setup wizard is crashing.

Yes, I installed gapps and didn't think to not to do this for initial testing. Duh!

I'll try building/installing again in a week.

Thanks, and keep up the excellent work. My current build of your 14.1 ROM is simply awesome!!
20th November 2017, 11:47 PM |#11  
Senior Member
Thanks Meter: 173
 
More
A first look
Quote:
Originally Posted by vince2678

Code:
All devices
* [BUG]  WiFi does not work
* [BUG]  Camera and camera-related functions (flash) do not work
* [BUG]  RIL functions (Calling, texting, data) do not currently work 
* [BUG]  Music playback may not be working 
* [BUG]  NFC does not work 

I built and flashed a 11/20 ROM, this time without flashing GApps, because I was excited to see that the FM radio was enabled again.

Alas, there was only static on my G530W. I still would like to know if the hardware has been definitely crippled on this variant or perhaps mixing/matching the proprietary firmware from other variants might enable FM.

Otherwise:
  1. WIFI is working for me.
  2. I don't even see a camera app in apps panel. It is listed in Settings->Apps.
  3. The phone can make and receive phone calls but has no audio. This is the RIL issue?
  4. Music payback with the default Music app is working for me.
  5. NFC (Near Field Communication - is this bluetooth?) - sending a file using bluetooth didn't work from my computer although it could see the phone. "Connection refused" was the error message.
Other observations:
  1. The $WITH_SU flag doesn't work with Lineage so I didn't have root baked-in. This is a disappointment.
  2. ADB thru a cable doesn't work but it does for my NookHD+ so it isn't my desktop. Error below.
  3. ADB over the network does work.
  4. Mobile network is stuck in "Connecting" but this is glitchy on 14.1 because it is stuck too after a recent flash. Wait!? A reboot fixed this! Working now.
  5. Nice and smooth responsiveness.
So progress is being made!
adb W 11-20 18:06:28 27156 27159 usb_libusb.cpp:287] failed to open usb device at usb:1:14: LIBUSB_ERROR_ACCESS
The Following User Says Thank You to Zippy Dufus For This Useful Post: [ View ] Gift Zippy Dufus Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes