yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xorrgnlusrx:
Put it in the microwave on high and set settings to high for 1 Minute.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] gigamak:
you better stick your useless head in there
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xorrgnlusrx:
i could not agree with you more !
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
My Gmail ain't loading up my messages can anyone tell me how to fix this issues
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
I'm not a Lineage OS user, but what GApps did you flash? I last use Lineage maybe 2 weeks ago, used NikGApps and GMail worked for me. Just your normal stuff like live caption and some Google Dialer stuff doesn't, but I guess GApps has to be backed in for it to work.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
I fixed it by reinstalling it plus I use mindgapps
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Turn off gestures, active edge (Settings/System/Gestures/Active Edge) or change the default action for squeeze (what you are doing to cause the vibration/screenshot) and your root cause. The default action (squeeze) is to take a screenshot plus the default vibration is to vibrate for system (tech), so this is your cause. Turn off the vibration in sounds (Settings/Sounds/Vibration/Tech), but I personally turn off active edge (no need for me) and all vibrations like the "tech":
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I am the opposite, I ONLY use/run LOS :)

I'd be careful using any GAPPs but MindTheGapps (LOS recommended GAPP) with the current LOS for coral, I had Framework issues when I did. I know because I tested Niko myself (I prefer Niko over MindTheGapps) - well truly I prefer OpenGapps but there's still no 12.1 so I tested NikoGapps and a few others, but only MindTheGapps worked every time through every update. When I used NIK GAPPs, the LOS updates broke all Google Service Framework afterwards, meaning after the OS update, (OTA/reboot), is when the framework broke. It didn't matter if I did OTA or fastboot (same end result) Google Play Framework destroyed.

I rebuilt my device (LOS) a week or so ago (to fix the GAPP Framework issue), and used the recommended, MindTheGapps this time, and no issues. Then last Sunday, I took the OTA (last weekend) to test (after backing up TXTs/MMs/ETC just in case), and it updated the OS/GAPPs Framework without issues to the Framework. I only mention it, so others don't possibly break GAPPs (Framework) with an update (if they used anything other than the recommended GAPPs).

Just my two cents but I have found that MindTheGapps is the best GAPPs for stability on the Pixel 4 XL (through updates). This is true, for today, 9/27/2022 @7:15AM, but it could change any moment (like 5 minutes from now) and be completely opposite, so this is why I ALWAYS urge users to research first. It changes fast, really fast, and if you use outdated info, you can run into disasters, so this is my PSA for today (research research research).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
If LOS is setup correctly (using the recommended LOS GAPP framework), it will work without issues. Make sure you have syncs enabled and should be fine, plus DL/install GMail from the Play Store and update it current. LOS is ALL I use, and I get GMails all day long, so GMail is heavily used on my side, and I have never had a GMail hiccup (ever using LOS)!

Go to Settings/Password and Accounts/Google account (midway down) and select your main Google account. I have 3 Google Accounts, so for my GMail (that I use/care about), I make sure its enabled (on that account only). For the other two Google accounts I have/use (mainly for work), I disable GMail sync as I don't use GMail on them. You can check your sync settings and make sure GMail is selected, and change/enable, and also set the rest but I personally sync everything in my (main) Google account. My secondary Google Accounts are disabled, since there's no need (no inbound/outbound mail is sent/received):
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
Hi,

Just joined the forum. Some history first.

1. Was running LOS 18.1 OVER A-11. ROOTED with Magisk/ everything was smooth

2. Last Sat nite, plugged phone into charger

3. Woke up Sunday and phone now requests "Password required after device restarts" . Could not use phone day. Was on the road!

4. Sun evening, tried to get in phone via linux adb and it told me i could not see the data folder, or nothing. IS the DATA gone?

5. So I tried using TWRP sideload..LOST ROOT and BOOTLOADER locked up - Fixed it though by side-loading LOS lineage-19.1-20220703-nightly-coral-signed but still booting to above #3-Error

6. So ?'s : What happened? Anyone please chime-in

7. I can get into Recovery/Bootloader/ Fastboot/Fastbootd

(see BLUE enclosed Image)/

