Database Info

LineageOS 13.0 for Samsung Galaxy Core Plus

Code:
#include <std_disclaimer.h>
/*
* 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.
*/
Introduction
This is a UNOFFICIAL build of LineageOS for the Samsung Galaxy Core Plus.
It's not ready yet and has some bugs in it which could cause problems to some users.
The ROM will only work on the SM-G350 Version of the Phone (without any Numbers/Letters behind).
This ROM could be used for daily use now (though you should look at the list of what doesn't work first).
Known Bugs
Camera sometimes switches to green-purple. The resulting picture doesn't have the weird color, but it may be flipped and/or distorted at the edges.
Video Recording
Codecs (some work, some don't. I tested MP4 and AVI, both work. I should really make a list...)
Installation Instructions
Special thanks to @Giovix92 for making this tutorial!
Requirements:
1: A computer with Windows.
2: An Internet connection.
3: A backup of your phone data (contacts, photo, music, videos, and other).
4: About 300 MB free space on your SD card.
5: Phone charged at least 80%.
Download links are below
I do NOT take any responsibility for bricked devices!
Let's start!
1: Download the Samsung USB Drivers.
2: Download the ODIN3. (Only for Windows)
3: Download the TWRP Odin package to your desktop and download the LineageOS 13 zip to your SD card.
4: Make a backup of your files, because the storage will be wiped. (External SD card will not be wiped)
5: Reboot your phone in to the Download mode (Volume Down- , Home- and Power button). Press the Volume Up button when asked. Then open the ODIN3 and connect your phone to your PC.
6: Press AP and choose the TWRP Odin package (recovery.tar) and make sure re-partition is NOT ticked. "Auto-Reboot" should not be ticked either, otherwise you will need to be quick to boot into the recovery immediately after flashing.
7: Press start! Wait a few seconds. Then your phone will be rebooted. Now you can disconnect the cable and power off your phone.
8: Boot your phone in to the TWRP Recovery (Volume Up-, Home- and Power button).
9: Go to Wipe, and Swipe to Factory Reset.
10. After wiping go to the home screen by pressing the home button.
11: Go to Install. Choose the "external_sd" from the top bar. (It says "Storage: Internal Storage (xxxxMB)" by default)
12: Choose the LineageOS 13 ZIP and Swipe to Confirm Flash. Make sure you don't power off while flashing!
13: After the zip has been flashed choose "Reboot System".
14: Wait 5-15 minutes to boot the phone. If the phone keeps booting take out the battery and do a Factory Reset again.
15: When the phone boots the first time, go through the Setup Wizard and you are ready to use your phone!
If there was something you didn't understand, please don't hesitate to ask
Changelog
23-01-2021:
Security patches until April of 2019
Updated Chromium from 67.0.3396.87 to 87.0.4280.101
Disabled latinimegoogle (which is compiled against an incompatible instruction set and results in crashes)
Fix offline charging
Old Changelogs:
02-05-2019:
Include all security patches up to January 2019 (and most of February and March, except for the PNG vulnerability)
NFC
Fix up some of the codecs (h264 and ac3, which should enable you to watch most videos)
Remove Gello (the old, bloated Browser) in favour of Jelly
Using way less hacks than previously (again)
05-04-2018:
Include all security patches up to March 2018
SELinux is now enforcing
OTA Updates the third (now using the internal Updater)
Using way less hacks than previously
24-05-2017:
Now compile with newest toolchain (Commit)
Fix SD Card (Device commit, Kernel commit)
Removed PMEM from the kernel (as this saves some RAM) (Commit)
OTA Updates (Commit)
18-04-2017:
Switch to LineageOS
4 Months of Security Patches
10-04-2017:
Fixed GApps (through a modified WebView)
07-04-2017:
Fixed Network (Commit)
Enabled permissive SELinux (Patch, Commit)
10-10-2016:
Bringup
Downloads
Samsung USB Drivers
Odin v3.09
Odin v3.11.1
TWRP 3
TWRP 2.8.1.0
lineage-13.0-20210123-UNOFFICIAL-cs02.zip
Sources
Device tree
Kernel tree
Proprietary files
WebView
Thanks To/Credits
Thanks to ...
... androidlover5842, ishantvivek, SandPox, ZIM555 and everyone else working on Samsung's hawaii-Boards
... berkantkz and santeri3700 for teaching me the basics of ROM developing

First Version of CM 13 is up

First! Good rom man!
Inviato dal mio ASUS_Z00A utilizzando Tapatalk

Hey !
i was happy when i saw that cm13 was out for our galaxy core plus so now i'm downloading it. After i will flash it if you want i can be a beta tester.
Thanks for this rom !
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
I installed it and for me the bigest problem is the wifi.

gaetano76le said:
Hey !
i was happy when i saw that cm13 was out for our galaxy core plus so now i'm downloading it. After i will flash it if you want i can be a beta tester.
Thanks for this rom !
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
I installed it and for me the bigest problem is the wifi.
Click to expand...
Click to collapse
Still working on that.

I just noticed that the sound sometimes "breaks" and sounds like damaged speakers (just for a part of a second, nothing permanent). I don't know if this is a software problem or just my phone. Can someone confirm that? It sometimes happens when doing a call or pressing random numbers at the Dialer. It also seems to happen only with standard sound level or higher.
I'll check it after I fixed (or tried to fix) Internet and SD Card

This is the same on stock when listening YT idk why it happens.
For the sdcard fix check if there are correct mounts for vold.fstab or framework
BTW. Videoplayback isnt working good on YT on Internet browser and is glitched too on chrome.

TimSchumi said:
I just noticed that the sound sometimes "breaks" and sounds like damaged speakers (just for a part of a second, nothing permanent). I don't know if this is a software problem or just my phone. Can someone confirm that? It sometimes happens when doing a call or pressing random numbers at the Dialer. It also seems to happen only with standard sound level or higher.
I'll check it after I fixed (or tried to fix) Internet and SD Card
Click to expand...
Click to collapse
bump
 @TimSchumi
http://forum.xda-developers.com/s7582/development/rom-cm13-0-galaxy-s-duos-2-trend-plus-t3307986
Maybe talk with this guys to allow to use their source? Will be easier to fix rom and you will can to support them too

So, any changes about the network?

QGM said:
bump
@TimSchumi
http://forum.xda-developers.com/s7582/development/rom-cm13-0-galaxy-s-duos-2-trend-plus-t3307986
Maybe talk with this guys to allow to use their source? Will be easier to fix rom and you will can to support them too
Click to expand...
Click to collapse
Thanks for searching :good:
I'll write to developer and ask for the fix!
john_sdr said:
So, any changes about the network?
Click to expand...
Click to collapse
Not now, still working on it. I don't even know where to search.

something about the vpn? or maybe something isnt compatible with cm13?

I searched on google and disable the firewall could be a solution.

john_sdr said:
something about the vpn? or maybe something isnt compatible with cm13?
Click to expand...
Click to collapse
Seems to be a more general problem. I'll look through the device/kernel/vendor trees of similiar devices for a fix.
SpYneX_ said:
I searched on google and disable the firewall could be a solution.
Click to expand...
Click to collapse
Could you test it?

TimSchumi said:
Seems to be a more general problem. I'll look through the device/kernel/vendor trees of similiar devices for a fix.
Could you test it?
Click to expand...
Click to collapse
How could you even disable a device's firewall?

Well, i just red here "https://forums.oneplus.net/threads/official-cm13-nightly-builds-rolling-out-for-opo.411202/page-103" that its may be fault of the recovery. I dont think that we all got the same twrp though, is something you can test? i used santori's twrp, i had it flashed quite a time. maybe an update or a modification will solve that issue

I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone

zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?

Hey, I'm new here at xda forums. I just installed this ROM on my galaxy core plus, and it works great. My phone is now super snappy. But many features don't work as of now, the bluetooth actually worked for me, I didnt expect it to after reading the post. When will these bugs be fixed, and more importantly how can I follow so that I can get my hands on the new release as soon as it gets out? Thanks a lot!

zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
john_sdr said:
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Click to expand...
Click to collapse
I also could try to make CM Recovery first, and if it won't work, I'll give TWRP a try.
Abiti7 said:
Hey, I'm new here at xda forums. I just installed this ROM on my galaxy core plus, and it works great. My phone is now super snappy. But many features don't work as of now, the bluetooth actually worked for me, I didnt expect it to after reading the post. When will these bugs be fixed, and more importantly how can I follow so that I can get my hands on the new release as soon as it gets out? Thanks a lot!
Click to expand...
Click to collapse
I still need to search what causes the Internet and SD Card to fail. Bluetooth does work, only Bluetooth Calls, Car connection and other devices are untested.
You can subscribe to this thread or subscribe to the DevDB project, to get a notification if it's updated. To get updates on your Smartphone, you could install XDA Legacy (Tapatalk) or XDA Labs (just called XDA) from Play Store.

john_sdr said:
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Click to expand...
Click to collapse
zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
CM Recovery didn't fix the problem. And I somehow can't get TWRP to boot.

[Treble GSI] [Umidigi One Max] GSI Experiments

Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10
Apparently it works as shown here: https://forum.xda-developers.com/showpost.php?p=80319007&postcount=13 credits to @4ctiv_
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Tethering doesn't work with data ON !
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
NFC doesn't appear at all. There is a fix with magisk tho ! See here (NFC4PRA)
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops​
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone

Make sure to check out my guide on installing GSIs at https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521/

I downloaded system-arm64-ab-gapps-su.xz, extracted the file, booted into TWRP, did a full wipe, and installed "image" system-arm64-ab-gapps-su.img. TWRP asks which partition to install it to. I selected "system". However, after install I go to reboot, and TWRP complains there is no OS. Am I missing something?
I did a complete backup in TWRP of all important partitions first (nvram, modem, system Etc.), so going back to my stock setup was not difficult. Those trying this, backup all important partitions from TWRP on to microsd!

For everyone, make sure you download AONLY images, not AB !

_cab13_ said:
Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10 Q Beta
Beta 4 : Probably not working, as our device is not system-as-root (but is VNDK isolation compatible)
Still needs testing
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Wifi access point doesn't work.
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops​
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone
Click to expand...
Click to collapse
I posted this in another forum, but for the life of me I do not know what is causing this issue. I installed RR rom located here:
https://get.resurrectionremix.com/?dir=gsi/
system-190120-arm64-aonly-vanilla-nosu.img
I also install, Gapps (pico), and Magisk.
It runs great, for the most part. However, if I start streaming a video from any app or start streaming music, after a short amount of time my Umidigi One Max:
A.) Announces, "Powering Down"
B.) Boots directly into TWRP
C.) If I reboot, it again boots directly into recovery. Almost as if the partition became corrupted.
D.) Try to recover a backup I made in twrp, reboot, again boots straight into recovery.
E.) If SP Flash can communicate with the phone, I can usually push all the stock images back to the phone. If not, I have to push the images via fastboot with my Ubuntu PC.
If I do any other CPU intensive task under a GSI ROM, it doesn't have this issue, only when I stream video. I haven't tried any games to see if it causes this behavior.
I have tried multiple GSI Roms located here too, same problem:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I do not believe the device is overheating, it's usually around 32-34C from the TWRP menu at that point. I really like the RR Rom, but if I cannot figure out what is causing this, I'll have to stray away from GSI for now.
As a sidenote, this issue of the device suddenly powering down after starting to stream a video, does not happen with the stock ROM. I am kind of at a loss on this one.
Weirdest thing I have experienced running a custom ROM.

