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.

Lineage OS 13 Alpha 4 (links to LOS 14.1 port and TWRP 3.1.0-0 in second post)

Not sure if you guys are seeing this over on androidforums so im posting it here too
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
************************************* Start of dev info***************************************************
kernel sources based off of v20k: https://github.com/touchpro/android_kernel_lge_stock-v20k
all the device and vendor trees are based off of teamregular's work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos13
g4stylus-common: https://github.com/touchpro/android_device_lge_g4stylus-common
vendor: https://github.com/touchpro/android_vendor_lge
also you need a few modded hardware/qcom folders, until the kernel gets updated to play nice with caf sources:
audio-caf: https://github.com/touchpro/android_hardware_qcom_audio-caf
display-caf: https://github.com/touchpro/android_hardware_qcom_display-caf
******************************************End of dev info***************************************************
I would recommend using my TWRP here to flash it: http://androidforums.com/threads/update-twrp-3-0-3-0-built-from-source-2-18-17.1103219/
what I know works:
display
touchscreen
vibration
ril (calling and texting. i cant test data since i dont have a data plan atm)
wifi
buttons
adb
mtp
panel backlight brightness adjustment
camera
video recording
internal storage
external_SD
sound
bluetooth (file transfer, audio)
youtube/netflix (any others i didnt test but i bet they work)
wired headset sound and microphone
microphone
gps/location services
compass
rotation
flashlight and camera flash
nfc (dunno what works and what doesnt, dont have another nfc device or android pay)
notification led
what doesnt work:
double tap to wake
data (manual network selection now works, im getting closer)
maybe some other things
The rom zip:
https://www.androidfilehost.com/?fid=673368273298938085
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 6.0)
THIS DOESNT COME WITH SU AND THE ONLY WORKING SU I FOUND IS SUPERSU!
Download it here: http://www.supersu.com/download
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!

Also,
Lineage OS 14.1 for the h631/ms631
twrp 3.1.0-0 for the h631/ms631

Hey. I flashed this rom on my friends phone. Its a metro stylo. Everything works but cellular data. Any fix for this?

Support for H635?
This is just for the US model, right? Not for the international H635?

LOS 14.1
Stonkers said:
Hey. I flashed this rom on my friends phone. Its a metro stylo. Everything works but cellular data. Any fix for this?
Click to expand...
Click to collapse
Please elaborate, did you flash this with TWRP and it's all good? I'm still running KATANA and would like to get a little more current.
Thanks!

barguybrady said:
Please elaborate, did you flash this with TWRP and it's all good? I'm still running KATANA and would like to get a little more current.
Thanks!
Click to expand...
Click to collapse
I flashed los 14 with twrp 3.1. cellular data would not work so i restored a backup. Now bluetooth, netflix and youtube wont work in katana rom. Trying to downgrade twrp and flash metro partitions to see if i can get it working.

Any updates on this rom?
Stonkers said:
I flashed los 14 with twrp 3.1. cellular data would not work so i restored a backup. Now bluetooth, netflix and youtube wont work in katana rom. Trying to downgrade twrp and flash metro partitions to see if i can get it working.
Click to expand...
Click to collapse
any updates on this ROM?

whoshotjr2006 said:
Not sure if you guys are seeing this over on androidforums so im posting it here too
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
************************************* Start of dev info***************************************************
kernel sources based off of v20k: https://github.com/touchpro/android_kernel_lge_stock-v20k
all the device and vendor trees are based off of teamregular's work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos13
g4stylus-common: https://github.com/touchpro/android_device_lge_g4stylus-common
vendor: https://github.com/touchpro/android_vendor_lge
also you need a few modded hardware/qcom folders, until the kernel gets updated to play nice with caf sources:
audio-caf: https://github.com/touchpro/android_hardware_qcom_audio-caf
display-caf: https://github.com/touchpro/android_hardware_qcom_display-caf
******************************************End of dev info***************************************************
I would recommend using my TWRP here to flash it: http://androidforums.com/threads/update-twrp-3-0-3-0-built-from-source-2-18-17.1103219/
what I know works:
display
touchscreen
vibration
ril (calling and texting. i cant test data since i dont have a data plan atm)
wifi
buttons
adb
mtp
panel backlight brightness adjustment
camera
video recording
internal storage
external_SD
sound
bluetooth (file transfer, audio)
youtube/netflix (any others i didnt test but i bet they work)
wired headset sound and microphone
microphone
gps/location services
compass
rotation
flashlight and camera flash
nfc (dunno what works and what doesnt, dont have another nfc device or android pay)
notification led
what doesnt work:
double tap to wake
data (manual network selection now works, im getting closer)
maybe some other things
The rom zip:
https://www.androidfilehost.com/?fid=673368273298938085
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 6.0)
THIS DOESNT COME WITH SU AND THE ONLY WORKING SU I FOUND IS SUPERSU!
Download it here: http://www.supersu.com/download
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hey! Why was the "android_device_lge_g4stylus-common" included to build the ROM for h631?