8. After trying for quite a bit, I just found out I lost root.. "su" is not avail via ./adb shell

9. I just want to

GET-TO-THE-DATA

- IS THERE A PROCEDURE?

10. Reading the thread, I have this on phone:

(see

GREY

similar-enclosed image)

11. @

npjohnson

: I tried to get the 18.1 that I used, but could not find it on the LOS site. However, I have this file ==>lineage-18.1-20220319-nightly-ocean-signed.zip . Is this the CORRECT one for the PIXEL 4 XL.

I do not remember

and If so can I just sideload this OVER the LOS19.1 ?

12. Reading the thread, is there a way to obtain the Magisk A12 patched boot.img from a site? If it can be done, can I sideload it?

13. TWRP is not avail for A12, therefore my italicized question above

14. I just need to get the DATA.

15. Any suggestions or methods to get to the filesystem to mount via adb? Currently it states "Unable to mount Pixel 4 XL"

In advance, many THANKS for any/all assistance.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Syntaxerror_s:
Nightly ocean hmm I think it should be coral I think. Its pretty hard to find 18.1 image. I would upload for you if I had the official, I only have a unofficial build of it
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
Hope this site helps https://lineageosroms.com/coral/
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
Anyone here using the twrp a12 on the 4 xl an how you get the touch working also
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
@ Syntaxerror_s = T.Y., but prefer the 18.1 OFFICIAL build

@ legend876 = ONLY 19.1 shows ; Initially as mentioned I was on LOS

18.1, then I "sideloaded the LOS 19.1--- then installed TWRP(lost-

root) and locked the bootloader. Then fixed it via extract of

payload.bin from LOS 19

@ legend876 & @ Syntaxerror_s : This why I was asking :

(12)........ is there a way to obtain the Magisk A12 patched boot.img

from a site? If it can be done, can I sideload it?

@ legend876 & @ Syntaxerror_s : Then-can try for "root" and "TWRP" for

A12 which should provide "RW" access via console===> ./adb shell

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hi, An Update:

SOME MORE INFO:

A. WAS using this -----> lineage_coral-userdebug 11 RQ3A.211001.001

10041641

B . LOS 18.1 is not to be found? WHY? There should be a section FOR

archive..

C. I am aware that a REMOVAL of "*.key" is a possible solution, but

RW access within ./adb is not functional

D. I even attempted to connect via "wifi": Booted phone/Connect to

house wifi, then using "./adb connect xxx.xxx.xxx.xxx:5555.. but get

error "host refused". Of course in console, "device is unauth.."

In Post #207 I can get into Recovery/Bootloader/ Fastboot/Fastbootd

(see BLUE enclosed Image)/

F: I now see the purpose FOR an external SD card

G: Therefore, my goal is to get "su" from ./adb shell or FIX this:

Currently it states "Unable to mount Pixel 4 XL"

AGAIN, In advance, many THANKS for any/all assistance.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Your post format is a bit wild for me to fully follow, but it seems you're aware of what you're doing and whatnot.

The error your experiencing, I've experienced this multiple times over the past 3-4 months. I really couldn't figure it out either, and this was on other roms, not Lineage. I'd reboot and try to type the password in as fast as possible, sometimes it'd work, sometimes it wouldn't.

Now for accessing the data partition, maybe try flashing stock but don't wipe the device. If you're still greeted with errors, you might just end up screwed and having to fully wipe.

Lastly, I explored the Telegram Lineage group chat for Flame/Coral. I'm going to PM you a link that someone else hosted on their Google Drive, since it's not my link, for Lineage 18.1.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xorrgnlusrx:
are you trying to get the boot.img for 18 los ? or stock ..

you can download the factory image for the devices , un zip , copy boot img, copy onto another devices patch the boot img with magisk, copy back on to computer and re compress the zip using the patched boot.img and flash the stock modified original firmware, although you are not meant to do this it does work, and it would be the same for los.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
@Curiousn00b ==Sorry man! just trying to post as much needed info as poss.

- "maybe try flashing stock" <==initially phone came with A12, and I downgraded to A11 to put LOS 18.1 (Mar-2022).

- Never had a password on device

- So should I sideload the A12 over LOS19.1 ?