Yeah it happened to me sometimes as well... The phone goes straight into recovery and then never goes to system again. I haven't found the cause of it.

Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)

phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.

w1lh3lm3d said:
Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)
Click to expand...
Click to collapse
I posted a fix that works. Here it is if you didn't see : https://forum.xda-developers.com/p8...pment/flashable-nfc-kirin655-devices-t3811916
tomprc said:
phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.
Click to expand...
Click to collapse
I don't get any performance issue. The only issues is that some ongoing calls doesn't come, and sometimes 4G totally glitches out. Other than that it's pretty much all.

@ _cab13_
i cant find the vendor folder in twrp in the mount section or in the file manager.
what have i done wrong? ok i started from scratch and then it worked porfectly
thx you for your work and help

Engineering mode access or work around
On the 9.0 ROM I cant seem to access engineering mode via the keypad, I need to sort the handset speaker out. Is there any other way to access it or some way of tweaking the voice settings through the shell?
Any help would be appreciated.

Please help
I'm trying to get the new phh Android q to boot and and I'm a newbiew

Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )

On Phh's 9 v119 Is the headphone jack sensor working for anyone. (If so how)

4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
Click to expand...
Click to collapse
did you use the a only or ab image?

I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!

seiyria said:
I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!
Click to expand...
Click to collapse
I'm in the same boat bro. I've just tried both the latest phhusson AOSP 10 ROM as well as an older version of the same ROM, and both time I get caught in a loop after install. Completely wiped beforehand, tried installing with and without Magisk/Disable-Force-Encryption. Going to have to bring it back down to Android 9. I wonder how 4ctiv_ got it working?

