Develop Bugs

Lineage OS 15.0 Dev Thread [DISCUSSION]

Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.

When does the development starts?
I don't know the procedure of ROM development. Are devs waiting for the oreo update from HTC?

Some devs already work on Oreo aosp, but it's not that easy to get it working on the 10 so that everything works. Maybe even stock will be earlier here than custom Roms like aosp and los
Sent from my HTC 10 using XDA Labs

Don't really know about LOS but AOSP based is already here...
https://forum.xda-developers.com/htc-10/development/rom-official-pure-fusion-os-oreo-t3694203/page2
P.S why is there a Dev in the Title?

Is there any news?

kingfared said:
Is there any news?
Click to expand...
Click to collapse
Lineage has a whole site with news and downloads and everything: https://www.lineageos.org/
---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------
Honestly Annoying said:
Figured we should have a thread set up for discussion, has anyone started work on this? Maybe we should get a hangouts group started.
Click to expand...
Click to collapse
You can't start a "Dev thread" if you aren't a dev on the project; you can only start a "Nag thread".

Sorry for unqualified question. I know the new site but I don't know where to find dev threads. If you can help me I'll be glad.

My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.

Ndaoud360 said:
My question is why do some older phones have LOS 15.0 and we don't yet. You'd assume the newer phones get priority. My old HTC M8 has a fully functional LOS 15.
Click to expand...
Click to collapse
That device still has an active developer working on it. crpalmer, the user who brought 14.X to HTC 10 seems to have moved on to newer devices.

hope it will have LOS15.1

Even though Raymon left development does this mean there are no los 15 for us?

As already stated by fagyi, once he solves all bugs on aosip 8.1 he will build los.

15.1 Running flawless albeit hot sometimes!
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.

heyChristo said:
Ladies and Gentleman,
I have been extremely pissed off lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
If you are so frustrated about stuff you get for free than just stay stock and stop being frustrated.......mwuhahaha funny how the world works these days......oh and by the way, you don't downgrade your kernel, you downgrade your firmware.
Cheers, have an absolutely fabulous Sunday

heyChristo said:
Ladies and Gentleman,
I have been lately at the lack of instruction that some of the devs have in their OP in regards to the kernel challenges with running back and forth between nougat and oreo. All I want for my recently required and gently used HTC 10 was a simple and pure rom that I can theme and run unhindered of bloat and unneccesary tweaks without having to gut the rom with titanium backup. With that said, in my constant frustration over the past two weeks I have been able to get Lineage os 15.1 running flawlessly on my device as of yesterday with everything working including the camera and tethering. The speaker volume is a bit low, but I can live with that.
To run this as with the other 8.0 rom you have to be on nougat kernel. IF you are already running Oreo- stock or otherwise, you will have to downgrade your kernel being s-off. Generally I don't pay for sunshine but since i got a great deal on this used phone i coughed up the $25 bucks to fix my phone after deciding I wanted to run modified oreo without having to read 1100 pages of posts.
Personally I have Sprint as a provider so I used a combination of OMJs kernel flashing instructions
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
along with this post to downgrade effectively:
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Download Rom from here:
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Now I tested this rom by flashing multiple times and I could not get any version of gapps to work but then i discovered a work around that will help. But before I get there let me explain everything I did. Some steps may be unnecessary depending on where you are coming from but i think nougat kernel is a must. I did not ruu after kernel flash.
1. Flash kernel using adb.
2. Boot straight into bootloader then Wipe and then fix persist per wonders never ceases post.
I had issues with going back to nougat kernel and had to type these instructions in the twrp terminal to get my persist back:
To fix : failed to mount '/persist' (invalid argument)
Type this in twrp terminal:
make_ext4fs /dev/block/bootdevice/by-name/persist
MAKE SURE YOU DO CLEAN WIPE all internal and format data. Fix ext4 after.
3. Resend twrp from adb.
4. Flash lineage Rom
5. Flash Magisk
6. Boot to Rom and install from Magisk G-apps systemless framework
This will not show up as being installed in magisk anymore after you install gapps. Gapps overwrites it somehow. But if you try to install gapps by itself, it will fail and crash when you boot to the rom.
7. Reboot to twrp and flash nano gapps.
8. clear cache, format data
9. profit!
Finger print scanner, Camera and everything is working. have not found any issues yet. Since I am kinda excited at getting back to LOS because i couldn't get it for my Bolt, i wanted to share with everyone else that fagyi's work is payoff.
Click to expand...
Click to collapse
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?