Rotation doesn't work, after flash the rom it work but after a few minutes the rotation not work anymore, is there any fix?

whoshotjr2006 said:
what doesnt work:
double tap to wake
data (manual network selection now works, im getting closer)
maybe some other things
Click to expand...
Click to collapse
Hey, thanks for working on this. I'm trying to get away from Metro stock ROM, but the phone is my entire Internet connection so of course I need data Does that mean it's working for you in your local kit but not in what you uploaded? Either way, I tried manual network selection and it said "registering on MetroPCS" (or equivalent, that was last night so I don't recall precisely) for about 20-30 seconds, then it very briefly flashed a scarcely-readable error message, then bumped it with a message indicating it successfully joined. But I never get a 4G or any similar symbol in the status bar, or any data, so I wondered if there's something I can do, either to force it into submission or to help you out. Thanks again

[ROM] [UNOFFICIAL] LineageOS 13 for Life One X2-Mini [Discontinued]

LineageOS 13 for Life One X2 Mini​
This Rom was ported from the Unofficial LineageOS 13 for the Yureka Black. First I need to give credit for all the hard work the developers put into their Rom, I only modified it to work on the Blu Life One X2 Mini.
Note: Please remember I'm doing this on my own time and using my own money to cover expenses.
What Works:
(please let me know)
Camera
Fingerprint
SIM
Data
GPS
Audio
Video Playback
Sensors
Led
Not Working Yet:
(Please let me know)
FM Radio
Bluetooth
Latest Build: https://drive.google.com/open?id=0BzMHnGbQH3bheWVUNlFDNjljcEE
Builds: https://drive.google.com/drive/folders/0BzMHnGbQH3bhRXNUWi1jaGhDR3M?usp=sharing (list view recommended)
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel:
Gapps: http://opengapps.org

Screenshots:

Changelog

Troubleshooting
Encryption Unsuccessful Screen:
Boot into TWRP and format Data (not wipe)

reserved 4

OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.

debianmain1 said:
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
Click to expand...
Click to collapse
Boot into TWRP and format Data (not wipe)

srgrusso said:
Boot into TWRP and format Data (not wipe)
Click to expand...
Click to collapse
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
edit:
sorry spoke too soon.
Just looked at fstab.qcom in boot.img and it is not set to "forceencrypt"

mrmazak said:
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
Click to expand...
Click to collapse
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks

OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00

srgrusso said:
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
Click to expand...
Click to collapse
I added an edit to my earlier post.
The way it is looks ok.
It can be encrypted, (encryptable=footer) but not being forced to be. (forceencrypt=)
The length and location of the encryption key would be important to get right, if force is used.

debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
if your ready to do some more testing I should be able to get wifi working.

debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)

mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in bin to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.

srgrusso said:
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in etc to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
Click to expand...
Click to collapse
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.

mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.

vampirefo said:
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
Click to expand...
Click to collapse
So I would guess that will close the Wi-Fi & Bluetooth issues at the same time.

debianmain1 said:
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
Click to expand...
Click to collapse
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks

srgrusso said:
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
Click to expand...
Click to collapse
No problem---I also contacted the other guy that is interested in helping---should hear from him soon. Will download the new one & be ready for tomorrow.

Here is the new build. Hopefully it fixes Wifi.
https://drive.google.com/file/d/0BzMHnGbQH3bhenZNVE5MeEttVFk/view?usp=sharing

[HOW-TO] Install Android 10 on HTC U11+