so first you have to no encryption then erase and format data
flash android 10 arm 64 a without gapps build (image) to system i use havoc 3.5 and everything exept nfc works
then install gapps (it failed for me so i had to resize system in twrp and install gapps again
last step is to flash the custom phhson magisk
then just reboot wihout wipping

Thank you so much for your work...
Hi, I'm a long time Android user and I used to code apps, if I can be of any help please let me know but I'm now disabled wheel chair user with dystonia so I find it extremely difficult to type now so I use voice to text... I really enjoy using the umidigi one max it has the storage and usability of a much more expensive phone, also functionally for me the wireless charging and NFC make my life so much easier as I find cables akward and payments at shops much easier.
I read about the Treble programmea while ago and recently read this article and if it is possible to get the NFC working on this update, I will be so greatful as it will extend the life of this great phone for me.
Good luck with your work and thank you in advance.
4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )
Click to expand...
Click to collapse

[ROM][UNOFFICIAL][9.0.0] LineageOS 16.0 [BETA][16.04.2020] for i9305

Code:
/*
* 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.
*/
This is an unofficial Pie build for the S3 LTE (i9305) based on LineageOS 16.0.
!! Please note that all thanks and credits go to @ChronoMonochrome because he ported the necessary changes to t0lte and got Pie to work for that device, especially the kernel thingis!!​
And below is a quote from his release, where he mentioned in his t0lte thread all the involved devs and credited to all the people helped to get pie running for our "old" devices.
This work is heavily based on works of PoisonNinja, Option58 (thanks for device tree, kernel and device patches for LOS 14.1).
A full credit for Pie bringup goes to rINanDO (thanks for device tree, kernel and device patches for LOS 16.0).
Click to expand...
Click to collapse
Working
Graphics
Wifi
Data (LTE is not supported currently)
RIL
Bluetooth (needs more testing, receiving files is working, sending I am not sure, also device name needs a change)
Sensors (needs more testing, proximity sensor works, others not sure whether it work)
Vibration
Camera (advanced settings not working switched to snap cam and its working now)
Audio
LED Notification, color and brightness settings
Pico Gapps are working, Youtube and Google Films are well
livedisplay
etc
Not tested, needs testing
Call recording, call forwarding and else
NFC (needs more testing, not sure whether it work)
GPS (got a fix with gps status, first fix lasts a minute, nexts are much faster) currently getting worse, have no fixes 14/03/20
Bugs
feel free to report them, will try to find a solution, but no promise
Download:
ROM
TWRP
Root
Installation:
I am using an older TWRP, which is working fine: TWRP_2.8.7.0_alpha17_by-SdtBarbarossa_i9305.zip
Download the latest build and copy it to the phone
Factory reset in TWRP (Very important! Do not skip)
Wipe cache, Data, System and Dalvik in TWRP advanced (Very important! Do not skip)
Flash LineageOS 16.0
Optional: Flash gapps and root package
Reboot
Be patient. The first boot will take between 5 - 15 minutes.
Enjoy and have fun
Credits:
rINanDO
forkbomb444
Option58
PoisonNinja
AdrianDC
A$teroid
Lord Boeffla
LineageOS team
Nameless ROM
If I miss someone, please PM or post here, and I will add you
Source code: LOS 16.0
XDA:DevDB Information
LineageOS 16.0, ROM for the Samsung S3 LTE (i9305)
Contributors
rodman01, ChronoMonochrome, rINanDO, Option58, PoisonNinja, LineageOS team
Source Code: https://github.com/CustomROMs/android_local_manifests_i9300/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
ROM Firmware Required: TWRP_2.8.7.0_alpha17 or newer
Version Information
Status: Beta
Created 2020-01-15
Last Updated 2020-04-16

