if you want Android 11 / lineage-18.0 :highfive:
https://forum.xda-developers.com/pi...om-lineage-18-0-pixel-3-xl-blueline-t4185847/
https://forum.xda-developers.com/pi...om-lineage-18-0-pixel-3-xl-blueline-t4185847/
[ROM][10][OFFICIAL] lineage-17.1 for Pixel 3/XL (blueline/crosshatch)
- Thread starter razorloves
- Start date
I was able to upgrade using the OTA. For some reason all of the recent releases are failing to boot, when the upgrade is applied using the LOS recovery (via adb sideload). But the OTA update to 20201103 worked.
Just reflash magisk to inactive slot before you reboot - works for me
I wonder if it has something to do with how you install it. Did you sideload magisk or patch the boot image (I sideloaded). Also, I'm on the latest canary, I'm not sure when this started working.I installed the new magisk but after updating it has been erased as usual
I don't think that would matter. It gets overwritten anyway. I noticed there's a 99-magisk.sh in my /system/addon.d. Do you have that? I wonder if that doesn't get installed if you patch the boot image yourself.
By the way, I just took another OTA and magisk is still there after it completed.
By the way, I just took another OTA and magisk is still there after it completed.
I dont have that file, I'll look at installing via sideload thanks
On topic this ROM has been stable as usual for many months
Can anyone help me find the patched boot img to root using magisk? All I find are pretty dated guides like this https://forum.xda-developers.com/t/...magisk-18-1-pre-patched-boot-img-feb.3856712/
Figured it out, just need to patch the recovery file (64mb) that you used to flash the phone and it's all good.
@H2avo I suspect you rebooted into the system in between the flash. Follow the video exactly and youll be fine.
Figured it out, just need to patch the recovery file (64mb) that you used to flash the phone and it's all good.
@H2avo I suspect you rebooted into the system in between the flash. Follow the video exactly and youll be fine.
Last edited:
do anyone has problems with SMS? (in GSM/2G/3G/4G) I opened a bug report here
gitlab.com
SMS never works (official zip:
lineage-17.1-20210420-nightly-blueline-signed.zip
Solved the problem for los17.1 (I do not have gapps)
Just disable these 2 things by adb command
From : https://forum.xda-developers.com/t/...1-for-pixel-3-xl-blueline-crosshatch.4185847/
Cannot send or receive SMS (#3394) · Issues · LineageOS / issues / android · GitLab
Expected Behavior SMS send/receive should work Current Behavior SMS cannot be sent...
SMS never works (official zip:
lineage-17.1-20210420-nightly-blueline-signed.zip
Solved the problem for los17.1 (I do not have gapps)
Just disable these 2 things by adb command
Code:
adb shell pm disable-user --user 0 com.google.android.euicc
adb shell pm disable-user --user 0 com.google.android.imsFrom : https://forum.xda-developers.com/t/...1-for-pixel-3-xl-blueline-crosshatch.4185847/
Last edited:
Hello everyone,
First of all, thank you for your amazing work.
I am encountering an issue I do not know how to fix or find any information. It is related to the device's USB-C port
I bought a supposedly "new" Pixel 3 on Rakuten from Hong-Kong (I am in Europe) during February, used it some days with its stock ROM.
Then flashed it with this ROM. Everything was going really well, microG, magisk. The USB-C port was able to do as asked : charge, adb, audio, MTP, etc... I precise adb and fastboot were also functional with the bootloader and recovery.
And some day later I noticed my headphones (USB-C) stopped working : the phone was still playing sound through its own speakers. I discovered that adb was not working anymore. Same goes for MTP. I tried multiple cables and computers, rebooting everything I could. Even switch computer OSes. I tried to reboot the phone to recovery, or bootloader but it was still not available through adb or fastboot. I used the option in lineage recovery to make a factory reset, but it didn't change antyhing. The weird thing was that charging the phone was still perfectly okay.
And as, in the current state of TWRP (not available with this android version), I am not able to flash anything without adb or fastboot. I wanted to put it back in its original state (stock rom) to send it back to the seller but I couldn't. I still sent it back to the seller to get a replacement.
Took more than one month to get the replacement (postal services went haywire) but it got another Pixel 3. Screen has a small black circle and power/ volumes buttons were missing a bit of paint. So not a "new" Pixel 3. But I was still kinda happy to finally got a phone back.
I ran some checks : headphones, adb, fastboot, mtp were all okay with stock ROM. Decided to flash again to this ROM, with the same general options (MicroG, Magisk). Everything was again perfectly working with this LineageOS. Recovery and bootloader were also good, headphones were playing sound. And....
Yesterday I plugged my headset to make a call, and noticed that it stopped working. Same as before. And I got back to the same situation were no data could get transferred through cable, nor audio. The charge is, once again, still functional.
I tried to check logcat, and dmesg through ADB over network, but I didn't find anything standing out. My computer does not even see it getting connected when I check the computer logs (dmesg, journalctl, lsusb...).
Tried to see if the USB-C port has some dust in it with a tiny needle and nothing really came out.
I am a bit lost. Have I done something wrong to put my phone in this state ? Anyone has ever encountered something like this with the Google Pixel 3 ? Any lead of how to fix this ? I am looking for any advice.
I cannot really afford to send it back, again, to the seller.
I ordered a new Google Pixel 3 Charging Assembly part. I am going to try to replace the current one. It is a bit of a desperate move, I think
First of all, thank you for your amazing work.
I am encountering an issue I do not know how to fix or find any information. It is related to the device's USB-C port
I bought a supposedly "new" Pixel 3 on Rakuten from Hong-Kong (I am in Europe) during February, used it some days with its stock ROM.
Then flashed it with this ROM. Everything was going really well, microG, magisk. The USB-C port was able to do as asked : charge, adb, audio, MTP, etc... I precise adb and fastboot were also functional with the bootloader and recovery.
And some day later I noticed my headphones (USB-C) stopped working : the phone was still playing sound through its own speakers. I discovered that adb was not working anymore. Same goes for MTP. I tried multiple cables and computers, rebooting everything I could. Even switch computer OSes. I tried to reboot the phone to recovery, or bootloader but it was still not available through adb or fastboot. I used the option in lineage recovery to make a factory reset, but it didn't change antyhing. The weird thing was that charging the phone was still perfectly okay.
And as, in the current state of TWRP (not available with this android version), I am not able to flash anything without adb or fastboot. I wanted to put it back in its original state (stock rom) to send it back to the seller but I couldn't. I still sent it back to the seller to get a replacement.
Took more than one month to get the replacement (postal services went haywire) but it got another Pixel 3. Screen has a small black circle and power/ volumes buttons were missing a bit of paint. So not a "new" Pixel 3. But I was still kinda happy to finally got a phone back.
I ran some checks : headphones, adb, fastboot, mtp were all okay with stock ROM. Decided to flash again to this ROM, with the same general options (MicroG, Magisk). Everything was again perfectly working with this LineageOS. Recovery and bootloader were also good, headphones were playing sound. And....
Yesterday I plugged my headset to make a call, and noticed that it stopped working. Same as before. And I got back to the same situation were no data could get transferred through cable, nor audio. The charge is, once again, still functional.
I tried to check logcat, and dmesg through ADB over network, but I didn't find anything standing out. My computer does not even see it getting connected when I check the computer logs (dmesg, journalctl, lsusb...).
Tried to see if the USB-C port has some dust in it with a tiny needle and nothing really came out.
I am a bit lost. Have I done something wrong to put my phone in this state ? Anyone has ever encountered something like this with the Google Pixel 3 ? Any lead of how to fix this ? I am looking for any advice.
I cannot really afford to send it back, again, to the seller.
I ordered a new Google Pixel 3 Charging Assembly part. I am going to try to replace the current one. It is a bit of a desperate move, I think
Hi everyone,
I was on the 30 march build and decided to update to the 4 of May build but there is something wrong happening when trying to unlock the phone. The fingerprint, double tap or power button doesn't wake up the phone immediately (had to wait for 5/10 seconds or more). I don't know if I'm the only one having this issue but downgrading didn't fix the issue.
Best regards.
I was on the 30 march build and decided to update to the 4 of May build but there is something wrong happening when trying to unlock the phone. The fingerprint, double tap or power button doesn't wake up the phone immediately (had to wait for 5/10 seconds or more). I don't know if I'm the only one having this issue but downgrading didn't fix the issue.
Best regards.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
64lineage 18.1 (android 11) builds are now available. See new thread here:
https://forum.xda-developers.com/t/...1-for-pixel-3-xl-blueline-crosshatch.4185847/
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki for more details.
IMPORTANT NOTES:
1. Since TWRP doesn't work on Q for our device yet, you can use the lineage recovery. It's built into the rom's boot.img and is available separately on the download portal, named recovery image.
2. The newest vendor, radio, & bootloader img's are included in the rom zip, so no need to flash those manually.
3. Lineage comes with adb root that you can enable in developer options, but if you want root for apps, you can install the magisk apk, then follow these boot.img patching instructions. Use the file labeled 'recovery image' on the lineage rom download portal, which is actually just the boot.img. It is renamed to recovery to simplify the rom install steps.
Downloads:
blueline rom: https://download.lineageos.org/blueline
crosshatch rom: https://download.lineageos.org/crosshatch
gapps: (gapps are optional) - link / WARNING: Only use pico or nano gapps.
google fi gapps addon - if your carrier is Google Fi, flash this zip right after flashing gapps zip. https://androidfilehost.com/?fid=8889791610682871038
Instructions:
FOR INITIAL INSTALL
blueline: https://wiki.lineageos.org/devices/blueline/install
crosshatch: https://wiki.lineageos.org/devices/crosshatch/install
FOR UPDATING
For normal updating from official 17.1 to a newer official 17.1, follow these steps:
blueline: https://wiki.lineageos.org/devices/blueline/update
crosshatch: https://wiki.lineageos.org/devices/crosshatch/update
Protip: Enable "Prioritize update process" in the Updater preferences to make it go faster
Alternative manual updating instructions:
1. boot into lineage recovery.
2. install rom zip.
3. if you use gapps, select the "reboot into recovery" option, then install the gapps zips.
Changelog
blueline
crosshatch
Bug reporting
https://wiki.lineageos.org/bugreport-howto.html
Source Code:
crosshatch device tree: https://github.com/LineageOS/android_device_google_crosshatch/tree/lineage-17.1
blueline device tree: https://github.com/LineageOS/android_device_google_blueline/tree/lineage-17.1
kernel tree: https://github.com/LineageOS/android_kernel_google_msm-4.9/tree/lineage-17.1
vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-17.1
Credits:
Many thanks to my fellow LineageOS team members and all the contributors out there in the community. :good:
Android version: 10
Kernel version: 4.9.210
Status: Official Nightly28The time has come.
https://review.lineageos.org/c/LineageOS/hudson/+/282563
Official builds will start coming out whenever the build servers get to it. Probably within a few days. I'll keep an eye out for them and let you know when i see them coming through the pipeline.23I was going to wait till april security patches came out, to release new builds, but some very exciting news came
around this morning that dev @jhenrique09 has found the problem and fix for Android Auto. :good: :highfive:
Please go to his post here and hit his thanks and/or donate button to show him some love.
So here are the new builds with the Android Auto fix.
blueline rom - https://androidfilehost.com/?fid=4349826312261757899
blueline boot img - https://androidfilehost.com/?fid=4349826312261757900
crosshatch rom - https://androidfilehost.com/?fid=4349826312261757916
crosshatch boot img - https://androidfilehost.com/?fid=434982631226175791420Great news! We finally figured out how to flash gapps zips to devices with dynamic partitions, like the pixel3/3xl.
So, from here on out ALL MY BUILDS WILL BE WITHOUT GAPPS.
That means every time you install my build in recovery and you want to keep gapps, you have to select "reboot to recovery", then install a gapps zip.
If you want gapps, you must use one of these unofficial opengapps zips that I made. The official opengapps are still missing one change to work properly with dynamic partitions. I'll let you all know when that change gets added to official opengapps.
GAPPS Download: https://www.androidfilehost.com/?w=files&flid=313020
Note: The micro package replaces the default launcher (Trebuchet) with google's Pixel Launcher.
Here are the new builds:
blueline rom - https://androidfilehost.com/?fid=4349826312261822021
blueline boot img - https://androidfilehost.com/?fid=4349826312261822022
crosshatch rom - https://androidfilehost.com/?fid=4349826312261822074
crosshatch boot img - https://androidfilehost.com/?fid=4349826312261822075
NOTE: When switching from my old rom (gapps included) to new rom (gapps not included), and you want to keep using gapps, just reboot into recovery and install my new build, then select the "reboot to recovery" option, then install gapps zip, then reboot to system.
NOTE#2: When switching from my old rom to new rom and you DON'T want to keep using gapps, you'll have to format data. Reboot into recovery, select the factory reset option (WARNING: this option erases everything on /data, including internal storage, so copy that stuff to your PC if you want to keep it.) Then install my new build, then reboot to system.
Notable changes:
* google neglected the aosp calendar app for years, so we switched to using Etar - change
* added auto dark mode to a few of our apps (dialer, contacts, messaging, keyboard) - change
* added pure black option to the dark theme settings - change
* added a couple new fonts to Styles (theme picker) - change
* added setting to hide gestural navigation hint bar - change19new builds with june security updates from google. :good:
blueline rom - https://androidfilehost.com/?fid=12420606652095399330
blueline boot img - https://androidfilehost.com/?fid=12420606652095399331
crosshatch rom - https://androidfilehost.com/?fid=12420606652095399378
crosshatch boot img - https://androidfilehost.com/?fid=12420606652095399377
NOTE: The opengapps team merged my change for dynamic partitions, so you can use their official builds now. :highfive:
I tested pico thru stock variant, so those work.
Also, fyi, in micro variant and bigger, you cannot use the launcher built into lineage (Trebuchet). You have to use Pixel Launcher.
New posts
-
-
-
[GUIDE][FIRMWARE] QLink Scepter 8 Stock Firmware Restoration & Upgrading Guide- Latest: Viva La Android