- T.Y. for seeking the link.

@xorrgnlusrx : YES, the patched_boot_img, however, for LOS19.1 which is

now on phone

- Your method is interesting; shall consider it and re-read/review it.

- "copy onto another devices patch the boot img"

QUESTION: Can I use A11 and over-write the LOS 19.1. (TWRP) is avail for A11 and LOS 18.1

OR Should I use A12 and over-write the LOS 19.1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

AGAIN, In advance, many THANKS for any/all assistance.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
I'd say yes. I normally flash stock without wiping my /data/ partition when I mess something up on a rom just to recover what I wanted, then fully wipe the device for a fresh start.

If you want, you can try this as a last resort. I know sometimes you just end up in a fastboot/recovery loot about how the system is corrupted and then you're basically forced to clean flash at that point.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] 江灵z:
When will LOS20 be released?🤩
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] npjohnson:
Don't discuss magisk here. It's unsupported. You have a "coral" not an "ocean", just rename magisk.apk to magisk.zip and sideload it. Will work fine..

Why are you using 18.1? Also unsupported.

No, you can't. That would use stocks boot image, you would need to unpack lineage's using payload dumper like the wiki details for extrating blobs.

Just follow the wiki. Seriously. You are way overcomplicating things.

Don't do that. You'll mess up selinux context hard.

No ETAs
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] legend876:
Anyone here got TWRP a12 coral to touch on los19.1
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] npjohnson:
LineageOS doesn't support TWRP, but also, no, a12 will not decrypt with TWRP at the moment. Period.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
@npjohnson . T.Y.

- "just rename magisk.apk to magisk.zip" I cannot access phone

- "Why are you using 18.1? Didn't get around to it

- phone now requests "Password required after device restarts" .

- I cannot get in phone - I never set password

- what is method to get RW access on phone?

- What is method to remove the "password required" nuisance ?

- IS there a method to mount USB-RW in ./adb ?

-My goal is to "backup" the data

- Is there a Win ODIN tool or other SW that possibly remove the password?

- IS there an archive section of LOS to get the 18.1 for coral?

- twrp-installer-3.6.2_11-0-coral is working for LOS 18.1, correct?

-Thats why I am seeking LOS 18.1

AGAIN, In advance, many THANKS for any/all assistance.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] npjohnson:
1. Just rename it on the damn PC lol then sideload it.

2. Alright.

3. You can't. Data is encrypted. You. Snt just decrypt data like that. No clue why you have a password unless you set one or did something weird to corrupt data

4. Again, we don't support TWRP. I wouldn't recommend it.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] digitalcircuit:
@npjohnson

I'm looking to make the jump from stock Android 12.1 to LineageOS 19.1, however, I have concerns about the infamous green tint at low brightness issue.

Manual tweaking with the CleanSlate kernel on XDA has made a significant positive impact for my device's display - it's the only reason I've been using CleanSlate. Around 2020-10, I tried porting the CleanSlate color correction code onto the AOSP kernel, but I never got past the boot animation. I think I messed up the AOSP kernel build config.

Spoiler content hidden.

Does LineageOS provide some means of brightness-dependent color calibration, e.g. "when below 15% brightness apply this R,G,B slider calibration, otherwise disable calibration"?

My Nexus 6 on LOS 15.1 has color calibration sliders in Live Display, but that applied regardless of screen brightness and I think Live Display was replaced with Google's Night Color.

I found one bug report from 2021-9-20 about the green tint which was closed without any mention of kernel workarounds:

