yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
Just be mindful of what slot you are currently on when you are doing things. If the ROM rebases on to a new security update, then you'll have to change to that. Watch the changelog on the download page and it'll tell you what firmware the ROM requires now. It'll be "update fingerprint to [build code]". This will only happen after Google releases the monthly security updates. You can install the ROM to both slots, but I don't do that as if a nightly is broken then your phone will attempt to boot to the other slot. If you've installed the nightly to both slots then you're just gonna keep bootlooping. My practice goes like this when a new monthly security update is out.

Look at what firmware the ROM is now based on from changelog

Download that firmware from Google

Run flash-all script (remove -w if needed)

fastboot --set-active=other

(yes, "other" is valid)

Run flash-all script again

Boot and install TWRP

Reboot to TWRP

Install ROM

Install TWRP

Done

LineageOS's installer for root is broken for our devices because it doesn't properly recognize the directory structure of our system partitions, and installs the files to the root folder instead of the system folder. I've modified the installer so that it will work properly. I've also modified the uninstaller but I haven't tested that yet, but it should work. Both are attached below. The menu for enabling root access is under Developer Options, and you could also use iSu to control access to root however I haven't tried that out yet. I'd do a clean install of the ROM before running the installer if you've tried installing SuperSU.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] General_Tso:
I missed this step when I initially installed Lineage OS. Is there a safe way to reinstall TWRP now? Should I just repeat the steps in the first post? Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
You don't need TWRP installed because you can use the updater in the ROM, unless you want to keep the ROM on only one slot or need to flash things. For most general flashables you can just fastboot boot RC1 and install them. If the flashable requires you to change slots or explicitly says it needs RC2 then you'll need to install it. It's perfectly fine to flash the TWRP installer after the fact because it patches the boot images.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] General_Tso:
My only requirements are rooting...and maybe backups. Does the first one at least work with fastboot boot RC1?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] josdehaes:
I'm curious to try the a/b updater. How does this work exactly? Does it preserve magisk? Anyone tried this?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
If you're using the LineageOS su then you should be able to flash it with RC1. If you're going with SuperSU then I'd recommend installing RC2 and using it.

Both the Updater and ROM flashing use the exact same process, so it'll install to the inactive slot and switch over to it, except the Updater doesn't do it in TWRP. All files on the system partition are destroyed and the boot image is overwritten on the inactive slot, so if you're going to use Magisk then you're going to need to keep TWRP.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] haibane:
Is there still a push to get this official, or are we just going to keep this as the weird a/b method with G-apps included? I've kind of stayed away after my first attempt because it is so convoluted. I am just curious if anyone else had the same experience. I wouldn't mind running LineageOS again in the future.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] General_Tso:
I tried to install AdAway after I installed Namelesswonder's SU add on, but it is failing to copy the hosts file. Is it possible that the cause is the same thing that complicates installing the SU add on?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] capz21:
Seconding this.

Sorry to be "that eta guy" but is there any progress [MENTION=2385005]invisiblek[/MENTION]?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] wewuz:
So, this is my first time flashing ROMS on my Pixel. I've followed the steps outlined above, and while the phone is not bootlooping, the initial boot after the install of the ROM seems to be stuck. Is there anything else I can try?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
How long constitutes stuck?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] wewuz:
I guess that was pretty essential information. At least 10 mins. Maybe I'm just not waiting long enough? I've flashed many ROMs in the past, this just seems to be longer than expected.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I've stopped counting and usually walk away but I would give it a bit, maybe 15 minutes at most but that does seem like a stretch but if you followed the steps you quoted and you're flashing rc1/rc2 of twrp then I would think you are good.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] wewuz:
Ya know, I just tried it a third time, and I ensured that I wiped (default twrp) prior to flashing the ROM and it ran with no problems. Much speedier and it appears to be working as expected. Not sure if the wipe or just luck. :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
I can't believe I missed that but yes you are spot on and those steps should include a factory reset before booting. Awesome that you got it going though.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jeffyh:
Does anyone have any older nightlies for sailfish? I updated from 07-26 to 07-31 and it borked my bluetooth audio. It sounds like someone took the audio and put it at 1/3 speed with lots of pops and such. Trying to toubleshoot now. I still had the 07-26 zip and tried flashing it after doing a full factory image flash-all, but I still have the audio issues. The NJH47D factory image does not have this issue.

I'm leaving for Italy in 10 hours and desperately trying to get things up and running. Does anyone have a 07-16 zip or something in the teens so I can test??
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hobbified:
Having the same problem on marlin, even to this day. And no, I don't have any older builds handy, at least none newer than May.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Sileem:
I was able to downgrade by going into the updater and selecting a July 13th build (which I had previously installed).
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DreamScar:
Could you upload that July version you have? I'm having the same Bluetooth audio issue, but I don't have an old version to roll back.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Sileem:
Do you know where the OTAs are stored? And is it accessible on a non-rooted device?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
/data/data/org.lineageos.updater/app_updates