Musthafa-Noor said:
I'm kinda confused by what you said. Is that ROM for Oreo firmware or Nougat?
Click to expand...
Click to collapse
Nougat.

heyChristo said:
Nougat.
Click to expand...
Click to collapse
Maybe was wrong. Maybe was Oreo firmware. Switched to this and had to go the other one. Sometimes I just go into a flashing rage and can't rememember what happened after.

https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-htc-10-android-8-1/
Click to expand...
Click to collapse
I'm using that ROM build of 15.1 on my HTC 10 (Android 8.1), and it works pretty good actually. besides a few minor issues.
Unlocked Bootloader from HTCDev, Running latest TWRP Recovery, S-On (for me at least was not needed to turn this off), Latest Magisk (which seems to pass the Safetynet check) / Busybox.
I changed the Kernel afterwards to "kernel_htc_pme_aosp_tabp0le_eas_4.02-O" (from tabp0le) because it has the "performance" cpu governor that i can enable using Kernel Adiutor.
The bugs i encountered so far :
- Camera apps open slowly, except for "Open Camera" , not a big issue.
- HTC Sense Launcher doesn't seem to work, just get the famous (app has stopped) message, but maybe it's a conflict with my GAPPS installation
- Only 1 speaker works, HTC10 has Boomsound with 2 speakers on stock rom, 1 is a treble speaker, the other one is kinda like a small subwoofer for the low frequencies.
Is there any soundmod that would enable both speakers again?

There is not any mod to do that. But the dev of this ROM is working on getting the bottom speaker working.

I just saw that a new build-version is released for HTC10.
lineage-15.1-20180624-UNOFFICIAL-pme.zip

[RECOVERY][Unofficial]TWRP 3.2.3 for Nokia 3(Heart)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This TWRP Has been Compiled by Myself From Source Using My Rebased Device Tree. Flashing Works Pretty Much Well, No Lags Or Delays.
Download Link: - Click Here To Download
Flashing: - fastboot flash recovery-28032019.img
Internal showing 0 mb ?:
Format data, It Removes Encryption
Credits:
~ TeamWin
~ CM/Lineage/Omni Android
~ SevenMaxs
Kernel: Using Prebuilt Kernel
XDA:DevDB Information
Twrp, Tool/Utility for the Nokia 3
Contributors
RevanthTolety
Source Code: https://github.com/RevanthTolety/device_nokia_heart/tree/android-7.1
Version Information
Status: Stable
Stable Release Date: 2019-03-28
Created 2019-03-28
Last Updated 2019-03-28

ScreenShot

Reserved

Great! Thanks, but... How do I EXACTLY install this? I mean, with locked bootloader starting from Oreo 8.1 january patch.

Fernandus91 said:
Great! Thanks, but... How do I EXACTLY install this? I mean, with locked bootloader starting from Oreo 8.1 january patch.
Click to expand...
Click to collapse
Hey, If Bootloader is Unlocked Should be Easy to Install. And I havent Tested this Build With Oreo Yet. And i Am Sure this Build Wont Work For Oreo Yet

RevanthTolety said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This TWRP Has been Compiled by Myself From Source Using My Rebased Device Tree. Flashing Works Pretty Much Well, No Lags Or Delays.
Download Link: - Click Here To Download
Flashing: - fastboot flash recovery-28032019.img
Internal showing 0 mb ?:
Format data, It Removes Encryption
Credits:
~ TeamWin
~ CM/Lineage/Omni Android
~ SevenMaxs
Kernel: Using Prebuilt Kernel
XDA:DevDB Information
Twrp, Tool/Utility for the Nokia 3
Contributors
RevanthTolety
Source Code: https://github.com/Revanth/device_nokia_heart/tree/android-7.1
Version Information
Status: Stable
Stable Release Date: 2019-03-28
Created 2019-03-28
Last Updated 2019-03-28
Click to expand...
Click to collapse
i have installed this recovery its working fine except Mtp not showing on pc,
otg works fine and have flashed rom with.

