[OFFICIAL] LineageOS 20 for the Google Pixel 2 XL

Search This thread
By:
Advanced…
jam456

jam456

Senior Member
Feb 3, 2014
57
27
Manchester UK
Google Pixel 2 XL
Apple iPhone 12
5dPZ said:
Here's my experiment with the first OFFICIAL build:
  • 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)
Ok, this is my first attempt to transit from UNOFFICIAL to OFFICIAL which I would call a fail because I could not keep my user data.
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)
So 2nd attempt failed again.

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.
Click to expand...
Click to collapse

There is no way to do what you want to do. the unofficial maybe lineage but has been tweaked to such an extent that you may as well consider it as a separate type of ROM. You can back up data for apps and phone and clean install the official then restore data back once apps have been re installed
 
J

justinkb

Senior Member
Sep 16, 2010
103
39
can I install the new UNOFFICIAL build from today over an OFFICIAL+MindTheGapps from last week without issue?
 
Q

Qhasu

New member
Oct 18, 2020
4
3
ieatabiscuit said:
I am clearly holding my face wrong while flashing or something. I can not get texts to send reliably since updating to android 13.
Click to expand...
Click to collapse
I too am having the same issues.

Summary of what I have tried:
Reflashed to factory rom: texting works like expected.
Flashed to LOS 19: texting works like normal.
Flashed to LOS 20: unable to send or receive texts both on LOS message app and Google Messages. For the Google Message app, I get an error message of "Can't send. This recipient's phone number can't be confirmed. Error code 0." LOS message app outputs similar error message.
 
jam456

jam456

Senior Member
Feb 3, 2014
57
27
Manchester UK
Google Pixel 2 XL
Apple iPhone 12
Qhasu said:
I too am having the same issues.

Summary of what I have tried:
Reflashed to factory rom: texting works like expected.
Flashed to LOS 19: texting works like normal.
Flashed to LOS 20: unable to send or receive texts both on LOS message app and Google Messages. For the Google Message app, I get an error message of "Can't send. This recipient's phone number can't be confirmed. Error code 0." LOS message app outputs similar error message.
Click to expand...
Click to collapse
What country? Have you checked message settings, have you tried toggling airplane mode, have you archived the text convo and tried sending the text again. Have you checked that you have the country selected in message settings is your own, have you checked it is SMS trying to be sent and not MMS.. need more info to start answering and also send logs to the devs


..the below attachment, your own should show the same with your number
 

Attachments

  • Screenshot_20230213-051345.png
    Screenshot_20230213-051345.png
    89.9 KB · Views: 24
jam456

jam456

Senior Member
Feb 3, 2014
57
27
Manchester UK
Google Pixel 2 XL
Apple iPhone 12
ieatabiscuit said:
So there's already a bug opened for LOS20 that causes some taimen devices to not read the SIM card. How best can I contribute to this aside from just being patient? Will logs from more phones with the issue help?
Click to expand...
Click to collapse
Yes, ofc the more info provided the better. I have never had the no sim/signal. I moved from official 19.1 to Los 20 unofficial, because it was stable has been my daily driver. I would love to know why some people have issues and some like me don't
 
  • Like
Reactions: ieatabiscuit
ieatabiscuit

ieatabiscuit

Senior Member
Jan 13, 2015
397
128
Milton, GA
Samsung Galaxy S8
Google Pixel 2 XL
jam456 said:
Yes, ofc the more info provided the better. I have never had the no sim/signal. I moved from official 19.1 to Los 20 unofficial, because it was stable has been my daily driver. I would love to know why some people have issues and some like me don't
Click to expand...
Click to collapse
Ok, let's abuse my phone a bit. It fails on almost any ROM as mentioned, so which version of LOS would you like me to start with? I pulled a log from a fresh clean install of official last night, what's the best way to deliver it to whomever wants to see it?
 
  • Like
Reactions: all43
You must log in or register to reply here.

Similar threads