Pretty sure you need root to access that location
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] General_Tso:
Is your installer for root persistent after flashing an update? All of the sudden, I don't seem to have root. Is there a way I can verify? Thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
No, addon.d is currently not working for the ROM and because of the fact that the system partition is completely wiped out on updates I can't make anything persistent. On updates you'll need to reflash the installer. To check if root is working you can either open up the developer options menu and see if you have the ability to enable root for apps or you can use a root checker app from the Play Store.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] starcitizen:
Bluetooth audio issue isn't fixed yet.

Is there a workaround to return BT audio functionality in the latest releases ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joeski27:
Question for you guys - spent all night (last 4 hours) trying to get to the bottom of this..........can anyone tell me why it is that every time I flash the latest nightly, gapps, etc., I lose TWRP? In other words, after I flash the rom and the other accompanying goodies, I reboot the system, and then the next time I reboot to recovery I have the Lineage recovery instead of TWRP. I've never had this happen on any other phone. Thoughts??
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] blaze9090:
Because los comes with its own recovery. Just flash twrp right after you flash the rom and you'll be fine.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joeski27:
Thanks for that, but I've been using Lineage for many months on my old 6P (just switching to/setting up my new XL now). Is this recovery thing I'm running into unique to the XL builds for Lineage? Because like I said I never had to reflash TWRP every time I updated to a new Lineage nightly on my 6P.

Also, is anyone (successfully) running ElementalX kernal with this? While at first it seemed to work fine for me, I noticed that with it flashed a number of apps started behaving strangely, so then after some reflashes I could see those apps working smoothly without Elemental installed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rockingondrums:
You must reflash twrp every time before you reboot. Please reference twrp pixel thread OP.

Edit: ninja'd. Yes, unique to Pixel family.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joeski27:
Ok so I'm a little late to the game with getting an XL set up after my 6P's battery finally **** out on me....but anyways I'm struggling to find a custom kernel (esp. the big name ones like ElementalX or Franco) that work with Lineage. Can anyone shed any light on this? One of the main reasons I wait to get a phone until it has been out nearly a year is that most of the main hacking kinks have been worked out, so I don't have to deal with any of the early BS. But apparently that's not the case with the Pixels. Getting a bit frustrated, but clearly neither Elemental or Franco work with LOS. Any input to a late-to-the-party member would be greatly appreciated :(
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] HesThatGuy:
You're either going to have to run the stock LOS kernel the has the SDCardFS commits or you're going to have to switch ROMs and use whatever kernel you want.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SkandaH:
[MENTION=3710876]joeski27[/MENTION] [MENTION=2438439]rockingondrums[/MENTION]

To be precise, the situation is applicable for every devices where there is no separate /recovery partition & the actual recovery is a part of the boot image. In the early days, Sony devices with the legacy S1 bootloader are the only one with this design. Lately with Pixel (XL), Google adopts the similar design & officially cut the separate /recovery partition from the design.

In case of 2011 & up Sony (Ericson) devices, developers can bundle whatever recovery they want along with the boot image. Later TWRP devs found a way to utilize the (apparently useless) /FOTAKernel partition (in 2012 or later Sony devices) to store the recovery image separately so that users can have the freedom to choose & flash the recovery other than the choice of the kernel devs.

In case of Pixel (XL), devs have chosen to stick with Google's concept as more & more new devices are gonna follow the same design & the legacy process of installing OTA will be no more.

Regarding the Lineage OS specific recovery, it's the same thing from CyanogenMod days. While compiling CM/LOS, you can opt to compile the recovery as well as recovery is nothing but a modified boot image. It can still be possible to taste it out by manually patching your stock LOS boot image using applypatch binary with /system/recovery-from-boot.p patch file (if present) or compile from scratch.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joeski27:
Having an issue now where it seems that every time I reboot the phone (just standard reboot) it ends up booting to recovery (TWRP)...and when I get to TWRP, I try to reboot system and it just reboots to TWRP again. The only way to fix it is to reflash the rom, gapps, etc. What could I have messed up in my last rom flashing process? I typically flash LOS nightly rom, then gapps, then SuperSU, then TWRP, then bootsigner (v8), and then reboot system. Now sometimes SuperSU doesn't stick and I don't have root, which is easily fixed by going back into recovery and flashing SuperSU again (have no idea why this happens either). But what is up with this - am I just not flashing things in the appropriate order here?