90hz Smooth Display - green tint - Pixel 4 XL coral (#3987) · Issues · LineageOS / issues / android · GitLab

Expected Behavior Setting should only affect refresh rate. Current Behavior Setting affects...

gitlab.com

I realize this is a workaround at best and I'd understand if this is too much effort to implement and maintain. And regardless, thank you for the effort on shamu (I plan to upgrade it to 18.1), and coral!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xorrgnlusrx:
yeah thats what i meant , i was being brief.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xorrgnlusrx:
./fastboot oem setbrightness ??? ./fastboot oem display_color .. maybe you could change something with those commands ?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xorrgnlusrx:
do you want to patch stock android 12 firmware boot.img ?, i can send you a12 stock firmware patched boot.img / or los 19 stock patched boot.img if that helps.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
@xorrgnlusrx = YES, GOAL = accessing the data partition .​

(do you want to patch stock android 12 firmware boot.img ?, i can send you a12 stock firmware patched boot.img / or los 19 stock patched boot.img if that helps.)​

& Curiousn00b suggested: "Now for accessing the data partition, maybe try flashing stock but don't wipe the device. If you're still greeted with errors, you might just end up screwed and having to fully wipe." " I normally flash stock without wiping my /data/ partition when I mess something up on a rom just to recover what I wanted, then fully wipe the device for a fresh start. If you want, you can try this as a last resort. I know sometimes you just end up in a fastboot/recovery loot about how the system is corrupted and then you're basically forced to clean flash at that point.​

I found it logical, so I tried it: Here are steps performed:​

Was running LOS 19.1

booting to requesting password:

1. Fastbooted files FROM A12.stock.. coral-sq3a.220705.003.a1-factory-7d161018.zip

2.

Below are steps don

e: taken from site: (IN YELLOW)

POST#1 - ITEM 4===>KEEP-DATA: From BOTH sites/links

https://xdaforums.com/t/guide-root-pixel-4-xl-android-10-q.3996969/

https://xdaforums.com/t/guide-root-pixel-4-xl-with-magisk-android-13.4160441/

3. extracted zip file

4. Remove -w from flash-all.bat and flash-all.sh (DID NOT factory reset/wipe data)

5. Copy/Moved these files to the Platform-tools folder:

bootloader-coral-....img

flash-all.bat

image-coral-....zip

radio-coral-....img

6. booted to fastboot

7. batch file did not work- bcuz it gave error stating not valid fastboot and to get lastest versio of platform tools, which is what I'm on = platform- tools_r33.0.3-linux

8. ran

a. fastboot flash bootloader bootloader-coral-c2f2-0.4-8351033.img

b. fastboot reboot-bootloader

c. fastboot flash radio radio-coral-g8150-00123-220402-b-8399852.img

d. fastboot reboot-bootloader

e.fastboot update image-coral-sq3a.220705.003.a1.zip

when it finishes, google starts loading, then defaults into the boot-loader.../fastboot menu.

DURING Step "E", I ALSO get a an option to go into a "recovery" menu and step "E" fails when entered "recovery" menu.

?A: is this because of the non-patched boot.img in the platform folder?

?B: should I attempt to fully side-load the A12 stock.zip file?

@xorrgnlusrx = PLEASE ALSO SEND YOUR INSTRUCTIONS

AGAIN, In advance, many THANKS for any/all assistance.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Syntaxerror_s:
At this stage I think you are just trolling.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Syntaxerror_s:
Modify the bat script and remove the lines containing which fastboot is required, remove all the lines above, fastboot flash etc, if you can't modify the bat script , run on Linux and modify the flash all .sh and remove what was mentioned above, if that doesn't work , flash radio / bootloader in fastboot , reboot into bootloader and run fastboot reboot fastboot, this will boot you into fastbootd from there run fastboot flash update image-coral-sq3a.220705.003.a1.zip,

If that doesn't working unzip the zip and flash them all manually , ie . fastboot flash system *system.IMG* etc etc ..
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Syntaxerror_s:
If you cant boot into fastbootd , run

Fastboot boot *linagerecovery.zip*

From there you should be able to run fastboot reboot fastboot. And you should be in fastbootd where you can manually flash all that is contained within the zip. I would try fastboot flash update *example.zip* first before manually doing it. Anyhoo , a multitude of ways to accomplish this simple task.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Syntaxerror_s:
You might be able to adb pull once you temp boot recovery
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I agree, this is some of the craziest steps taken (and none of them should have been done). I have no clue what this user did because its written like a zodiac cryptogram. We can help, but you gotta listen and stop trying so many things randomly and without warrant. If you want help, tell us where you are now, what's the status, what have you done/undone to fix this?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
@Syntaxerror_s...Huh..trolling NOT...just seeking help..which you gave some good methods.. THANKS...shall try it..​
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
@GROOVYJOSHCLARK..Absolutely not..Give me slack dudeThe point was to share the issue & what procedures I performed.​

The error: "Password. requires after device restarts" showed no solutions except for a posting with A8..when supposedly TWRP worked.

I was on Los 18.1..now I cant even find it...Therefore other methods had to be tried, since not one post effectively addressed the error but only in variables...
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] insestito:
Do this

