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.
[OFFICIAL] LineageOS 19.1 for the Google Pixel 4 XL
- Thread starter npjohnson
- Start date
- Status
GROOVYJOSHCLARK
Senior Member
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":
Last edited:
GROOVYJOSHCLARK
Senior Member
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).
Last edited:
GROOVYJOSHCLARK
Senior Member
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):
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.
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.
Attachments
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
@ 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.
@ 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.
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.
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.
@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.
- "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.
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.
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 ETAsWhen will LOS20 be released?
LineageOS doesn't support TWRP, but also, no, a12 will not decrypt with TWRP at the moment. Period.
@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.
- "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.
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.
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
8
Google Pixel 4 XL
Code:- Your warranty is now void. - You have been warned. - Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Google Pixel 4 XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.- coral - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
Known Bugs:
Notes:- None.
- Find any? Report them according to this guide.
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.14- The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
- Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
5Hey all! The final 19.1 unofficial are rolling right now.
From here on it will be 20 builds for these devices only when it comes to unofficials.
The device will continue receiving official 19.1 for some time, but 20 will launch soon enough, so get ready to migrate using the upgrade guides!332
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.