Edit: and by the way, the above TWRP flashes are taking place using TWRP recovery installed on the phone, not via booting to the TWRP image in fastboot. (Does this make a difference?)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Namelesswonder:
I haven't had issues with being forced into TWRP for over a month now, but I would make sure your flashing process is alright.

Make sure you only flash ZIPs while on TWRP RC2.

After flashing the ROM you should flash the TWRP installer and then reboot back into the recovery so the active slot can be updated.

If SuperSU still gives you issues I would recommend rolling with LineageOS's su.

You don't need to flash verified boot signer as the checks in the bootloader have been reversed going on several months now.

I have tried waiting it out, hoping that maybe an update one day is going to fix the issue, however even on the latest build it is still happening and it's been many months that this has been happening.

I've been meaning to bring it up with [MENTION=2385005]invisiblek[/MENTION] but I don't know how to file an issue and lately I've just been lazy as the alternative of manually selecting each app to hide the navbar on has worked just fine.

And clearing all decent apps doesn't fix the issue, it's got something to do with the lockscreen I think becoming the active and on top app while locked and for some reason it just does not like immersive mode being forced on it at all.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] General_Tso:
I noticed there hasn't been a nightly for a while. Is all well with the unofficial build? Thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Exelios:
How do I get to TWRP? Power + volume down gets me just to ram dump
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] invisiblek:
I just uploaded a marlin build (sailfish on the way shortly) that should address the bluetooth issues that have been going on lately. It's using a completely AOSP-based bluetooth stack rather than the caf one in mainline Lineage which hasn't turned out to be too good on the pixel.

I doubt I'll be uploading any more builds for N for either of these (barring any major bugs being found).

EDIT: sailfish build is up
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jeffyh:
The man! Thanks for addressing this as a goodbye to lineage pixel N.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] veti:
this will be good for oreo to support the build in bluetooth codecs.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] m2thedeep:
I'm seeing some radio issues with my Verizon Google Pixel. What's the proper way to flash-all before flashing this ROM? Use the files from NHG47Q but the vendor.img from NJH47F?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] invisiblek:
Always use everything from the AOSP version that matches the fingerprint found here: https://github.com/LineageOS/android_device_google_marlin/blob/cm-14.1/lineage.mk#L22

Except boot, recovery and system.

On another note: I'll be rolling another build relatively soon. Verity was on for that last build (whoops, I had re-synced and was using the Lineage kernel branch instead of my personal one). I also want to include the patches for BlueBorne, so I'll probably wait until the 7.1.2 Sept security bulletin tags drop. In fact, I'll probably upload a build monthly for the security releases, at least until I make the jump to O.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] General_Tso:
How does someone do this? I didn't follow this process when I first installed Lineage. I haven't had any issues, but I do see a "wrong" fingerprint error when I restart... Are the two connected?

Edit: Actually, I'm pretty sure I was overthinking this. Just download 7.1.2 (NJH47F, Aug 2017)?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Colday96:
Why doesn't the google pixel get an official version of lineage os ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Shadoukun:
Has anyone managed to build LineageOS 15 for the pixel/pixel XL yet?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] invisiblek:
The main reason is because invisiblek is a lazy piece of sh!t and hasn't got around to finishing sepolicy for backuptool for A/B. Official lineage cannot ship with gapps like these builds do, so when you install a separate gapps package, we need a way to retain it between rom updates. That's currently not possible on A/B.

My lineage-15.0 repos for device/kernel/vendor should get you a build, but I have no idea if it boots or if anything is broken. Feel free to test it and let me know.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Colday96:
So it is possible but you just need a lot more time ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] plittlefield:
Hi Folks,

I have read different ways to do this so I am just checking the easiest procedure.

Model: Google Pixel (sailfish) 32GB

Android Version: 7.1.1 STOCK

Android Security Patch Level: December 5, 2016

Baseband Version: 8996-012511-1611190200

Kernel Version: 3.18.31-gbd96fbf Mon Nov 7 20:29:14 UTC 2016

Build Number: NMF26Q

Rooted: SuperSU 2.92

Recovery: TWRP 3.0.2 RC1

I would like to change to LineageOS (which I have on my Nexus 5 hammerhead) and was going to do the following:-

- download lineage-14.1-20170915-UNOFFICIAL-sailfish.zip and open_gapps-arm-7.1-nano-20170915.zip

- reboot into existing TWRP

- wipe cache, system, data

- install ROM zip

- reboot into existing TWRP again

- install Open Gapps zip

- wipe cache

- reboot system

Is that all absolutely correct?

Thanks,

Paully
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] johnciaccio:
Any version of Lineage OS for the Pixel XL without gapps? Looking to get away from Google's apps completely.

Edit: Or really any AOSP roms without Google apps.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jasonsamms666:
Gapps is baked in. And flash TWRP after the ROM or you will lose it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] plittlefield:
Nice, and thanks for the TWRP tip.

