[ROM][UNOFFICIAL] LineageOS 18.1 for Nexus 6P (angler)

Search This thread
yUIn6TF.png
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.

Important Info:
To flash this rom you need TWRP 3.3.1.0 or newer.


Make sure you have the vendor, radio, & bootloader img's installed, from the stock oreo 8.1 OPM7.181205.001 Dec 2018 factory image.
They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
vendor, radio, bootloader img's: https://androidfilehost.com/?w=files&flid=286833
The vendor img is flashable with twrp or fastboot. For the radio and bootloader img, use fastboot.

Instructions:
If updating from an unofficial lineage-18.1 build, follow the steps below:
  1. If you don't already have them installed, flash the newest vendor, radio, and bootloader img's linked above.
  2. Boot into TWRP.
  3. Flash the ROM zip.
  4. Reboot & enjoy.
NOTE: if you previously flashed gapps and/or the su addon, there's no need to flash them again. They will be automatically re-installed during rom zip installation.

If coming from a different ROM:
  1. If you don't already have them installed, flash the newest vendor, radio, and bootloader img's linked above. also make sure you have the newest twrp, linked above.
  2. Boot into TWRP.
  3. Wipe system & data & cache partitions.
  4. Format data.
  5. Flash rom & GApps & su zips (GApps & su zips are optional).
  6. Reboot & enjoy.

For more info or more detailed instructions, visit our wiki here.

Downloads:
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:
Gapps version:

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:

Source Code:
 

2ndLeaf

Member
Dec 21, 2014
23
5
After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:

E:\>adb devices
List of devices attached
84D7Q15A12345678 offline

Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging

When booting to bootloader, fastboot doesn't report any device.

Recovery is wiped out. That is, I can no longer boot into recovery.

After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.

Any suggestion?
 
Last edited:
  • Like
Reactions: rahul2021

rahul2021

New member
Jan 24, 2021
1
1
After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:

E:\>adb devices
List of devices attached
84D7Q15A12345678 offline

Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging

When booting to bootloader, fastboot doesn't report any device.

Recovery is wiped out. That is, I can no longer boot into recovery.

After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.

Any suggestion?
I am having same problem. Any suggestion ?
 
  • Like
Reactions: Moses mamman

marianodelfino

Senior Member
Apr 30, 2015
270
70
After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:

E:\>adb devices
List of devices attached
84D7Q15A12345678 offline

Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging

When booting to bootloader, fastboot doesn't report any device.

Recovery is wiped out. That is, I can no longer boot into recovery.

After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.

Any suggestion?

Reboot to bootloader. Connect the phone to pc, uninstall the driver in case of recognition, if not choose update driver. Once it pops up, select manually the adb bootloader interface driver. Open adb and do fastboot devices, it should appear. Also, switch usb port.
 

2ndLeaf

Member
Dec 21, 2014
23
5
Reboot to bootloader. Connect the phone to pc, uninstall the driver in case of recognition, if not choose update driver. Once it pops up, select manually the adb bootloader interface driver. Open adb and do fastboot devices, it should appear. Also, switch usb port.

Thanks for your suggestion. I check the device manager. My Windows PC already has nexus-6p driver installed. I try to upgrade it. Windows reports I already have the latest driver. The same usb port works for my other android phones. Only the nexus 6p doesn't work (it worked well before I upgraded to lineage-18.0-20200929-UNOFFICIAL-angler .)

BTW, I am able to copy files to my phone. Is there any way to reflash my phone to a different image by sideloading a program on phone? I try to sideload the play store app but the app always crashes.
 
Last edited:

marianodelfino

Senior Member
Apr 30, 2015
270
70
Thanks for your suggestion. I check the device manager. My Windows PC already has nexus-6p driver installed. I try to upgrade it. Windows reports I already have the latest driver. The same usb port works for my other android phones. Only the nexus 6p doesn't work (it worked well before I upgraded to lineage-18.0-20200929-UNOFFICIAL-angler .)

BTW, I am able to copy files to my phone. Is there any way to reflash my phone to a different image by sideloading a program on phone? I try to sideload the play store app but the app always crashes.

Doesn't matter if it used to work or work for other phones... do the process... sometimes it doesn't recognize the proper driver... the easy test is... go to fastboot and connect the phone to the pc if you inspect the device manager and your phone is not listed as "Bootloader interface" then it will never be recognized on fastboot... is that simple... That's why you have to manually select it, to force windows use the driver you are selecting.

I know this process because it happened to other of my phones... i had to manually select the driver so it appear on fastboot and be able to flash through it
 
  • Like
Reactions: 2ndLeaf

2ndLeaf

Member
Dec 21, 2014
23
5
Doesn't matter if it used to work or work for other phones... do the process... sometimes it doesn't recognize the proper driver... the easy test is... go to fastboot and connect the phone to the pc if you inspect the device manager and your phone is not listed as "Bootloader interface" then it will never be recognized on fastboot... is that simple... That's why you have to manually select it, to force windows use the driver you are selecting.

I know this process because it happened to other of my phones... i had to manually select the driver so it appear on fastboot and be able to flash through it

Thanks again for your reply. I can see Nexus 6P in device manager (see attached). Does that mean I already have proper driver installed? If not, could you point me to a wiki that I can follow to update the driver? I follow the link below to set up adb. It doesn't mention about driver:


I downloaded the USB driver from the following site. But windows refuses to update the driver claiming I already have the latest.

 

marianodelfino

Senior Member
Apr 30, 2015
270
70
I find this thread: https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/