reserved
if I need one

reserved
maybe another one needed?

nice job dev @rodman01
Well done

Hi, thanks for your great job!
Almost features are fine. I recognized only two stuffs for now.
** 1) phone call **
I set up a VoIP phone app on a phone which was flashed this rom, and called another phone.
The echo back is heard on the VoIP app side, but I could not hear the voice I talked on the receiving phone.
Do you think above phenomenon is related your attention "Call recording, call forwarding and else" or not?
2) FTU was appeared a few times
When I started using this rom, FTU appeared twice or more after I went through FTU.
But as for now I don't see FTU anymore. Thus, this is a trivial issue.
Anyway, I am looking forward to seeing the next updated version!

small update
Hi There,
gapps pico are working, but graphical glitches are occurring in youtube app, youtube browser is working fine, google films is working fine.
Bluetooth sending and receiving is working, device name is still wrong, shows still Galaxy Note 2, which does not matter and can be changed in settings manually.
Download
lineage-16.0-20200118-UNOFFICIAL-i9305_rodman01.zip https://www.androidfilehost.com/?fid=4349826312261704972

phone call problem was solved! thanks!! :good: :laugh:

super
Fantastic . I will keep an eyes to this.
thank you so much !

trying the rom
What file should I download from the root link ?

new build is up: 20200122
Hi There,
made a new version nd its uploaded now.
Based on yesterday evening leo sources and small update in device source.
- Youtube App is now working and Google films too
No other bigger changes.
And since there are no reports yet about serious problems, I changed the status to from Beta testing to bBeta.
Whats App, Instagram, Facebook and other messengers as well as other social media apps needs testing and would be glad, if someone can report back.
GPS most probably won't work. I am getting no satellites and no fix
Download
lineage-16.0-20200121-UNOFFICIAL-i9305_rodman01.zip: https://androidfilehost.com/?fid=4349826312261708954