Does this twrp work on android pie?

link broken

Bug report.
Hello developer of current TWRP for Nokia 3, i am going to report some bugs based on what i have seen and experienced, if you do see this message, please note that i am willing to become a tester for the recovery of this device, i am now going to start stating the problems, please also note that i am using Nokia 3 with Pie ROM, Bootloader unlocked, rooted with Magisk, i am using TWRP 3.2.3 from https://unofficialtwrp.com/nokia-3-root-twrp-3-2-3/, i also believe this is the same with the TWRP that @RevanthTolety made, in other words, you, let me introduce the problems to you.
i have attached the pictures of the bugs, as well as logs, to help you all regarding about this problem, i have messaged all five of you in hopes that some of you are still willing to develop a proper, working recovery for the Pie ROM of this device, or at least team up in making one, anything as long as this project will still continue or something will be done.
Bugs i have found:
1. Decrypting of data, the recovery is asking me for a password and i have no idea what to do, i have never encrypted my device, or anything, and here is what i have done so far:
1a. Formatted data through TWRP, rebooted into recovery and applied root.
1b. Wiped data through TWRP, rebooted into recovery, then applied with root.
1c. All of the above, except this time i flashed no verity opt encrypt, didn't work.
1d. Formatted data through fastboot, rebooted into recovery immediately and applied root.
For the most part, by the time i managed to format or wipe my data/userdata, i am able to gain access on it through TWRP, and the recovery isn't asking me for a password, but once i am able to fully set up my device and it reaches the home screen, not putting any screen locks, just Swipe, rebooting into recovery again, and now it asks me for a password, i tried "default_password" and "password" but it didn't work, at this moment, i can only flash zips through my MicroSD Card, the recovery doesn't have access to my internal storage and i couldn't make a backup with my userdata.
2. TWRP gets replaced with stock recovery if you do not boot into it immediately after flashing, trust me, this is where i got frustrated the most, i was about to smash the phone because of this! I still had to root to ensure that the recovery will stay, or else at next boot the stock recovery will be back.
3. Battery percentage is shown incorrectly, based on the 5 forums i've seen which is all related to porting TWRP for this phone, this error has been very consistent.
4. The recovery keeps showing me a prompt of asking whether to keep System read-only or not, even though i selected the box "Don't show me this screen again.", it still comes back anyway.
5. The recovery complains about '/hidden/emmc_hidden" not being found and all that.
6. I cannot save my language, even though i already toggled it through the settings of the recovery.
7. Touch is very slow during the first screen which is the "Keep System read-only?"
Here are the things i confirmed to be working:
MicroSD Card access
OTG access
Installing .zips
I cannot test the backup and restore option since i can't access data through it, i don't want to lose progress.
The link is broken so i couldn't test the recovery from the true source which is you, hopefully you could still provide me the recovery you actually ported to see if anything is wrong, but if the recovery i obtained from the link i provided is from yours, then please hopefully you could provide a fix for it, you are currently the latest developer for this recovery so i expect you can still do it, the device tree is also still intact and that's the reason why i still have hopes, i want to help not only myself, but also other Nokia 3 users regarding about this, please lets do something so all Nokia 3 phones with Pie ROM can enjoy a fully stable TWRP.
That's all of the bugs i have seen so far, i am going to use my friend's phone who happens to own a Nokia 3 for testing the recovery, if i still haven't received a response within 1 week i will return the cellphone, you could contact me through Telegram, Facebook and other social media sites such as Instagram, i am willing to take the risk, please contact me if you all are still willing to continue with the development of TWRP for this cellphone.

The link doesn't work
I get a 404 error when I click the link