I was able to enable the ADB interface. But "adb devices" still shows nexus 6p is offline.

View attachment 5217521

1613044356706.png


This is what you should see if you are in bootloader.

If you are in bootloader, windows shows the proper driver like in the image and you type fastboot devices, the device will show up and you will be able to reflash twrp if you want or do whatever
 
  • Like
Reactions: 2ndLeaf

marianodelfino

Senior Member
Apr 30, 2015
270
70
I downloaded the USB driver from the following site. But windows refuses to update the driver claiming I already have the latest.

The steps are... you boot into bootloader, connect the phone to pc. Select the device on device manager and click properties and then drivers. Then select update drive and select the option that says something like "choose manually", then select the other option that appears, says something like "choose from list" once you click that it will present to you a list of drivers and you manually select the bootloder interface driver. After doing that, it will work. Open adb, type fastboot devices and it will appear.
 
  • Like
Reactions: 2ndLeaf

2ndLeaf

Member
Dec 21, 2014
23
5
The steps are... you boot into bootloader, connect the phone to pc. Select the device on device manager and click properties and then drivers. Then select update drive and select the option that says something like "choose manually", then select the other option that appears, says something like "choose from list" once you click that it will present to you a list of drivers and you manually select the bootloder interface driver. After doing that, it will work. Open adb, type fastboot devices and it will appear.

Thanks for the detail instruction. I am able to recover my nexus 6p. Hooray!!! :)
 

Moses mamman

New member
Mar 19, 2021
3
0
I had t
After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:

E:\>adb devices
List of devices attached
84D7Q15A12345678 offline

Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging

When booting to bootloader, fastboot doesn't report any device.

Recovery is wiped out. That is, I can no longer boot into recovery.

After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.

Any suggestio

After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:

E:\>adb devices
List of devices attached
84D7Q15A12345678 offline

Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging

When booting to bootloader, fastboot doesn't report any device.

Recovery is wiped out. That is, I can no longer boot into recovery.

After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.

Any suggestion?
I had the same issue and I really need help
 

Moses mamman

New member
Mar 19, 2021
3
0
I had t
After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:

E:\>adb devices
List of devices attached
84D7Q15A12345678 offline

Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging

When booting to bootloader, fastboot doesn't report any device.

Recovery is wiped out. That is, I can no longer boot into recovery.

After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.

Any suggestio

After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:

E:\>adb devices
List of devices attached
84D7Q15A12345678 offline

Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging

When booting to bootloader, fastboot doesn't report any device.

Recovery is wiped out. That is, I can no longer boot into recovery.

After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.

Any suggestion?
I had the same issue and I really need h
Known issues
  • Constant System UI crashes.
  • Regular hiccups/freezes.
  • Broken Camera.
  • Bluetooth connectivity may vary.
  • Wi-Fi Hotspot.
Can't play videos
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    yUIn6TF.png
    LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.

    Important Info:
    To flash this rom you need TWRP 3.3.1.0 or newer.


    Make sure you have the vendor, radio, & bootloader img's installed, from the stock oreo 8.1 OPM7.181205.001 Dec 2018 factory image.
    They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
    vendor, radio, bootloader img's: https://androidfilehost.com/?w=files&flid=286833
    The vendor img is flashable with twrp or fastboot. For the radio and bootloader img, use fastboot.

    Instructions:
    If updating from an unofficial lineage-18.1 build, follow the steps below:
    1. If you don't already have them installed, flash the newest vendor, radio, and bootloader img's linked above.
    2. Boot into TWRP.
    3. Flash the ROM zip.
    4. Reboot & enjoy.
    NOTE: if you previously flashed gapps and/or the su addon, there's no need to flash them again. They will be automatically re-installed during rom zip installation.

    If coming from a different ROM:
    1. If you don't already have them installed, flash the newest vendor, radio, and bootloader img's linked above. also make sure you have the newest twrp, linked above.
    2. Boot into TWRP.
    3. Wipe system & data & cache partitions.
    4. Format data.
    5. Flash rom & GApps & su zips (GApps & su zips are optional).
    6. Reboot & enjoy.

    For more info or more detailed instructions, visit our wiki here.

    Downloads:
    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:
    Gapps version:
    
    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:

    Source Code:
    5
    Known issues
    • Constant System UI crashes.
    • Regular hiccups/freezes.
    • Broken Camera.
    • Bluetooth connectivity may vary.
    • Wi-Fi Hotspot.
    5
    Peripherals

    FBE Recovery
    : TWRP
    FBE Recovery (4 Core): TWRP
    BLOD Patch (4 Core): boot.img
    4
    Thank you for the work, but why do you have to keep developing new ROM's instead of updating old ROM's that you released before? Isn't it more work to create a new ROM than updating an existing ROM?

    It would have been fine if we could just flash a new ROM over a different ROM and keep all the settings, but we need to wipe the settings to flash a new ROM. This may not be a problem for a testing device, but if one is actually using the phone, keep losing the settings (and possibly data if something goes wrong during the flashing) is really inconvenient.
    3
    The steps are... you boot into bootloader, connect the phone to pc. Select the device on device manager and click properties and then drivers. Then select update drive and select the option that says something like "choose manually", then select the other option that appears, says something like "choose from list" once you click that it will present to you a list of drivers and you manually select the bootloder interface driver. After doing that, it will work. Open adb, type fastboot devices and it will appear.

    Thanks for the detail instruction. I am able to recover my nexus 6p. Hooray!!! :)