Android Flash Tool

flash.android.com
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Sorry man, I didn't mean to bash, I just can't follow the weirda$$ layout you use (all over the place with quotes/replies that made it really hard to follow) at least for me. It did seem like you were just posting a lot of random things, to sound like questions, so originally it did come off troll'y. I didn't mean to upset, but I also have ZERO clue where you are now, and what's left to do (what's the goal)?

At this point, if you can't get into the OS, then I would try to get any type of OS loaded, just to pull out my data using ADB (or any means possible). Meaning, I have no idea what you are trying to do now (other than fix it) but I don't know where you are physically, what ROM is loaded, what OS is loaded, can you get in to anything, will it boot, what happens when it boots, where is it hung up, ETC?

My goal/focus would be to load any OS, but without causing further damage to the /data partition (so you can backup and save everything) then wipe it and start over and restore the data. If you want my help to do this, I need answers, but clearly laid out so I don't guess, or get a headache trying to follow the flow.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Well guys, I can vouch for him with the whole random password thing happening. It's happened to me a handful of times where I've rebooted my phone, and the password I set just would not work whatsoever after days/weeks of using the phone fine. I couldn't get to the bottom of it either, but luckily whatever I had on the phone wasn't super super important since I backup my SMS everyday, and use Google Photos for pictures.

At random times, I'd reboot and type the password in fast enough and it'll unlock normal, and sometimes it was just a dead end. The password the phone would be looking for was N/A, and on top of that, no matter how many times you typed it in wrong, there was no cool down for it. I was just able to infinitely guess the password wrong without it locking me out completely. 😅

@xdadottts In the end dude, you might be screwed and have no choice but to factory reset to get your device back running properly.

On a side note, pre-ordered the Pixel 7 Pro, so my time in the 4XL is limited now.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
@GROOVYJOSHCLARK & Curiousn00b​

- load any OS - nothing would load until factory reset..now have A12 loaded...​

THANK-YOU ALL FOR THE ASISSTANCE!​

Are there other ROM's besides LOS19.1?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] npjohnson:
Please only discuss lineage on this thread. You've talked about so much random stuff.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] MJPollard:
I didn't grow up in the Sixties, but reading those posts with all those different colors and font sizes gives me a small idea of what an acid trip must feel like. :ROFLMAO:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ralfbergs:
Pardon my ignorance, but does that mean I absolutely must install Magisk before Official LOS will be able to pass SafetyNet?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Pretty much, but I do think that the version in the OP with Google Apps baked in might have the fix. Not 100% sure on that, but the module that currently works no problem is this one below.

Release v2.3.1-MOD · Displax/safetynet-fix

SafetyNet & Play Integrity API workarounds for Magisk - Release v2.3.1-MOD · Displax/safetynet-fix

github.com
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xdadottts:
Running: LOS ver: 19-20221002-NIGHTLY-coral & rooted

@npjohnson or Super Devs:

Is it ok to lock the bootloader after root & post LOS19.1 ?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ralfbergs:
Yeah, but it's not the "Offical LOS" build, as the OP writes themselves:

Thank you, but I would like to use an "bfficial" build and not tinker with it by any means, because it's for my wife who is very untechnical. It should "just work."
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xorrgnlusrx:
im using micro g / los 19 and pass safety net, not sure why it says its not supported, but its working, initially was going to use mindthegapps but didn't have internet at the time and only had micro g, turns out it works fine.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I would definitely NOT re-lock the BL! This is a custom ROM, not stock, so you risk locking yourself out with data-loss but up to you. I wouldn't do it though, not a chance in hell, but if you must re-lock it, and you want a ROM like that, Proton lets you lock the BL. But again, I would NEVER do it with a custom ROM (even proton). WHY, WHY risk it?