T
[UPDATED][2017.11.6][Magisk] Root Pixel 2 (XL)
Replies
3K
Views
351K
7
73sydney
Dees_Troy
TWRP 3.2.3-1 for Pixel 2 XL
Replies
3K
Views
296K
Alxoom33
Alxoom33
flar2
[KERNEL] Pixel 2 XL ElementalX
Replies
2K
Views
199K
N
northsail
nitin.chobhe
[ROM][Pixel 2 XL][13.0] PixelDust Android 13 for taimen [04 Feb 2023]
Replies
2K
Views
186K
E
edednon
Eamo5
[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL
Replies
477
Views
110K
craigviar
craigviar

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 2
    A
    askany
    justDave said:
    Random suggestion: If you go into Messages app > Settings > Advanced, is the phone number set right? I remember that at some point on some phone I ended up with that field either empty or with nonsense and the SMS app was pretty confused.
    Click to expand...
    Click to collapse
    Positive, no problem there. My number is correct, the SMSC # is correct in the Advanced Settings.
    View
    2
    ridenickel9
    ridenickel9
    jam456 said:
    Good to hear!
    I have 2 taimens, one really beat up taimen I bought from ebay really cheap just for testing and my daily driver I've had from new and have ran unofficial LOS 19/20. The whole RIL issue came up with Android 13 last year when everyone first installed, it took the devs a while to sort out, one of the steps to fix was to go back to stock and reinstall A13. On my test taimen I have had to go back few times to stock as i install/switch to multiple roms.. on my daily since being on unofficial 20 I have never had to do it again, even if I had to wipe and reinstall clean again, so sticking to one seems to avoid reverting to stock.

    I don't really know why it happens changing from A12 to A13, thats a question for a dev. Remember the age of the phone, its 5+ years old and not everything is open source, qualcomm drivers etc.
    The whole Verizone texting issue i think is a rom based issue, something is missing from the rom system causing that issue but that will soon be fixed also hopefully
    Click to expand...
    Click to collapse
    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!
    View
    2
    madLyfe
    madLyfe
    madLyfe said:
    i was on feb 9 release and got an update for march 22, just installed that and after the reboot the swipe up gesture wont let me go to home screen w/o launcher crashing. i can swipe out of apps back to home screen though.

    i new update for today, march 23, but i get errors on downloading it or trying to go back to my feb 9 download via the install button.

    edit: looks like if i copy the url from the updater of march 23rd and go to it, it says "not found":
    "https://github.com/ods-releases/tai...n/lineage-20.0-20230323-UNOFFICIAL-taimen.zip"
    Click to expand...
    Click to collapse

    the download started working and got it installed. the march 23 build is the best yet. no more stutters and locks when moving around the ui. thanks!
    View
    2
    N
    npjohnson
    micoli5 said:
    Hi sir On new builds data connectivity toggle on qs is slow also Bluetooth connection is slow and too hard to find devices please do something
    Click to expand...
    Click to collapse
    Neither of these are helpful bug reports.

    Please use the bug reports system detailed on the wiki if you have issued.
    View
    2
    N
    npjohnson
    neilth said:
    The weekly LOS 20 updates now have three img files available to download along with the update itself. Where are any details/instructions concerning the use of these img files documented?
    Click to expand...
    Click to collapse
    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 following
    View
  • 21
    N
    npjohnson
    lineage-os-logo.png


    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.
    • taimen - Official builds​
    • taimen - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • None.​
    • Find any? Report them according to this guide.​
    Notes:
    • 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!​
    Kernel Source: https://github.com/LineageOS/android_kernel_google_wahoo
    View
    17
    N
    npjohnson
    Official builds will roll within a week!
    View
    8
    N
    npjohnson
    5dPZ said:
    Did anyone bother to try out every recent build and see which is the latest one that works without a bootloop?
    It seems that at least
    20230106
    20230109
    are not working.

    @npjohnson I understand that devs are extremely busy people, but how available are you for this project? If you do not have much spare time, could you at least make a working ROM (that is, without bootloops) before you take a break from this project? Much appreciated!
    Click to expand...
    Click to collapse
    work trip, I'll look into it when I get back. No clue what's going on.
    View
    7
    N
    npjohnson
    mo0zh222 said:
    Hey Dev!
    Thank you for your continued support of Taimen as this phone still is a workhorse even in late 2022! I can not log into my snapchat as of the latest build, today is 11/17/22 , it says due to repeated attempts or unusual activity your access to snapchat is currently disabled. I reverted to the stock 11 rom and it worked fine! Yes I tried their troubleshooting and support to no avail. How fluently you have 13 working on here Google should still supported Taimen!!!!! Thank you I look forward to and anticipate future builds!!! I flashed back to your rom after testing logging in on 11. Also the SELinux not enforcing thing I am concerned about as well.
    Click to expand...
    Click to collapse
    SELinux is permissive due to a single bug I need to solve.

    And snapchat is safety net related. Enforcing might fix it alone.
    View
    4
    N
    npjohnson
    dimpoblimpo said:
    I believe all android 13 ROMs are permissive unless someone can shine more light on this. Security is out the window if that's what your after on android 13. Go to arrow 12.1 if you want everything working for safetynet
    Click to expand...
    Click to collapse
    it will be fixed in the next build, temporary.
    View

New posts