Im trying to install this custom rom but everytime I got stuck on LineageOS loading logo forever. Anyone have this problem too?

some problems...
on 20200118 ver.
1) following apps sometimes crashed.
LINE, Adobe photoshop express, Amazon Shopping, Proton Mail.
I felt these apps often crash especially when a first invocation and registering an account to every app via network.
After registered my account, crash frequency decreased.
2) following apps couldn't be installed by Google Play Store
LINE, Google Drive, Google Spreadsheet
* For LINE, I installed older apk manually.
I cannot download 20200121 ver. via AFH yet. I'll test further after the rom is updated.

MagusCoD said:
Im trying to install this custom rom but everytime I got stuck on LineageOS loading logo forever. Anyone have this problem too?
Click to expand...
Click to collapse
Have you wiped out data, cache, and Dalvik cache before install the rom?
If you didn't yet, try it but ALL OF YOUR DATA WILL BE CLEARED!!
Be aware of what you're doing and do everything at your own risk.

I got the same issues .
I keep it stuck there for almost 40 minutes 2 times but it didn't work.

@rodman01
I intend to flash and test the ROM this weekend. However, I've issues to download it as AFH doesn't find any mirror. Do you have another DL available?
Another question: Anything against not to use your given and linked root solution but to use Magisk? As you provide a separate root solution, I assume Magisk is not incorporated into the ROM.

MagusCoD said:
Im trying to install this custom rom but everytime I got stuck on LineageOS loading logo forever. Anyone have this problem too?
Click to expand...
Click to collapse
ximia said:
Have you wiped out data, cache, and Dalvik cache before install the rom?
If you didn't yet, try it but ALL OF YOUR DATA WILL BE CLEARED!!
Be aware of what you're doing and do everything at your own risk.
Click to expand...
Click to collapse
Depending on from which rom you are coming, it could be better to flash an other custom rom first. You can try RR or cm14 and test whether this is working. And if yes, that follow the steps in op for a new and clean installation. It can also depend on the recovery you are using.

