• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[UNOFFICIAL][OMS][ROM] LineageOS 14.1 for Galaxy J5 [SM-J5008/H/F/FN/G/M/Y]

Status
Not open for further replies.

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,900
0
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-J500F/G/M/Y[/B] - [COLOR="DarkSlateBlue"][B]j5lte[/B][/COLOR]
[B]SM-J5008[/B] - [COLOR="DarkSlateBlue"][B]j5ltechn[/B][/COLOR]
[B]SM-J500FN[/B] - [COLOR="DarkSlateBlue"][B]j5nlte[/B][/COLOR]
[B]SM-J500H[/B] - [COLOR="DarkSlateBlue"][B]j53gxx[/B][/COLOR]

Download



Instructions

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:
[B]
* Supports both MM/LL bootloaders.
* OMS/Substratum theming support.
* The usual LineageOS features.
* All builds support over-the-air updates.
[/B]
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][OMS][ROM] LineageOS 14.1 for Galaxy J5 [SM-J5008/H/F/FN/G/M/Y], ROM for the Samsung Galaxy J5

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

ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: >= 5.0.x Lollipop
Based On: LineageOS

Version Information
Status: Stable

Created 2017-04-12
Last Updated 2018-08-10
 

Attachments

Last edited:

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,900
0
Changelog

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

Code:
[B][U]11/09/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Rear camera focus and flash should be working in the latest builds. [/B]

Code:
[B][U]29/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Added KeyDisabler. For devices with touch keys controlled separately
  from the touch screen, this means that the virtual Nav Bar
  can be enabled in the Settings. [/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]
  
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Data should be working fully on all devices. [/B]
Code:
[B][U]22/08/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B]Updated xda post to include F/FN devices [/B]
Code:
[B][U]08/06/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] Video recording should now be working [/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]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] Touch screen should be disabled properly during
  calls and when the screen is off.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B][B] Rotation sensor should be working properly in
  the latest build.[/B]
* [B][[COLOR="Red"]FEATURE[/COLOR]][/B][B] OMS/Substratum support is now built into the
  ROM.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS is enabled in-kernel, so F2FS filesystem
  mounting and formatting should be working fully.[/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"]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"]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] Brightness adjustment should be functional. [/B]
Code:
[B][U]15/07/2017[/U][/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] RIL should be fully functional. The
  RIL service was not starting at boot for the second SIM. [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Fixed support for all bootloaders.
  The culprit was a hardcoded string in the bootloader
  passed to the kernel, which is not recognised if the
  bootloader is older than the display driver and vice-versa. [/B]
Code:
[B][U]12/07/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Build first image [/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Created DevDB project [/B]



Known Issues

Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] USB OTG does not work [/B]
Code:
[COLOR="RoyalBlue"][B]J5008/FN[/B][/COLOR]
* [B][[COLOR="Red"]BUG[/COLOR]][/B] [B] NFC does not work [/B]
 
Last edited:

Aadars

Senior Member
Nov 25, 2016
65
5
0
Kathmandu
when i try to install through twrp it shows an error which goes something like this:
E3004: This package is for device: gprimelte.......this device is j5lte
updater process ended with ERROR:7

I am currently using TWRP Aroma Installer
 
Last edited:

veez21

Elite Member
Feb 22, 2016
2,172
2,699
113
Guess Where
when i try to install through twrp it shows an error which goes something like this:
E3004: This package is for device: gprimelte.......this device is j5lte
updater process ended with ERROR:7

I am currently using TWRP Aroma Installer
This is only for H. You have another variant
 
K

krishnasaha95

Guest
when i try to install through twrp it shows an error which goes something like this:
E3004: This package is for device: gprimelte.......this device is j5lte
updater process ended with ERROR:7

I am currently using TWRP Aroma Installer
You have a J500F and you are trying to install a Grand Prime rom? ok
 

Aadars

Senior Member
Nov 25, 2016
65
5
0
Kathmandu
Installing the wrong device ROM...
Oh i got it ....had problem with aroma installer 3.0.2.1
Now i had succesfully installed it..hurray:angel :):)

---------- Post added at 05:13 PM ---------- Previous post was at 05:07 PM ----------[/SIZ

---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------

Just tried it and it is really awesome couple of bugs though but hope they will be shortly fixed
one of the bug is that the tile doesnt get managed if we drag it....other bugs are already mentioned by dev
Really thankful for dev for making it available for j500H
 

kim

Member
Feb 14, 2017
28
6
0
Seoul
There's a problem with the updater-script, if you're coming from a ported rom it'll detect different variant.
I've deleted the part that checks if the device is 3gxx. Voila.
 

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,900
0
There's a problem with the updater-script, if you're coming from a ported rom it'll detect different variant.
I've deleted the part that checks if the device is 3gxx. Voila.
That's not a problem with the updater script. That's a problem with the rom you're running not being compatible with the rom you're trying to install, and happens when there's a mismatch of device strings.
 

kim

Member
Feb 14, 2017
28
6
0
Seoul
That's not a problem with the updater script. That's a problem with the rom you're running not being compatible with the rom you're trying to install, and happens when there's a mismatch of device strings.
Okay it's not a problem in updater-script, but it detects j5lte in my j53g, maybe it's because of my current rom. But Thanks this Rom works with blazing fast performance ?
 
Status
Not open for further replies.