[ROM][P900][UNOFFICIAL] LineageOS 16.0 | Android 9.0 Pie 20200821 technical preview

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!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using pico/nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Full wipe all
4. Flash firmware and gapps
Work
almost all
Known Issues
- camera
- screenshots
- missed icons in trebuchet tauncher (install nova or microsoft launcher and other)
Links
LineageOS Builds
1. 20200821: init build: https://drive.google.com/file/d/19-rPOcmlYIhcoZleG4MKRROk9TXytEOe/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official version from: https://twrp.me/samsung/samsunggalaxynotepro122exynoswifi.html
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_v1awifi
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos5420
Vendor: https://github.com/Valera1978/android_vendor_samsung_v1awifi
Thanks
Thanks to LineageOS team
Thanks to exynos5420 team for the right kernel

Thx @Valera1978 that's great news.
Gonna test today.
Edit 6h later first impressions:
Coming from Lineage 14.1 Vanilla with TWRP 3.4.0-0.
Backed up everything, full wipe plus data format.
Installing purely the ROM with TWRP 3.4.0 led to "Error 7" 3.3.1 did the trick.
Made a reboot to check if it starts.
Noticed screen failures in form of small black bars/stripes which vanished after a few seconds when I let the screen settle.
(Appearing very often even now after full installation of everything I need.)
Rebooted to TWRP and installed BiTGapps (prefer them to opengapps as they are even smaller than pico) and Magisk.
After each flash wiped cache/dalvik of course.
Installed Nova prime (dark mode) and all my other apps.
Camera doesn't work with Lineage App (as said) but does with opencamera from f-droid.
Screenshots neither but using Quickboot is a workaround when activated in its settings.
When writing text and correcting failures the magnifier shows only a white field with now text in it even when dark mode is off.
Great work @Valera1978 will carry on testing.
Edit 18h later:
Firefox seems to have problems with it, doesn't often even open its add-on page or urls.
Lightning browser has no probs.
Only one sudden reboot until now.
Edit 24h later:
Tried to upload a pic with the screen problems but didn't work.
Mostly occuring when switching from portrait to landscape (reproducible).
Because of the Firefox problems I've tried the 79 version but starting it resulted directly in a reboot (reproducible).

I'm surprised there aren't more responses
Can confirm TWRP 3.3.1 is the latest recovery to work. Doesn't seem to work with 3.1.1
Can't change wallpaper. Not sure why. I have to go to live wallpaper to get the default one back
Ok Google needs to be installed manually
I get security flags from SELinux and Public trust certificates. Probably because the release is so early
Overall it's not bad for a Pre-Alpha release.