ximia said:
I cannot download 20200121 ver. via AFH yet. I'll test further after the rom is updated.
Click to expand...
Click to collapse
Oswald Boelcke said:
@rodman01
I intend to flash and test the ROM this weekend. However, I've issues to download it as AFH doesn't find any mirror. Do you have another DL available?
Another question: Anything against not to use your given and linked root solution but to use Magisk? As you provide a separate root solution, I assume Magisk is not incorporated into the ROM.
Click to expand...
Click to collapse
Sorry for the issues with afh. I will try to fix it with uploading the version again.
@Oswald Boelcke no specific reason why I linked the root to leos. Magisk should work as in previous versions. I tested it a couple of weeks ago with a prototype version and it worked. So its worth to try magisc, yes.

Rom new uploaded, afh should find mirror now. Sorry for circumstances:
lineage-16.0-20200121-UNOFFICIAL-i9305.zip: https://androidfilehost.com/?fid=4349826312261708954

rodman01 said:
Rom new uploaded, afh should find mirror now. Sorry for circumstances:
lineage-16.0-20200121-UNOFFICIAL-i9305.zip: https://androidfilehost.com/?fid=4349826312261708954
Click to expand...
Click to collapse
Affirmative, just downloading. Thanks a lot!

ximia said:
on 20200118 ver.
1) following apps sometimes crashed.
LINE, Adobe photoshop express, Amazon Shopping, Proton Mail.
I felt these apps often crash especially when a first invocation and registering an account to every app via network.
After registered my account, crash frequency decreased.
2) following apps couldn't be installed by Google Play Store
LINE, Google Drive, Google Spreadsheet
* For LINE, I installed older apk manually.
Click to expand...
Click to collapse
I could install all your mentioned apps via google play store. It last a bit, the download is not fast, but worked on my end. Amazon is crashing on my side too, the others not, but I haven't tested them much, because I don't have accounts or ids for for example photoshop express or want to create or share my phone number or personal details.

[DISCUSSION] LineageOS 17.1 [HLTE/CHN/KOR/TMO][OFFICIAL]

Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator

Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?

asassello said:
Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?
Click to expand...
Click to collapse
1 : yes
2 : yes..update maybe your modem

re 1: yes2 (using it quite some time on various devices and it seems to do what I expect it should do, though some apps seem to bypass the 'normal' DNS resolution. OT: And I'm still haven't made up my mind yet if DoH or DoT are good or bad ...)
re 2: dark mode? What's that?

rayman95 said:
1 : yes
2 : yes..update maybe your modem
Click to expand...
Click to collapse
Are you sure NFC works? I mean paying in shops? I updated modem and now it's N9005XXUGPQB1. And paying still doesn't work. I've just tried.
odoll said:
re 2: dark mode? What's that?
Click to expand...
Click to collapse
Sorry. It's dark theme (I don't have English set as default language). [emoji846]

installation error

https://download.lineageos.org/hltetmo

Can somebody please confirm that paying through NFC works? If so - what's your modem and baseband?
Also I've installed GAPPS PICO maybe that's the case? Although on LOS 16 I also had Pico and it worked, but maybe I'm missing some app like Google search or something?

Been using Lineage OS 16 ever since it was officially released for HLTE. I gotta say, the development of that release has came a long way and by the time of writing this, I'd say it's the most stable and clean custom rom for the Note 3 out there.
I did try the new release the second I received a notification for an update. How did it go? Well let's just say I'm glad I created a full system backup before wiping LOS 16. This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
I do appreciate all of the time that the devs are still willing to put into the platform. However I'd recommend users that are looking for a rock stable experience to stick with Lineage OS 16 for the time. You're not missing out on a lot.

loudseries said:
This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
Click to expand...
Click to collapse
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx

odoll said:
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx
Click to expand...
Click to collapse
I have to agree with you, because except my 2 issues (with NFC payments and night mode that doesn't switch automatically) I actually don't have any other problems.
Ver. 17 seems faster and snappier than 16.
Also on 16 sometimes sharing from ie. Firefox to WhatsApp caused the later one not loading (just black screen).
So for me only that NFC seems to be a real issue. Other than that I'd advice anyone trying 17.

made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...

rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
for me the only difference is the size of the home screen changed (changed trebuchet to a larger grid before), otherwise i would not even have noticed it is not 16 anymore, rock stable even after a dirty flash

rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect.
Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?

Scorpionea said:
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect. Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?
Click to expand...
Click to collapse
I'm on PQB1 nordic modem and BRL1 bootloader.

rayman95 said:
I'm on PQB1 nordic modem and BRL1 bootloader.
Click to expand...
Click to collapse
Have the same as you . I thought it could be bootloader issue but guess not.
Thx

Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...

odoll said:
Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator
Click to expand...
Click to collapse
Hello. I have the latest version of LineageOS 16 installed and TWRP (3.3.1.0). I ask you if, after transferring the ROM file to the phone, it is possible to use TWRP to upgrade to 17.1 (by installing the zip file) or if I have to use ADB shell (as it says on the LineageOS official site).
Sorry I'm not an expert and some steps are not clear to me
Thank you
PS
Why you wrote "dirty"
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.

Hi Apten
i) think your Qs won't need a full quote
ii) drity flashing
iii) sure you can DL the ROM (and TWRP) to your (internal RAM) of your phone and upgrade or clean install from recovery (twrp)

