[Pixel 2XL][TESTING] Unofficial LineageOS 15.1 builds

Search This thread

GridironTrenches

Senior Member
Dec 6, 2012
171
26
the process I've used for flashing monthly updates are
1. fastboot OTA img. Lineage is different.
2. fastboot twrp img
3. flash twrp zip
4. flash a kernel
5.flash magisk last
but Lineage is probably different since its a zip but like the OP said you are still flashing a boot img so maybe the order is wipe stock rom in twrp, flash lineage, then flash twrp zip and finally flash magisk before initial boot but i could be wrong
 
Last edited:

Az Biker

Sr. Mod / RC-RT Committees / Shred'r of MTBs
Staff member
Can't you just flash Magisk

Good question. The post I responded to said root wasn't working, I just wanted to make sure they saw the instruction in the OP since it is not a usual step.

They also said they were going to flash Magisk, so I guess we'll soon find out if you can simply flash Magisk with this Rom.

I'm gonna sit back, read comments, and see results before I jump in :D
 

raynan

Senior Member
Jan 2, 2011
1,126
576
Good question. The post I responded to said root wasn't working, I just wanted to make sure they saw the instruction in the OP since it is not a usual step.

They also said they were going to flash Magisk, so I guess we'll soon find out if you can simply flash Magisk with this Rom.

I'm gonna sit back, read comments, and see results before I jump in :D

Just flashed it because I couldn't remount for some reason. Magisk is working fine so far! The water seems to be pretty good, you know you want to join us! :p
 
  • Like
Reactions: Az Biker

patt2k

Senior Member
Mar 22, 2009
3,390
546
Sweet thank you ! Will play around on the weekend :)

Sent from my Pixel 2 XL using Tapatalk
 

otonieru

Senior Member
May 7, 2011
3,716
2,362
Djakarta
Just flashed it because I couldn't remount for some reason. Magisk is working fine so far! The water seems to be pretty good, you know you want to join us! :p

Could you check whether the diag working on this rom ?

because diag mode was stripped from stock. shame you google. i cant plugged this phone to QXDM because of it.

to try diag, normally we need to run this command from adb :

adb shell
su
setprop sys.usb.config diag, adb

or

you can see in init.usb.rc whether there's any diag entry in sysconfig code
 

raynan

Senior Member
Jan 2, 2011
1,126
576
Could you check whether the diag working on this rom ?

because diag mode was stripped from stock. shame you google. i cant plugged this phone to QXDM because of it.

to try diag, normally we need to run this command from adb :

adb shell
su
setprop sys.usb.config diag, adb

or

you can see in init.usb.rc whether there's any diag entry in sysconfig code

So, it lets me set the property and getprop shows it's set, but I don't see anything in device manager after doing so.

Out of curiosity, what do you use QXDM for?
 
Last edited:
  • Like
Reactions: otonieru

Az Biker

Sr. Mod / RC-RT Committees / Shred'r of MTBs
Staff member

otonieru

Senior Member
May 7, 2011
3,716
2,362
Djakarta
So, it lets me set the property and getprop shows it's set, but I don't see anything in device manager after doing so.

Out of curiosity, what do you use QXDM for?

Thx for trying

So no "unknown device" appear in device manager ?

I need to use QXDM to reconfig the IMS (VoLTE) related NV value for my company, so that our VoLTE services can work in the device. Because its not supported out of the box by google :eek:

most of the time i only need to disable the "carrier check" configuration value. Kinda make me wonder, why cant google implement something simple like dialing *#*#VOLTE#*#* to do so just like what xiaomi did.

am quite often using it to play around as well, who knows what we can find. just like how i managed to unlock the LTE bands on Oneplus 3 back then.

---------- Post added at 06:18 PM ---------- Previous post was at 06:16 PM ----------

Im guessing no dui in this build or any nav bar customization? Does Google camera work?

+1

Does Google Camera porting work ?

Would be a huge miss if we are no longer able to get HDR+ and portrait mode :p
 