So, the procedure is now...

- download lineage-14.1-20170915-UNOFFICIAL-sailfish.zip and adb push

- download twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip and adb push

- reboot into existing TWRP

- wipe cache, system, data

- install ROM zip

- install TWRP zip

- wipe cache, dalvik

- reboot system

That all look good?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jasonsamms666:
Just put the ROM and TWRP installer on your phone.

Wipe cache, system, and data.

Flash the ROM, flash the TWRP installer right away.

Then boot into your system. If you get a message about a vendor mismatch find your vendor and flash that.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] plittlefield:
Sorry, newbie alert... I don't know what vendor means.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jasonsamms666:
If you read the op. It will tell you what vendor to flash. In recovery choose flash image where it says zip. Choose image. Then find your image and check vendor.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] plittlefield:
Got it, thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jasonsamms666:
Cool beans ?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] plittlefield:
Is this ROM for sailfish good enough for a daily driver? I need phone, wifi, camera to work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] patroll:
Have anyone managed to install this rom + Magisk + Adaway? I get ramdump after giving rights to Adaway, updating host files and rebooting.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] admiralspeedy:
Delete this pls
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] General_Tso:
Hey, is anyone having any issues with Google Play Services after flashing the latest update? Mine keeps stopping.

Edit: Looks like the latest build is minus Google Apps... Just FYI. I reflashed from scratched and noticed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cb474:
I don't see anything in the OP about the vendor. Am I missing something?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jasonsamms666:
Maybe I'm wrong but with every new security patch, there is a new vendor image. I haven't flashed a ROM on my pixel that didn't need a vendor.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cb474:
I just meant I don't see anything in the OP of this thread about how to download and install the vendor. I didn't mean you don't need it. You wrote:

But I don't see where in the OP it tells you what vendor to flash, etc.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] patroll:
There is no information about the vendor in the OP.

The correct vendor is NJH47F. Download the corresponding stock, unzip and you find vendor.img and flash it in the TWRP.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] starcitizen:
Are critical bluetooth and wifi vulnerabilities fixed in the latest nightly build ?

theverge.com/2017/9/12/16294904/bluetooth-hack-exploit-android-linux-blueborne
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
If I remember rightly already merged into LOS 14.1
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] invisiblek:
Yes, blueborne was patched weeks ago and krack is patched in the latest build.
[Xiaomi Redmi Note 3 Questions & Answers] jaanam alag:
i want to change emoji of my redmi note 3. i have applied the notocoloremoji.ttf and made an .mtz file from ifont app when i apply that font that font is not visible there is just a transparent screen. the emojis are changed but the text is not visible. please help me what should i do. i hate the google emojis i want to change them please help.
[Note 7 Questions & Answers] neavissa:
... but how can I use my Note 7 again? I never installed the "Stop the 60% battery limit", and I had it off for month now. I am afraid to turn it on, because supposingly T-Mobile will automatically, no matter what, install a "Brick this Phone NOW" update. At least this is my understanding.

That said. The hardest part is, that I do not have the time, nor the "understanding", to filter through a thousand post, "deciding" what is useful info and what is not. As great as this site is, it is also the downfall for someone like me. :mad:

So, if someone out there feels like wanting to be my HERO, please tell what to do. Even though you probably did it already a thousand times in this forum before, be my Obi Wan Kenobi and guide me in the right direction. :o

Thanks,

G
[Note 7 Questions & Answers] waterpass:
https://www.note7alliance.com/app.php/page/where-to-start-checklist

---------- Post added at 06:16 AM ---------- Previous post was at 06:14 AM ----------

Works 100% just read how to
[Note 7 Questions & Answers] neavissa:
Damn, that was fast! Thanks. You are my Hero! Seriously though, I really appreciate the link!

G
[Note 7 Questions & Answers] waterpass:
Anytime pm me if you have troubles
[Note 7 Questions & Answers] neavissa:
Copy that. : )

Thanks again,

G
[Samsung Galaxy S8 Questions and Answers] Infiniteey:
Hi, just want to double check with other users about the Picture size/ratio of the Whatsapp Camera.

On my S8 it is currently 1:1 even though the camera is 4:3, is this the same for everyone? Can you change this?

No biggie, its just annoying me a little, as I swear it was 16:9 on my S6.

:eek::eek::eek:

Also when i rotate the camera to landscape, the picture is still 1:1 and the camera rotates in the opposite way.... then crashes...

I'll upload pictures if anyone wants
[Samsung Galaxy S8 Questions and Answers] Infiniteey:
Screenshots
[Samsung Galaxy S8 Questions and Answers] zazolo:
me too on s8 and a friend of mine with his s8+