rayman95 said:
Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...
Click to expand...
Click to collapse
I've just dirty updated from 1010 to 1017 build . Will see how it goes later on.
Just tested with chrome downloading lineage and no issue with Fc

[ROM]|SM-T520|SM-T900|[UNOFFICIAL] LineageOS 17.1 | Android 10

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Special thanks to Exynos5420 team and LineageOS for all the sources.
Use SM-T900 build at your own risk. I can't guarantee you it will work, because I have no device to test it on.
Work
Almost everything
It has pretty much the same functionality as Lineage 14.1
Known Issues
Built in mic not working
USB problems
You tell me...
Installation:
1. Flash latest official Samsung Firmware with ODIN
2. Flash latest TWRP Recovery: SM-T520 - SM-T900
3. Backup all partitions
4. Wipe Cache and Data
5. Install ROM.ZIP
6. Install latest GApps (ARM/Android10) https://opengapps.org/
7. Reboot and Enjoy
8. Optional: Install Magisk
For SM-T520 TWRP recoveries 3.1.1.0 and older will not flash this rom ending up with error 7: incompatible device.
Make sure to flash TWRP mentioned above.
Download:
SM-T520
SM-T900
I ll probably create builds with updated security and device code patches occasionally.
Enjoy fresh new Android!
Sources:
https://github.com/LineageOS (LineageOS 17.1)
https://github.com/exynos5420/ (Kernel, Device, Vendor)

Damn!! Just installed and working.
Really good work! Thanks!!!!
i found a bit problem, starting android it loops between voice assistant and set lock for tablet. i needed connect earphones with microphone to finish voice assistant configuration and then it continued.
Thanks for rom!

@TechDriver can You build a LineageOS 17.1 ROM for SM-T900 who is used the same Exynos5420 CPU?
If is necessary I can be a beta tester.

manix01 said:
@TechDriver can You build a LineageOS 17.1 ROM for SM-T900 who is used the same Exynos5420 CPU?
If is necessary I can be a beta tester.
Click to expand...
Click to collapse
You got it there try it out!