Top Liked Posts

  • There are no posts matching your filters.
  • 65
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Bugs/Issues :
    • Mobile data seems to be broken
    • Project Fi eSim cards do not work
    • VoLTE/IMS not working
    • ...?

    Instructions :
    • Download the latest build
    • Reboot to recovery
    • Flash the latest build
    • Reboot
    Downloads :
    • Builds : See below
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
     
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
     
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
     
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    I'm your Lineage maintainer for taimen aka Pixel 2 XL, but will share my builds here until we provide official builds.

    WARNING: These are my personal testing builds. They include unmerged, work-in-progress stuff such as SuperUser, Privacy Guard, Google Play services etc. DO NOT FLASH 3RD PARTY GAPPS PACKAGES!

    If you see a warning about vendor partition mismatch, you can ignore that in most cases, but before reporting issues you should be on the right version (without the warning).

    ### RELEASES ###
    2018/01/11 - Android File Host
    2018/01/13 - Android File Host
    2018/01/19 - Android File Host


    XDA:DevDB Information
    LineageOS, ROM for the Google Pixel 2 XL

    Contributors
    RaymanFX
    Source Code: http://github.com/LineageOS

    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 4.x

    Version Information
    Status: Testing

    Created 2018-01-11
    Last Updated 2018-02-19
    18
    Hey guys, new build is up (check the OP), mobile data is fixed and LTE is enabled.

    Big thanks to surge for figuring that one out, it was easy to see where the issue came from with that information!
    The corresponding fixes are on Gerrit:
    https://review.lineageos.org/#/c/202338/ (netutils)
    https://review.lineageos.org/#/c/202337/ (LTE setting)

    Please let me know of any additional issues and I will work on them to make sure the builds are solid before putting them on our servers at some point in the future.

    One more thing - since I have been asked at least a thousand times now for walleye (smaller Pixel 2) support:
    I do not own one, so I cannot (and will not) support it. Someone else from our team has it, but everything from unofficial releases or maintenance is up to him.
    We coordinate our work, but that still does not mean I can provide builds (because if I would, I'd be left with a list of issues I cannot fix for obvious reasons).
    So if you want test builds now (same state as taimen), your options are 1) sending me a device 2) build it yourself :)
    12
    You just guys could try the below commands in terminal

    su (assuming lineage has it or an equivalent, try run-as with setcap to give it exec if not)

    mount -o rw,remount /system (assuming lineage uses toybox)

    Essentially all the prior steps are to get system remounted rw, I haven't used lineage and back when I used cm they used to do things similar to how we do on aosp, but since then they have diverged significantly, I tried to find the lineage build dir to find out for you guys but apparently they moved it to vendor for some ungodly reason, anyways the point is, get system remounted rw.

    So to recap:

    Code:
    su
    
    mount  -o rw,remount /system
    
    cd /system/bin
    
    ln -s netutils-wrapper-1.0 ./ip-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./ip6tables-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./iptables-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./ndc-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./tc-wrapper-1.0
    
    reboot

    I keep saying this but again this all all assuming lineage hasn't blocked mounting block devices for shell via sepolicy, and that they have not enabled verity for system

    But in any case try at your own peril.

    Also if those files already exist MAKE SURE they are symlinks if not, remove them and run the commands again
    11
    You just guys could try the below commands in terminal

    su (assuming lineage has it or an equivalent, try run-as with setcap to give it exec if not)

    mount -o rw,remount /system (assuming lineage uses toybox)

    Essentially all the prior steps are to get system remounted rw, I haven't used lineage and back when I used cm they used to do things similar to how we do on aosp, but since then they have diverged significantly, I tried to find the lineage build dir to find out for you guys but apparently they moved it to vendor for some ungodly reason, anyways the point is, get system remounted rw.

    So to recap:

    Code:
    su
    
    mount  -o rw,remount /system
    
    cd /system/bin
    
    ln -s netutils-wrapper-1.0 ./ip-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./ip6tables-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./iptables-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./ndc-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./tc-wrapper-1.0
    
    reboot

    I keep saying this but again this all all assuming lineage hasn't blocked mounting block devices for shell via sepolicy, and that they have not enabled verity for system

    But in any case try at your own peril.

    Also if those files already exist MAKE SURE they are symlinks if not, remove them and run the commands again

    Well @RaymanFX I can say that @Surge1223 instructions works perfectly! He figured out the Mobile Data issues for you hahah trying out the ROM now! Those that had mobile data issues.. just flash the ROM as usual then do the root commands for SU:

    adb root && adb remount (this will tell you that you need to disable verity so go to next command)

    adb disable-verity
    adb reboot
    adb root && adb remount
    adb shell chmod +x /system/xbin/su
    adb remount all
    adb shell

    Then run all of surges commands one line at a time:

    cd /system/bin

    ln -s netutils-wrapper-1.0 ./ip-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./ip6tables-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./iptables-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./ndc-wrapper-1.0
    ln -s netutils-wrapper-1.0 ./tc-wrapper-1.0

    also give @Surge1223 a thanks if he helped you out!
    8
    Don't flash! Not booting! Wiped my TWRP!

    Steps I took:
    Boot to twrp
    Format system, data and cache
    Install zip
    Reboot

    What happened:
    Stuck at google logo
    Recovery is now stock

    Guess I'm pulling my titanium backup and flashing system images

    Do you even understand how your own device works?
    A/B devices don't have a recovery partition anymore, it lives in the boot partition now, so YES, of course flashing another boot.img will wipe your TWRP.

    Which vendor image do you have currently?
    Be aware that if you flash this zip, it will install Lineage to the slot on your device that was *inactive* before, so it might have old stuff there that is not 8.1.

    I'd recommend you flash the stock Google 8.1 factory image before flashing this.

    My device boots just fine, so this has to be an error on your side I'm afraid :)

    I'm more curious to see if the Active Edge feature works.

    Active Edge is not integrated just yet, it requires more work on our side.