[OFFICIAL] LineageOS 20 for the Google Pixel 2 XL
- Thread starter npjohnson
- Start date
No, we don't do anything to spoof safety net as per LineageOS's charter requirements.
Use Magisk or something to do so, but I can't support that use case.
That's interesting, some people are having stutter and some like me not. I wonder what we have done that's different. I'm not rooted, and believe in the simpler/basic the rom the less things can break, clean installed the unofficial. If you can take logs and send them to dev to look at, so it can be pin pointed and sorted
I am having stutters as well with official release, other than that excellent. Bluetooth working good etc
I can't seem to be able to find what date is the security patch.
I can't seem to be able to find what date is the security patch.
Today I successfully installed LOS 20 and Magisk on my 2XL and the required modules to satisfy the YASNAC app and pass its SafetyNet tests.
The only problem I’m having is that this OS does not recognize my SIM cards, I’ve tried two. I saw that users of the previous unofficial versions of this 2XL LOS 20 OS mention this problem and I hope that the developer resolves this problem as soon as he can.
Last edited:
ughhhhh I thought this bug was gone - wipe data and try again. let me know.
I’m assuming that you are saying that you want me to do a factory reset/format data partition in LOS recovery? I tried doing a network reset, but that didn’t change anything.
As you said, ughhhhh! I followed your instructions, formatted data, rebooted my phone and it‘s still asking me to either insert a SIM card or download an eSIM. This problem still needs to be resolved, there’s a Google Fi SIM card inserted in the phone that had been working fine with LOS 19.1. Now that I’ve reset my phone again, if you need a volunteer to test any builds you come up with while trying to resolve this problem, please let me know.
Last edited:
Ughhhhhhh.
If you get me some logs like the wiki details on a bugticket I'll do my best.
How do I do anything like that after having done a factory reset? How would I access these logs?
You would follow the wiki guides, it talks about enabling adb and getting them.
I have adb enabled, but after looking through the four taimen Lineage wiki documents I couldn’t find anything about collecting logs. Can you please provide a link to the instructions for what you need me to do? Thanks.
Thank you, I will try to get this done tomorrow, submit the required data and get back to you. Good night.How to submit a bug report | LineageOS Wiki
wiki.lineageos.org
Here's my experiment with the first OFFICIAL build:
I know a fresh TWRP + format data + completely wipe + install OFFICIAL will work, but I don't want to install 50+ apps again for my phones.
For 2nd round testing (thanks to my cracked-screen dedicated testing Pixel 2XL):
If anyone knows a way to transit from UNOFFICIAL to OFFICIAL while retaining all user app/data, it would be appreciated if you could share your method here.
Even you are not sure your method would work out, you can still suggest it here and I can test it with my testing phone.
- Latest UNOFFICIAL build can not use OTA to upgrade to OFFICIAL Build.
- Installing UNOFFICAL build overwrite recovery: TWRP + UNOFFICIAL will become Lineage recovery + UNOFFICIAL
- Lineage recovery can not directly install *zip, it must be sideloaded with ADB (correct me if I am wrong here)
- Flash TWRP again with Lineage recovery + UNOFFICIAL will ERASE all info (UNOFFICIAL and all apps would be gone)
I know a fresh TWRP + format data + completely wipe + install OFFICIAL will work, but I don't want to install 50+ apps again for my phones.
For 2nd round testing (thanks to my cracked-screen dedicated testing Pixel 2XL):
- Clean flashed lastest UNOFFICIAL build with TWRP to reinstate the starting state above (emulate my 2 daily use phones)
- TWRP + UNOFFICIAL became Lineage recovery + UNOFFICIAL again
- Boot into Lineage recovery, and sideload OFFICIAL.zip which was succesful.
- But the phone stuck in bootloop (I think the exisitng gapps from UNOFFICIAL is causing this)
If anyone knows a way to transit from UNOFFICIAL to OFFICIAL while retaining all user app/data, it would be appreciated if you could share your method here.
Even you are not sure your method would work out, you can still suggest it here and I can test it with my testing phone.
Okay, I have created the issue on the Gitlab website and I have uploaded my logcat.txt file.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
Neither of these are helpful bug reports.
Please use the bug reports system detailed on the wiki if you have issued.2
Well, I followed your advice after first trying to install just the radio img file from the taimen factory image with fastboot. I hoped that might correct whatever the problem was with the RIL, but no such luck! So I had to do the full install of the factory image, which restored SIM detection as you said it would. I then installed the 0223 LOS 20 build and all appears to be well, my 2XL is currently running an app and data restore. I would like to know what might have caused this problem to occur in the first place so I can possibly prevent it from ever happening again!
thanks for your guidance and support!2
Same as it was before, follow the wiki, those images are mainly for debugging issues if you have them, and maintainers may ask you to use them to debug things, but really just the exact same process you're used to following2
So to the Verizon texting thing - I use Verizon - It worked for me fine on AN12 as soon as I went to AN13 nope. I can recieve them, and send in groups (MMS) but not direct SMS. I know its not cool talking about other ROMS here, but I came here to as my plan was to try 20 fro my Taimen. I have used Pixel Exp 13 and 13 +, PixelDust, and even tried EVO X. All still cannot do it - the only difference I can see is my SMSC # is "+19037029920",145 - my Pixel6 Pro, on Verizon - same SIM - uses SMSC# +19037029920 and it sends all SMS texts fine. I was hoping I could root and change a build prop? Unsure, but if any dev can use this info to try to help AN13 with Verizon it be great!2
I'm sure you are right about first installing the stock image, but this should not be necessary. Initializing the hardware correctly is one of the basic things operating systems do, or should do (I'm an old -- very old -- OS developer) very soon after coming to life. Why do we need the stock image to do this for 20/13? This hack, even if it works, does not exactly inspire confidence. I am going to reflash 19.1 and wait until 20 settles down.
Thanks very much for trying to help. -
21
Google Pixel 2 XL
Code:- Your warranty is now void. - You have been warned. - Use at your own risk.
Introduction:
This is the Official Lineage OS 20 thread for the Google Pixel 2 XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Notes:- None.
- Find any? Report them according to this guide.
Kernel Source: https://github.com/LineageOS/android_kernel_google_wahoo- The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
- Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
87
SELinux is permissive due to a single bug I need to solve.
And snapchat is safety net related. Enforcing might fix it alone.4