Larision said:
Damn!! Just installed and working.
Really good work! Thanks!!!!
i found a bit problem, starting android it loops between voice assistant and set lock for tablet. i needed connect earphones with microphone to finish voice assistant configuration and then it continued.
Thanks for rom!
Click to expand...
Click to collapse
Did you install on the t520 or the t900? Did you really go back to the Samsung official build first? (I'm on t900 lineage 14.1)

pjotrski1000 said:
Did you install on the t520 or the t900? Did you really go back to the Samsung official build first? (I'm on t900 lineage 14.1)
Click to expand...
Click to collapse
You don't need to go stock, just backup your data using TWRP and follow installation steps above. I am little unsure about build for T900 because I do not own this device, so I wait for someone who can report me if it works or not.

@TechDriver Clean flashed 17.1 over 14.1 without flashing stock on T900 using twrp-3.5.1_9-0 and it flashed great. I plugged in a headset but my Hey Google was already recorded and didn't give me any trouble. I don't know what would have happened if I hadn't plugged in the headset. Play Store does not recognize my already purchased apps. This usually means something is not right and I wonder if not flashing stock first is related to this? Can be very smooth but can be a little glitchy as well. Still experimenting and trying things. Bluetooth Keyboard and Mouse work great. Thank you for this.

kb8no said:
@TechDriver Clean flashed 17.1 over 14.1 without flashing stock on T900 using twrp-3.5.1_9-0 and it flashed great. I plugged in a headset but my Hey Google was already recorded and didn't give me any trouble. I don't know what would have happened if I hadn't plugged in the headset. Play Store does not recognize my already purchased apps. This usually means something is not right and I wonder if not flashing stock first is related to this? Can be very smooth but can be a little glitchy as well. Still experimenting and trying things. Bluetooth Keyboard and Mouse work great. Thank you for this.
Click to expand...
Click to collapse
It has probably something to do with missing play protect certification. I will try to sign device for certification but need someone with T900 who will cooperate with me. For now easiest way to avoid problem is going to browser version of play store and installing paid app to specific device from there. It should work fine. Also thanks for testing and reporting that T900 build works.

Just for understanding, these are still 32 bit builds, vor did you switch to arm_64?

@TechDriver SELinux is not enforcing. That may be why Google Play does not recognized my purchased apps. Installing purchased apps trick from Google Play on the web worked as expected. Booting tablet, it does not accept passcode on the first try, but works on second try. This is repeatable. I will be happy to be your T900 tester if you make some test builds.

hamudistan said:
Just for understanding, these are still 32 bit builds, vor did you switch to arm_64?
Click to expand...
Click to collapse
Exynos5420 is 32bit SoC. It doesn't support arm64

@TechDriver The pass code works the first time if you are not impatient and click the accept arrow before the last number changes to a dot. There is a delay and the passcode entry is laggy and you have to be patient for a few seconds. twrp-3.5.1_9-0 is able to back up and restore 17.1 with no problem.

@TechDriver The first login with PIN after booting will fail. The second and future screen saver logins will work with the caveat that you are patient until the last number turns into a dot.
Pixel launcher does not work correctly with mouse clicks and has a focus graphics glitch. It works right as long as you don't click the mouse. If you click with the mouse to open a group of icons in a folder it leaves a residual grey box behind. You can see this same grey box where the PIN numbers appear on the screen saver as well. I changed to Nova Launcher and the problem improved with the grey box occurring if I open the icon folder and actually open an app but then disappearing on moving into a different folder. This is all with the exception of the PIN screen saver which causes the same grey box on both launchers. Something is not quite right with the graphics using mouse.
I mostly use this tablet with keyboard and mouse and Nova is more acceptable now. I prefer Nova Launcher anyway as it is much better at using the whole screen.
The camera is extremely basic. Open Camera seems to be an improvement. Any Google Camera port available that might work?

Just to make things clear, I am not developer of code and not skilled enough to make changes in it. For this job, there is team exynos5420 and other cool contributors to make device sources. I use their device sources from exynos5420 and LineageOS github to build together final product... Rom.zip you install on device. I can't fix bugs, i only can wait until some contributor fixes it and I will build rom with fixes and updated security patches included.

@TechDriver Got it. Will the devs be watching this thread for feedback?

kb8no said:
@TechDriver Got it. Will the devs be watching this thread for feedback?
Click to expand...
Click to collapse
I am unsure about that, most of original devs for n2awifi and v2awifi stopped developing code for this devices. Keep an eye on exynos542X github for new commits.

First of all I want to thank you for the this ROM.
I tried this ROM with the latest TWRP version for two days and I want to inform that it is working good with some small non-conformities:
I had some random reboots and the system crashed and freezing
After rebooting there is a long time after entering the unlock pattern, sometimes it is necessary to enter the pattern several times.
I have installed ROM, gapps nano rebooted and after that install Magisk 22.1
my model is SM-T900

@TechDriver ,Great work on this build! Never thought I would see this accomplished. Many thanks and keep up the good work. This is fully usable with Nova beta 7.0.27.

Works perfectly on my T900, many thanks! Keep up the good work!

stanl56 said:
@TechDriver ,Great work on this build! Never This is fully usable with Nova beta 7.0.27.
Click to expand...
Click to collapse
Can you provide a link for this latest Nova beta? APK mirror seems booked.
Nova 7.0.27 Works smoother and scrolling and moving icons is better. PIN screen on first login is same problem and will not work on the first try. Mouse clicks and mouse related screen painting remains an issue. If you don't use a mouse you may not notice any problems other than first login. Come to think about it, 7.1 had issues with the mouse most noticeable when I used Collabora and I had attributed it to the app.