First of all: an awesome thank you to Valera1978 since I was expecting a newer version than 14.1 a long time
Have the same issue with the wallpaper change and some flickering in the display. Installed nova prime too but can`t close all apps in task manager only each manually single (wipe up)
I am eager for the next version and improvements :fingers-crossed: and willing to give further feedback.
THX a lot for your passion

the current version is rather a technical build for testing (public, the most stable, there were already about 40-50 internal builds for fixing bugs and checking various things).
In any way - lineage 17.1 coming soon (later today), release build done, on tests right now. And I like it much more, then technical 16.0 build.

I tried 16 and I like it. Looking forward to 17.1. Thanks for saving the P900 from an early grave you are and have been the best ?

i will try this process for the first time. Is there a video tutorial? thank you.

kayamece said:
i will try this process for the first time. Is there a video tutorial? thank you.
Click to expand...
Click to collapse
This ROM will probably not be in development any further as the brilliant dev @Valera1978 is already working on a 17.1.
About a video I don't know. Searching in YouTube might help finding out
Here is a very good description which I followed from @thompatry who's ROM is very stable, has a working camera (skype) and gets regularly updated.
[ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi)
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.* (Nougat), which is designed to increase performance and reliability over stock Android for your device. #include /* * Your...
forum.xda-developers.com
Download it to SD.
As he quoted install a TWRP first to exchange the stock recovery.
Easiest to do is use a windows PC with Odin version 3.13.
Battery fully loaded before starting.
1.Download TWRP 3.3.1 for v1awifi from twrp.me but choose the tar version and save it in Odin folder.
2.Get P900 into download mode (turn it off, then press buttons Pwr, home, vol- altogether).
Will give you a warning but continue with vol+.
3.Start Odin then connect P900 to PC and check in Odin if a field on the left turns blue (com+).
4.Uncheck "auto reboot" in Odin.
5.Flash TWRP 3.3.1 with Odin onto P900 putting the downloaded TWRP file in "AP" field in Odin.
When Odin says "Pass" all is fine.
6.Turn P900 off with pwr button but press afterwards directly home and Vol+ together as it automatically reboots.
Then you access the new recovery.
If you fail the Samsung recovery gets reborn and you have to repeat steps 2-6 again but that does no harm.
Save all what is possible with TWRP to external SD using Backup.
Then wipe everything in TWRP (except SD ), select "format data" after that.
Select install and choose the ROM from SD.
Test if system starts. Might take a while.
If you want to use Google apps, download Gapps from opengapps (choose ARM, 7.1 and pico) and save it in advance to SD.
If system starts, turn it off, restart to recovery (pwr, home, vol+) and install Gapps.

bmwdroid said:
Easiest to do is use a windows PC with Odin version 3.13.
Battery fully loaded before starting.
1.Download TWRP 3.3.1 for v1awifi from twrp.me but choose the tar version and save it in Odin folder.
2.Get P900 into download mode (turn it off, then press buttons Pwr, home, vol- altogether).
Will give you a warning but continue with vol+.
3.Start Odin then connect P900 to PC and check in Odin if a field on the left turns blue (com+).
4.Uncheck "auto reboot" in Odin.
5.Flash TWRP 3.3.1 with Odin onto P900 putting the downloaded TWRP file in "AP" field in Odin.
When Odin says "Pass" all is fine.
6.Turn P900 off with pwr button but press afterwards directly home and Vol+ together as it automatically reboots.
Then you access the new recovery.
If you fail the Samsung recovery gets reborn and you have to repeat steps 2-6 again but that does no harm.
Save all what is possible with TWRP to external SD using Backup.
Then wipe everything in TWRP (except SD ), select "format data" after that.
Select install and choose the ROM from SD.
Test if system starts. Might take a while.
If you want to use Google apps, download Gapps from opengapps (choose ARM, 7.1 and pico) and save it in advance to SD.
If system starts, turn it off, restart to recovery (pwr, home, vol+) and install Gapps.
Click to expand...
Click to collapse
Hi everyone, I hope you are all safe and well.
Just a quick question, do I use the latest version of TWRP for my P900 (note pro 12.2 wi-fi). There are versions on the website which are later than the 3.3.1 version in this post. At the moment my version is 1.22, so this is really old! This was obviously installed and I did the flash to 14.1.
Like I say, at the moment, I am using LineageOS 14.1 with an old security patch level (September 19) because I cannot seem to update it. I have tried the auto update, this fails and I have also tried to manually apply but this also does not work.
I was wondering whether it was time to upgrade to version 16 or 17.
I'm not an expert on this by any means and I recall I did struggle with some error message when trying to update to I think at the time line Lineage 15.
Any comments or suggestions would be much appreciated.

@mattgod69 auto updater I don't use/like at all.
My suggestion is download TWRP 2.8.7-0 as zip and flash this with your TWRP. It is the latest zip released.
From that on it can use img files and you can update further to 3.3.1 or higher.
For me 3.4.0 was needed to flash @Valera1978 LOS17.1.
3.3.1-0 for LOS14.1 by @thompatry which's Vanilla (version 20201215) I use for here camera is working instead of being on LOS17.1.

Thanks for the reply @bmwdroid, i was talking about the app which is version 1.2 (doh)... i have just booted into TWRP and i have version 3.3.1. So if you are using the same tablet as me, what would you upgrade to or would you leave it as is. Also, do you think i need to update the security patch level? Cheers and apologies if these are silly questions.

mattgod69 said:
Thanks for the reply @bmwdroid, i was talking about the app which is version 1.2 (doh)... i have just booted into TWRP and i have version 3.3.1. So if you are using the same tablet as me, what would you upgrade to or would you leave it as is. Also, do you think i need to update the security patch level? Cheers and apologies if these are silly questions.
Click to expand...
Click to collapse
Mine is a P900 v1awifi.
I suppose that the app 1.2 refers to the TWRP app which I don't use and I've always read warnings to install it so I never did.
It is said that it sometimes causes problems when flashing.
And imo it's not needed anyhow.
If you need camera working for skype or else I recommend to flash the latest LOS14,1 mentioned above.
https://download.exynos5420.com/LineageOS-14.1-Deathly/v1awifi/
with the deathly adiutor built in
or
https://download.exynos5420.com/LineageOS-14.1-Vanilla/v1awifi/
which is a plain android system
The development of this LOS16 seems suspended as the dev is already working on LOS17.1 which I've tested, but as said has no working camera.
Therefore I can't say much about its stabilty but it worked with Bitgapps and Magisk for 4-5 hours until I switched back to LOS14.1.
If you want to test it: I had to upgrade TWRP to 3.4.0 to avoid "Error 7".
To go back to 14.1 I had to downgrade to 3.3.1 first.
Questions show that someone is willing to learn which should be appreciated.

bmwdroid said:
Mine is a P900 v1awifi.
I suppose that the app 1.2 refers to the TWRP app which I don't use and I've always read warnings to install it so I never did.
It is said that it sometimes causes problems when flashing.
And imo it's not needed anyhow.
If you need camera working for skype or else I recommend to flash the latest LOS14,1 mentioned above.
https://download.exynos5420.com/LineageOS-14.1-Deathly/v1awifi/
with the deathly adiutor built in
or
https://download.exynos5420.com/LineageOS-14.1-Vanilla/v1awifi/
which is a plain android system
The development of this LOS16 seems suspended as the dev is already working on LOS17.1 which I've tested, but as said has no working camera.
Therefore I can't say much about its stabilty but it worked with Bitgapps and Magisk for 4-5 hours until I switched back to LOS14.1.
If you want to test it: I had to upgrade TWRP to 3.4.0 to avoid "Error 7".
To go back to 14.1 I had to downgrade to 3.3.1 first.
Questions show that someone is willing to learn which should be appreciated.
Click to expand...
Click to collapse
Thank you for the detailed response, very helpful.
I dont really use the camera with my tablet, but i might, so its probably best to wait til 17.1 is working. The tablet is really just a browsing device i use beside my bed, its not an everyday machine.. so i am willing to try new things and play about with it.... it also does not matter if it is wiped accidentally etc.
i have to say it has been overall much better with 14.1 installed, far better than the stock OS. It is faster and more responsive.
Presumably I need new google apps etc download any new OS? If i install the latest LOS 14.1 do i also need new gapps etc? Is this OS much better than the one i have?
I do not know what Bitgapps and Magisk are?
Many thanks for all your help.... this community is great because even though i have done this a couple of times on different devices, there are long time gaps between doing it and it is still quite scary because i dont want to brick the device!

Just looked at Magisk... is it not a good idea to have this in any event? it looks like this would be earier to install later OS like LOS17.12? Is this right?

@mattgod69 BitGapps are an even smaller Google Apps version than Opengapps pico.
I use them on Android Q, as opengapps weren't working properly at that time being.
I don't use Google TTS and always had to block it when using opengapps.
Magisk is an equivalent to SU which is no longer continued.
It's neede for all apps needing root like AFWall, DeviceInfo and many others.
If you or your tab are happy without there's no need flashing it.
It causes no probs when switching ROMs as long as it's a clean flash.
Even updating ROMs dirty works on mine.
If you already had LOS14.1 installed and google apps as well you don't need a newer gapps version when updating dirty as gapps get updated by Google itself.
When flashing cleanly I recommend a newer gapps version but you can use any old (designed for the specific android version) as well.
Only setting up might take longer as the gapps will be updated automatically as soon as they find an internet connection.
The newer version of LOS14.1 will imo only be different in patch level nothing else.
Hope I didn't overlook a question.

bmwdroid said:
@mattgod69 BitGapps are an even smaller Google Apps version than Opengapps pico.
I use them on Android Q, as opengapps weren't working properly at that time being.
I don't use Google TTS and always had to block it when using opengapps.
Magisk is an equivalent to SU which is no longer continued.
It's neede for all apps needing root like AFWall, DeviceInfo and many others.
If you or your tab are happy without there's no need flashing it.
It causes no probs when switching ROMs as long as it's a clean flash.
Even updating ROMs dirty works on mine.
If you already had LOS14.1 installed and google apps as well you don't need a newer gapps version when updating dirty as gapps get updated by Google itself.
When flashing cleanly I recommend a newer gapps version but you can use any old (designed for the specific android version) as well.
Only setting up might take longer as the gapps will be updated automatically as soon as they find an internet connection.
The newer version of LOS14.1 will imo only be different in patch level nothing else.
Hope I didn't overlook a question.
Click to expand...
Click to collapse
Many thanks for the message and info. i think maybe i will leave as is for a bit as the tablet is working fine at the moment.... look at this again when 17.1 is ready.....

mattgod69 said:
Many thanks for the message and info. i think maybe i will leave as is for a bit as the tablet is working fine at the moment.... look at this again when 17.1 is ready.....
Click to expand...
Click to collapse
But I hope you will be updating the ROM to be on the latest patch level.

bmwdroid said:
But I hope you will be updating the ROM to be on the latest patch level.
Click to expand...
Click to collapse
ok, i will update with the lastest 14.1 OS.... is there a step by step guide for this on here....?

bmwdroid said:
But I hope you will be updating the ROM to be on the latest patch level.
Click to expand...
Click to collapse
i think i am going to try 17.1... i think most issues have been sorted now?
i did have some questions before i do this which i have put in another post.....
Also, how do you do a dirty install... is this where the cache etc is not wiped?
would you update TWRP to 3.5.0. (the latest one). I assume this can be done from the program in recovery mode?
Many thanks for your help and advice.

mattgod69 said:
.... would you update TWRP to 3.5.0. (the latest one). I assume this can be done from the program in recovery mode?...
Click to expand...
Click to collapse
Updating TWRP can be done with itself.
Working up- and downwards.
Just select "install" switch to "image" choose the file and select "recovery".
Afterwards reboot directly into the new recovery.

[ROM][10] Lineageos 17.1 [Official] Pixel 3a "Sargo"

Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org

Horninho10 said:
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
Yes, it runs nice and smooth, I was recently on LOS.

The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?

pojr said:
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
Click to expand...
Click to collapse
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.

MoistPicklez said:
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
Click to expand...
Click to collapse
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10

pojr said:
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
Click to expand...
Click to collapse
Test it out if you're interested, but A11 ROMs are likely around the corner. I bet we'll get a build or two of something else down the road. Cheers!

I've personally had GPS issues (while using OpenGapps Pico) with the official release. Hoping A11 builds fix it.

Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).

I seem to have overcome my GPS woes! My installation process was the following:
Install the last Android Q factory image
Flash LOS boot, go to recovery
Factory reset
Install update > adb sideload LOS zip
Very important(?) - go back to main menu, advanced, reboot to recovery
Install update > adb sideload opengapps pico zip > yes, install anyway
Sign in to your Google account during the initial setup process
Test GPS with an app (Google Maps, Waze, OSMAnd, Pokémon Go... )
The only issue I seem to have now is that the Google Fi app doesn't seem to get that my Fi service is ESIM based, and prompts me to order a physical SIM card, but playing with the mobile service settings seems to have gotten my service set up anyway.
EDIT: After talking with Google Fi support, going to Settings > System > Reset Options > Reset Wi-Fi, mobile & Bluetooth, check erase downloaded SIMs, then trying to activate Google Fi again in the app, it worked.

In addition to the helpful tips from @Mokura3rd. My two cents: I had some gps issues as well, but didn't test it to great extent. Here's a description of my (rather weird issue):
When I first installed Lineageos (jan16 - my previous comment), Google maps and Gps status were able to find gps signal (and quicky), but strava didn't find any gps signal (it didn't even ask for permission, which I granted manually - to no avail).
Some time after the first OTA update, I checked strava again. And it worked without issue. So there might have been merged some bugfixes that fixed gps issues on recent builds.

guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?

pojr said:
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
Click to expand...
Click to collapse
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.

MoistPicklez said:
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
Click to expand...
Click to collapse
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"

pojr said:
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
Click to expand...
Click to collapse
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)

MoistPicklez said:
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
Click to expand...
Click to collapse
did not realize we got a new twrp version. thats a step in the right direction. with that said, that info is good to know. i'm a lazy ass and prolly not gonna test out lineage os until it gets on 11 lmao.

For whoever needs it. I sure did after a derped update last week!
tl;dr install update, disable all modules before booting, get the latest recovery image and patch it, install with fastboot. long version below, just in case.
How To OTA With Magisk, Painlessly:
Open updater and download the OTA.
Press install and let it do its thing, but DON'T REBOOT YET.
Go to Magisk and disable all your modules.
Okay, you can reboot now. It might take longer than usual, it's a system update.
Open Magisk and note that it's no longer installed, don't panic.
Download the recovery image matching your update from here: https://download.lineageos.org/sargo
Open Magisk and patch the img you just downloaded.
Copy the magisk_patched_(random).img to a folder on your computer where you're able to access fastboot.
Reboot your phone to bootloader: either by the advanced power menu, enabled in developer settings, or by restarting and holding Volume Down while the phone boots up.
Open up your terminal/commandline/etc where you moved the image file.
Type the command "fastboot flash boot magisk_patched_*****.img", where the last part is the random string that got generated in the patching process. Press Enter.
After the command finishes, use the volume keys to scroll through the bootloader menu until you see "Start". Press the power button.
Your phone should reboot back to the OS, you can now go back to Magisk and re-enable your modules at your leisure.

So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##

harryharryharry said:
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
Click to expand...
Click to collapse
Just go into app settings and kill now & disable. I noticed that if you installl gapps, get rooted, setup the phone you prefer. Backup with google backup....use the lineage recovery to do a factory reinstall. Once you recover all the sim issues, installation issues simply stop.

nylar357 said:
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
Click to expand...
Click to collapse
The kernel issues might be because they're targeted toward Android 11, and LOS 17.1 is based on Android 10.

harryharryharry said:
[...] First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). [...]
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications.[...]
Click to expand...
Click to collapse
It happened to me the same way. I am in the German T-Mobile network. I also disabled 'SIM Manager'.
Unfortunately, I do not receive any 'missed call'-SMS in case the mobile phone was in flight mode.
I think the app could have something to do with it because everything fits on the ISP side. So far, I haven't found an option to reactivate the App in the settings. Apparently it's some kind of hidden app. Can someone help please?
EDIT: There is a "hidden" "System-apps" option in the app settings. Unfortunately the error still occurs.

OmniROM stuck at boot animation load screen

Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!

nutsnax said:
Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Weekly builds may be unstable. I'm actually curious on how you got a hold of such build for the this device. Most, if not all ROMs are unofficial for the stylus and updates for each rom varies by contributed developers.....
However, you say you're decent with Linux. I'm sure there's some developers here that would help you with various tools to learn on how to make your own version of any type of OS.
As for OmniRom, I'd probably ask @vache for some help, for he has his own unofficial version.
Also, I recommend that you have the latest platform tools and the moto software tool if you don't have these yet...

nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!

nutsnax said:
nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!
Click to expand...
Click to collapse
That's good you got it to work. One developer once told me, when all else fails, think outside of the box. You'll eventually get it to work somehow

I have your solution cuz I went through the same thing.. you have to start out with stock Android 10 so you have to be bootloader unlocked and rooted that way you can downgrade your software and it's only the super images that you have to downgrade.. so just flash your supers and you'll be fine but they have to be stock Android 10 it doesn't matter what firmware version because you're keeping the same modem file