[ROM][OFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL

Search This thread
D

Deleted member 11401259

Guest
An stupid question, is it posible to lock the bootloader once lineage os is installed?
 
D

Deleted member 11401259

Guest
I got It, i read some post about signed kernel in one plus one forum.
 

MrBrady

Senior Member
Oct 26, 2010
3,336
903
There are a couple ROMs that allow bootloader locking. Proton is one of them. But the phone knows you have a altered system and shows a different warning on boot.

I don't see a big advantage of doing it. I did it on my P2XL and gave the phone to my wife. All was well for a couple months until it was used until the battery died and I couldn't get it to charge or boot to any mode. I think it was because of the locked bootloader setup. Since the device appeared dead, we got her a Pixel 6 Pro as a replacement.

Eventually I was able to trigger a boot by plugging into a USB hub. Got it charged enough, unlocked the bootloader, factory flashed both partitions, then there on LOS. Never had a problem since and the phone is super snappy with good battery life!
 
Last edited:

MrBrady

Senior Member
Oct 26, 2010
3,336
903
Just found either a bug with the ROM or a defect with my device. When I plug in the stock USB-C Audio Adapter and plug in headphones, the ROM doesn't see them and outputs audio through the speakers still.

What's more weird is, depending on the headphones, when I plug them in a USB notification pops-up saying it's charging the attached accessory. But it's not charging - the headphone charging lights are not illuminated.

Tried rebooting, updating to latest LOS and making sure USB Audio is not disabled in Developer Options.

Tried with Sennheiser HD1 and Marshall Mid headphones. Both are Bluetooth (turned off) with optional wired connector plugged in.


Seems to be a defect with my phone. Happens on stock and other ROMs too.
 
Last edited:
D

Deleted member 11401259

Guest
I'm experience ramdom problems with apps. Sometimes Gmail or drive not sync, sometimes other apps show "not connection to internet" or don´t load some parts of the app.

Battery is stuck in 98% with stock rom reachs 100%

Thank you
 
D

Deleted member 11401259

Guest
Reading forums, the problem seems to be updates form settings, some people fix it reinstalling gapps. In other threads seems to be switch wifi and mobile data. Now it's working fine, since i'm not using wifi.
 
Last edited by a moderator:
D

Deleted member 11401259

Guest
I don't know but is working fine with the update. I'll still asking about charge stop at 98% and with stock rom it reached 100%. Lineage rom, is faster and smooth, i love it.
 

Ethanol6

New member
Mar 9, 2022
4
1
Canada
I'm having a heck of a time just getting twrp booted. I only have experience with one other device so maybe there's something obvious here.

I'm using twrp-3.6.0_9-0-taimen.img.

The output of (fastboot boot twrp-3.6.0_9-0-taimen.img)

downloading 'boot.img'...
OKAY [ 1.133s]
booting...
FAILED (remote: dtb not found)
finished. total time: 2.290s

The instruction at the top of this thread say to use (fastboot boot ...) while the wiki that is linked says to use (fastboot flash boot ...) Which one is right?

The TWRP page for taimen says "If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image."

If I run (fastboot flash boot twrp-3.6.0_9-0-taimen.img) I get this:

target reported max download size of 536870912 bytes
sending 'boot_b' (40960 KB)...
OKAY [ 1.202s]
writing 'boot_b'...
FAILED (remote: size too large)
finished. total time: 1.251s

I switched to slot a with the same results.
Any help would be greatly appreciated.
 

dcarvil

Senior Member
Apr 20, 2016
596
337
I'm having a heck of a time just getting twrp booted. I only have experience with one other device so maybe there's something obvious here.

I'm using twrp-3.6.0_9-0-taimen.img.

The output of (fastboot boot twrp-3.6.0_9-0-taimen.img)

downloading 'boot.img'...
OKAY [ 1.133s]
booting...
FAILED (remote: dtb not found)
finished. total time: 2.290s

The instruction at the top of this thread say to use (fastboot boot ...) while the wiki that is linked says to use (fastboot flash boot ...) Which one is right?

The TWRP page for taimen says "If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image."

If I run (fastboot flash boot twrp-3.6.0_9-0-taimen.img) I get this:

target reported max download size of 536870912 bytes
sending 'boot_b' (40960 KB)...
OKAY [ 1.202s]
writing 'boot_b'...
FAILED (remote: size too large)
finished. total time: 1.251s

I switched to slot a with the same results.
Any help would be greatly appreciated.

fastboot boot twrp-3.6.0_9-0-taimen.img boots TWRP without installing it to the boot partition. This is the correct command.

fastboot flash boot twrp-3.6.0_9-0-taimen.img installs TWRP to the boot partition. Since you ran this command, you will now have to do as the TWRP page says, and download the latest factory image and reflash the boot image. You can download the factory image at https://developers.google.com/android/images#taimen. The boot image is inside the zip file that is inside the zip you will download.

If reflashing the factory boot image does not work, you may have to flash the full factory image, which will wipe your phone.
 

Ethanol6

New member
Mar 9, 2022
4
1
Canada
fastboot boot twrp-3.6.0_9-0-taimen.img boots TWRP without installing it to the boot partition. This is the correct command.

fastboot flash boot twrp-3.6.0_9-0-taimen.img installs TWRP to the boot partition. Since you ran this command, you will now have to do as the TWRP page says, and download the latest factory image and reflash the boot image. You can download the factory image at https://developers.google.com/android/images#taimen. The boot image is inside the zip file that is inside the zip you will download.

If reflashing the factory boot image does not work, you may have to flash the full factory image, which will wipe your phone.
Thanks for the details, I'll give this a shot. The fastboot command output said it failed though. So am I misunderstanding something here?
 

dcarvil

Senior Member
Apr 20, 2016
596
337
Thanks for the details, I'll give this a shot. The fastboot command output said it failed though. So am I misunderstanding something here?
The first command should have been successful if you were starting from a working phone. That error message indicates there was something wrong with the phone before you tried to install TWRP. If that is the case, you will need to flash a full image to restore the phone before installing TWRP.
 

Ethanol6

New member
Mar 9, 2022
4
1
Canada
The first command should have been successful if you were starting from a working phone. That error message indicates there was something wrong with the phone before you tried to install TWRP. If that is the case, you will need to flash a full image to restore the phone before installing TWRP.
Ah, understood. Well I'm embarrassed to admit that I've made a symphony of errors here, not the least of which is realizing... uh.. this isn't a pixel 2... I'm a dummy. Thanks so much for your time!
 
  • Like
Reactions: dcarvil

g000n

Senior Member
Sep 4, 2015
379
121

Lineage OS 19.0 for Pixel 2 / 2 XL thread​

 

g000n

Senior Member
Sep 4, 2015
379
121
the wiki guide has a mistake https://wiki.lineageos.org/devices/taimen/install

it says

Temporarily flash a recovery on your device by typing (replace <recovery_filename> with the actual filename!):
fastboot flash boot <recovery_filename>.img

when it should be

fastboot boot

not

fastboot flash boot

---

Also, when I try to run safetynet attestation on the latest version of YASNAC
it says
" Requires Googe Play Services v13.0 or above"
even though my Google Play services is v22.09.20
Any help?
 
Last edited:
  • Like
Reactions: neilth

cooltime

Member
Nov 27, 2017
13
4
My antenna performance has gone to crap. Possibly caused by me dropping my phone (small crack in bottom corner). Pixel 2. Can barely download any MMS pictures. Takes ages to find signal. Almost never on LTE. Put the same SIM into my old Nokia 6.1 2018 and I get full bars. This stuff has persisted across multiple LineageOS updates. Wifi and bluetooth still seems strong.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 28
    yUIn6TF.png

    LineageOS is a free, community built, aftermarket firmware distribution of Android 11.0, 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.

    What's working

    • Active Edge
    • RIL (Calls, SMS, Data)
    • Bluetooth
    • Wi-Fi
    • Camera
    • Video Recording
    • Video Playback
    • Audio ( Record and Playback )
    • Sensors
    • Flash
    • Led

    What's not working

    • Feel free to report any issues you may encounter with relevant logs

    Installation

    1. Download the latest supported Lineage OS build, TWRP image and optionally the TWRP installer zip.
    2. Reboot to bootloader
    3. Wipe userdata for initial install (fastboot format userdata)
    4. Fastboot into TWRP recovery (fastboot boot twrp.img)
    5. Flash the latest build of Lineage OS
    6. Reboot to bootloader and fastboot TWRP again
    7. (Optional) Flash gapps of choice (MindTheGapps are recommended)
    8. Reboot to system and don't install the TWRP app
    9. (Optional) Flash custom kernel / TWRP / Magisk

    A more detailed installation guide can be found on the wiki.

    Updates

    Simply repeat steps 4 - 7. You shouldn't need to flash factory images as all partitions (firmware, vendor etc.) are updated with the lineage zip.

    Downloads


    Credits

    • razorloves
    • javelinanddart
    • RaymanFX
    • Sultanxda
    • LineageOS Team

    Source


    Feel free to join my Pixel 2 telegram group here.
    12
    Lineage OS 18.1 (5/3/21)
    • March ASB
    • March kernel security patches
    • Fixed rare app not installed toast
    • Fixed crashes when installing without gapps
    • Revamped Lineage OS recorder app
    • Added Trebuchet icon pack support
    11
    Official builds are now available for downloading. The migration process from my unofficial builds is as follows:

    1. Download the latest version of Lineage OS and the lineage recovery image for your device from here.
    2. Reboot to bootloader
    3. Flash the recovery image to your boot partition (fastboot flash --slot all boot /path/to/recovery.img)
    4. Reboot into recovery
    5. Flash the official build of Lineage OS (adb sideload lineage.zip)
    6. If you have gapps installed, reboot to recovery again and ensure you flash gapps again before booting into Lineage OS
    7. Reboot your phone and enjoy!
    Or if you use TWRP you can just follow the normal updating steps and skip flashing the new recovery image.

    If you are coming from a previous version of Lineage OS, please refer to the wiki.
    10
    I've uploaded a slightly updated build to amend the missing live captions button when adjusting volume. Apologies for the inconvenience.
    10
    Lineage OS 18.1 (8/1/21)

    • January ASB
    • January / December kernel security patches
    • Bug fixes and improvements