hey guys want to write this guide to show you steps and fixes to get Android 10 working good on our dead htc u11+ (working with both QuackPhh and Havoc releases from treble project)
1. flash stock PIE rom, you can find it here: https://androidfilehost.com/?w=search&s=2Q4DIMG you must flash it from download mode by placing the .zip inside SD card after preparing it with RUU Decryption Tool.
2. install TWRP (this version: https://github.com/sabpprook/androi...es/download/0.0.1/twrp-3.3.1-0-ocm_190501.img ) with fastboot using this command: fastboot flash recovery XXX.img (where XXX.img is name of twrp image you just downloaded)
3. inside TWRP wipe data, system, dalvik cache
4. download Havoc 3.5 rom here: https://sourceforge.net/projects/ha...ficial-arm64-aonly-gapps-nosu.img.xz/download (if you want to choose another rom you can, just check is variant ARM64 A-Only) then place it on SD card and flash from TWRP (don't reboot)
5. download PhhMagisk here: https://drive.google.com/file/d/1ZgYuaN-sklg0ycDue08WtKsMFmzWsI6F/view (standard magisk won't work) then place it on SD card and flash from TWRP (don't reboot)
6. inside TWRP go to wipe -> system -> resize file system (do this 2 times as at first try you will get error)
7. reboot
8. rom is now booting and working.
FIXES:
-for better camera quality i suggest you to download this GCam version: https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.3.018_Urnyx05-v1.7-fix.apk and then go to Phh Treble Settings -> Qualcomm features and tick Use alternate camera profile (this will make phone recording video at correct quality 1080p/4k)
-to make earpiece audio during call and bluetooth multimedia audio working you must place the 3 files included in htc_audio_bt_fix.rar i attached inside /root/vendor/etc and be sure to set permissions properly (look how permissions are set in original files before replacing, you can use Root Explorer or any other file browser with root support that allow to check and edit permissions) then you must disable from the paired bluetooth device Call Audio
now you have a working android 10 htc u11+ :victory::victory: i am using it as daily rom... you will love android 10!
only bugs i faced at the moment are:
- bluetooth audio not working with calls
- some rare freezes after unlocking phone from lockscreen

I keep getting stuck on ROM loading screen, I try reflashing the havoc os system image, then PhhMagisk, but still no luck!
I had to follow this guide all the way from the start and got the phone to boot, but once I copied the htc_audio_bt_fix.rar files to /vendor/etc/ and edited its permissions and rebooted the phone and stuck at the loading screen all over again :/

Now I have the phone running but no luck with any sound on my bluetooth earphones
I have placed the rar files as stated and the permissions are exactly as the files before had them rw--r--r, for all 3 of them.
Does the quack build support Bluetooth audio calls? I don't want to go back to pie, anyone know a working GSI Android 10 for the U11+ with BT call support?

Slok 00 said:
hey guys want to write this guide to show you steps and fixes to get Android 10 working good on our dead htc u11+ (working with both QuackPhh and Havoc releases from treble project)
1. flash stock PIE rom, you can find it here: https://androidfilehost.com/?w=search&s=2Q4DIMG you must flash it from download mode by placing the .zip inside SD card after preparing it with RUU Decryption Tool.
2. install TWRP (this version: https://github.com/sabpprook/androi...es/download/0.0.1/twrp-3.3.1-0-ocm_190501.img ) with fastboot using this command: fastboot flash recovery XXX.img (where XXX.img is name of twrp image you just downloaded)
3. inside TWRP wipe data, system, dalvik cache
4. download Havoc 3.5 rom here: https://sourceforge.net/projects/ha...ficial-arm64-aonly-gapps-nosu.img.xz/download (if you want to choose another rom you can, just check is variant ARM64 A-Only) then place it on SD card and flash from TWRP (don't reboot)
5. download PhhMagisk here: https://drive.google.com/file/d/1ZgYuaN-sklg0ycDue08WtKsMFmzWsI6F/view (standard magisk won't work) then place it on SD card and flash from TWRP (don't reboot)
6. inside TWRP go to wipe -> system -> resize file system (do this 2 times as at first try you will get error)
7. reboot
8. rom is now booting and working.
FIXES:
-for better camera quality i suggest you to download this GCam version: https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.3.018_Urnyx05-v1.7-fix.apk and then go to Phh Treble Settings -> Qualcomm features and tick Use alternate camera profile (this will make phone recording video at correct quality 1080p/4k)
-to make earpiece audio during call and bluetooth multimedia audio working you must place the 3 files included in htc_audio_bt_fix.rar i attached inside /root/vendor/etc and be sure to set permissions properly (look how permissions are set in original files before replacing, you can use Root Explorer or any other file browser with root support that allow to check and edit permissions) then you must disable from the paired bluetooth device Call Audio
now you have a working android 10 htc u11+ :victory::victory: i am using it as daily rom... you will love android 10!
only bugs i faced at the moment are:
- bluetooth audio not working with calls
- some rare freezes after unlocking phone from lockscreen
Click to expand...
Click to collapse
So I have asked at the relevant threads regarding any word on when a bluetooth fix should be expected, but do you by any chance have any idea about that?
Because I have to decide whether to wait (if the fix maybe right around the corner or smth) or revert back to a stable pie build.

usmantahir said:
So I have asked at the relevant threads regarding any word on when a bluetooth fix should be expected, but do you by any chance have any idea about that?
Because I have to decide whether to wait (if the fix maybe right around the corner or smth) or revert back to a stable pie build.
Click to expand...
Click to collapse
unfortunately bt call audio isn't working atm only multimedia audio works... try playing with bluetooth workaround option inside treeble settings-> misc but i don't know if you will solve it

Slok 00 said:
unfortunately bt call audio isn't working atm only multimedia audio works... try playing with bluetooth workaround option inside treeble settings-> misc but i don't know if you will solve it
Click to expand...
Click to collapse
That's a bummer, I guess I'll revert to pie, i tried flashing Havoc (pie) to my phone for a change, it just wont flash. Error 255. It's been a day of disappointments :crying:

usmantahir said:
That's a bummer, I guess I'll revert to pie, i tried flashing Havoc (pie) to my phone for a change, it just wont flash. Error 255. It's been a day of disappointments :crying:
Click to expand...
Click to collapse
man i am using havoc 3.5 and i am loving it, far better than pie htc rom that is too old now

Slok 00 said:
man i am using havoc 3.5 and i am loving it, far better than pie htc rom that is too old now
Click to expand...
Click to collapse
It really is great! Too bad about the Bluetooth bug! I spend hours on-call, and I just cant go back to holding my phone to my ear :/

usmantahir said:
It really is great! Too bad about the Bluetooth bug! I spend hours on-call, and I just cant go back to holding my phone to my ear :/
Click to expand...
Click to collapse
yes i got your point, try contact phhusson (quack phh creator) is a very good guy maybe it can help you

Slok 00 said:
yes i got your point, try contact phhusson (quack phh creator) is a very good guy maybe it can help you
Click to expand...
Click to collapse
Great idea! I'll find him and hit him up. I'll post here and let you guys know if it works for me.

Hey, this is great news for me, but there's one, very important question - is there a way to use Edge Sense with this? I've seen some Magisk module re-activating the analogue feature on modded Pixels, but I haven't seen anything like that for HTC - could that work? I use Edge Sense regularly and losing it would stop me from any modding.

I downloaded the stock PIE rom from the URL provided by you, and decrypt it by RUU Decryption Tool. And now I got some img files inside two folders - firmware and system.
But then how to convert them into zip file so that I can place it inside SD card? Can you tell me in details? Sorry I'm a newbie in flashing roms.

openopentw said:
I downloaded the stock PIE rom from the URL provided by you, and decrypt it by RUU Decryption Tool. And now I got some img files inside two folders - firmware and system.
But then how to convert them into zip file so that I can place it inside SD card? Can you tell me in details? Sorry I'm a newbie in flashing roms.
Click to expand...
Click to collapse
I flashed the boot.img and system.img by fastboot into my phone instead of placing some zip into SD card, and followed the remaining steps including fixes. Now my phone is working!
However my phone can not recognize if I have plugged in the earphone or not, and of course no sound from earphone. Do you guys have any suggestions about it? Maybe I should flashed vendor.img in the first step as well?

openopentw said:
I flashed the boot.img and system.img by fastboot into my phone instead of placing some zip into SD card, and followed the remaining steps including fixes. Now my phone is working!
However my phone can not recognize if I have plugged in the earphone or not, and of course no sound from earphone. Do you guys have any suggestions about it? Maybe I should flashed vendor.img in the first step as well?
Click to expand...
Click to collapse
Flashing the vendor.img would change nothing, it is the same as it was before. The fix for earphone audio has been in the post for a long time, but there is no fix for using earphones/headphones.
Did you find the earpiece speaker fix?
---------- Post added at 03:52 PM ---------- Previous post was at 03:46 PM ----------
This is incredible, I've been following phhuson's Treble GSI development for 2 years now hoping that someone would find a fix for the earpiece speaker during calls.
I tried doing everything at once and got a bootloop, but then I tried every step separately and after a few days my U11+ is working great!
How long did it take you to find that GCam port? I've been using Arnova's for ages and could never find a good one for the U11+ before trying the one you've linked.
I'm really glad we got the earpiece fix, the U11+ still has really great hardware and the poorly made Android Pie port and old security patch was tempting me to upgrade to something new. Now I think I can hold onto it for an extra year.

My camera doesn't work...
After enable "Use alternate camera profile" then reboot , it still not working....
Is there any solution?
Please help me , camera is really important to me...

Pineapplemilk said:
My camera doesn't work...
After enable "Use alternate camera profile" then reboot , it still not working....
Is there any solution?
Please help me , camera is really important to me...
Click to expand...
Click to collapse
What's your vendor version?
I use Android Pie vendor with Havoc OS 3.7 work fine.
Maybe you should flash Pie RUU first then install the Havoc OS.
---------- Post added at 10:51 PM ---------- Previous post was at 10:41 PM ----------
Here is the way to use Edge Sense with Havoc OS.
1. Install com.htc.sense.edgesensorservice.apk (Resigned with Havoc OS keystore)
2. Install App Systemizer in Magisk
3. Systemize EdgeSensorService
4. Reboot
Now Edge Sense work fine.
And if you want to setup Edge Sense, open terminal
Code:
su
am start com.htc.sense.edgesensorservice/.ui.SettingsMainActivity
Recommended to use Edge Sense Plus to manage it so you don't need to setup in this dirty(?) way every time.

james35022000 said:
What's your vendor version?
I use Android Pie vendor with Havoc OS 3.7 work fine.
Maybe you should flash Pie RUU first then install the Havoc OS.
Click to expand...
Click to collapse
I flashed 2.15.709.1 Pie Ruu before install the "Phh AOSP Android 10"
(Havoc based on Phh)
TWRP Version : 190501
And it still can't encrypt data

Pineapplemilk said:
I flashed 2.15.709.1 Pie Ruu before install the "Phh AOSP Android 10"
(Havoc based on Phh)
TWRP Version : 190501
And it still can't encrypt data
Click to expand...
Click to collapse
Oh TWRP can't decrypt data is normal.
The thing you can do is to prevent system from encrypting data.
This thread:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Just wipe data in TWRP and flash the zip file upon
---------------------------------------------------------------------
And wait, I see XDDD
I flashed Phh AOSP before, the camera don't work neither.
You can find the issue on the Phh's github, it seems never work and no fix for our device.
So....please use Havoc OS

james35022000 said:
Oh TWRP can't decrypt data is normal.
The thing you can do is to prevent system from encrypting data.
This thread:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Just wipe data in TWRP and flash the zip file upon
Click to expand...
Click to collapse
Thank you for this information :good:
---------------------------------------------------------------------
james35022000 said:
And wait, I see XDDD
I flashed Phh AOSP before, the camera don't work neither.
You can find the issue on the Phh's github, it seems never work and no fix for our device.
So....please use Havoc OS
Click to expand...
Click to collapse
Really strange.....
Thank you for the information again~
Does Havoc os running smooth on U11+?
Phh AOSP has some bugs but it's smooth tho.

Pineapplemilk said:
Does Havoc os running smooth on U11+?
Phh AOSP has some bugs but it's smooth tho.
Click to expand...
Click to collapse
It runs smooth for me, but for the first week I kept crashing at the lock screen randomly and had to do a reset. Sometimes a normal reset would just bootloop or crash on the lockscreen again. So I had to specifically go into download mode -> bootloader mode -> recovery mode (TWRP) -> "reboot to system" which would let me get past the lockscreen without crashing.
The battery life and thermal performance is MUCH better, it's too early for me to say but I think it's pretty close to Oreo battery life and heat management might be EVEN BETTER.
I still think that HTC Oreo was smoother, but most phones weren't as smooth as the U11+ on Oreo.
The camera performance is definitely worse though, that could just be because we're forced to use the GCam port instead of the stock HTC app but it's inconsistent with lighting and sometimes crushes black levels on people's faces too much. If I find improved settings or a better GCam port then I'll link it here for you guys to use
I'm pretty sure that TWRP not being able to decrypt data is a bug with that specific version of TWRP, but I don't think there's another TWRP image that will work on the U11+ so we have to deal with it.
---------- Post added at 07:24 PM ---------- Previous post was at 07:12 PM ----------
james35022000 said:
What's your vendor version?
I use Android Pie vendor with Havoc OS 3.7 work fine.
Maybe you should flash Pie RUU first then install the Havoc OS.
---------- Post added at 10:51 PM ---------- Previous post was at 10:41 PM ----------
Here is the way to use Edge Sense with Havoc OS.
1. Install com.htc.sense.edgesensorservice.apk (Resigned with Havoc OS keystore)
2. Install App Systemizer in Magisk
3. Systemize EdgeSensorService
4. Reboot
Now Edge Sense work fine.
And if you want to setup Edge Sense, open terminal
Code:
su
am start com.htc.sense.edgesensorservice/.ui.SettingsMainActivity
Recommended to use Edge Sense Plus to manage it so you don't need to setup in this dirty(?) way every time.
Click to expand...
Click to collapse
How do you do step 1? I couldn't find any information about where to find the HavocOS Keystore or what it is? I assume it's an app to resign APKs for HavocOS?
Thanks for helping an ignorant person like me

[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