No, this was on me, I have updated my release process to include extra checks.Thank you! And thank you @tasoskio for providing crash logs.
And duly noted for the future - I'll wait to update if I'm going to bed, so I'll be awake enough to capture crash logs to help with troubleshooting. That was on me
[OFFICIAL] LineageOS 20 for the Google Pixel 4 XL
- Thread starter npjohnson
- Start date
GROOVYJOSHCLARK
Senior Member
You can roll back to previous LOS with a factory firmware with -w in the flashall.bat then roll back to previous LOS.
GROOVYJOSHCLARK
Senior Member
For anyone in the future, OR wish to rollback ASAP, follow this method and it works 100% but you will data loss!!!
Using Google's factory firmware is all you need! Use the factory firmware with -w will allow the rollback for anyone rushing to restore LOS (use coral-tp1a.221005.002.b2-factory-db99b1f8) factory firmware. BACKUP EVERYTHING PRIOR as you will LOSE IT ALL (if you don't backup PRIOR to the -w batch), then factory reset using recovery, then flash the batch (flashall.bat) with -w wipe left in, reboot (or it will reboot on its own when done), then bypass all setup, reboot to BL, start over with LOS (using the previous week). I am back rockin LOS using this method!
* I erase /system /data in fastbootD, but this is optional, I do it so I always have a clean /system base, but a factory reset is enough for most users!
Last edited:
GROOVYJOSHCLARK
Senior Member
Please confirm when you take the OTA (official LOS) and it works with the latest 3/26 ver so we all know and can update to it (launcher/services fixed). I am asking only users who used the 'Official LOS OTA Updater' and did an OTA update from a previous version (and it works afterwards). Please confirm the services and launcher issues are resolved with the latest official OTA (when a user has successfully done an OTA update with the fixed update).
GROOVYJOSHCLARK
Senior Member
Perfect thanks! I didn't want to test and find out I'm rebuilding again, after just rebuilding
hell no lol.
That's the worst security bypassing measure I've seen - SU does not, and by security model, should not use kernel mode assistance.
I'm staunchly against that as a commonly used concept.
Yeah, you're going to need to figure that one out, we don't really do anything to bypass safety directly
You are rooted? If yes then search universal safetynet fix by displax pass it ... working gpay and play store are certificate
No I'm not rooted and just factory reset after taking the March 26th update. Does it just not work anymore?
Is there any way I could get the Pixel fonts as a flashable zip, or magisk module? Or perhaps a guide to replace the fonts using root explorer? Every magisk module I've tried off of xda seems to be changing it to a single font (i.e bold, italicization etc, is all ignored, and replaced by a single regular font which is applied system wide, no matter the formatting of the original text.)
GROOVYJOSHCLARK
Senior Member
Thank you my brother!! It worked!!
Everyone else, I took the plunge and tested OTA from the previous version and it works perfectly fine now!! You're safe to OTA if you so choose!
Last edited:
GROOVYJOSHCLARK
Senior Member
GROOVYJOSHCLARK
Senior Member
I wrote a lot about this and how to fix it, in this thread, but I use ROOT, SafetyNetFix, LSPosed, and MagiskProps, then I enable options 1 and 2 (only those two options are used, don't enable any others), then force both options 1 and 2 to use Google Pixel 4 XL A12, then wipe play store data, reboot, open play store and test. You should become certified in play, and pass SN (then Netflix will show up along with Hulu and such).
This is all with ROOT, I don't know what you should do if you don't plan to ROOT and your BL is locked with a Google factory firmware applied. If you have done all 3 (lock BL, factory reset firmware, -w WIPE /data) and its still not working, then who knows what happened. Make sure you backed up everything prior, then go through the lock BL, and factory firmware with the wipe left in the flashall.bat file from the firmware. If you do all 3 (BL lock, factory firmware, wipe data) you should be solid and NF shows up in Play, bank apps work, and so on.
Without ROOT, make sure you do all 3 things to make it re-official Google device, then let us know if its resolved or not. The other option would be to ROOT, then bypass ROOT for the bank apps (hide ROOT in MAGISK with DENYLIST).
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
I meant I just installed this ROM today but now that I'm reading my post it says *I just it installed the wrong way*. Lol no I installed this ROM correctly. I haven't flashed around in years unlock the bootloader I flashed the DBTO.img, I installed the recovery and then side loaded your unofficial build. All of the clean flash. I provided a screenshot of what my QR code scanner tile looks like.1
Ooh now I get it xD
I think that I'll install this ROM again today, then I will verify if the QR Scanner tile stays in the same status as yours. I am not sure how the tile works, but is it supposed to launch an app (e.g. Google Camera)? If that's the case, check the app permissions for notifications and/or other that might be needed.1
Yeah, that file should not be needed (just the recovery img and the ROM zip).
No problem, it is easy to forget some things if we keep away from the custom ROMs for a while xD. Have a great day!1
The tile is not there by default. You have to edit the tiles.
With that said, I have never used the tile before, but just added it to test and it also says "Updating". QR codes still work with the Lens app or Lens feature of the camera. It's just a bit slower to get to.1
Thank you for your response & I'm really liking this ROM. I'm impressed -
15
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 20 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.
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!
7
Wow. Threaten me right off the bat with contacting moderators?
Hilarious. Stuff like this genuinely makes me dislike doing this.
Let me address these individually:
1. The official kernel source I link is the /only/ one there is - and I might add - the kernel is the only one that is a GPL component that has to be released.
2. For your information, by choice, not by license, all sources for the official AND unofficial are public.
Next time you want to threaten someone, do some preliminary research first - this is linked in multiple places - and I will take a moment to say, none of this is legally required to be released as it's all either apache or proprietary licensed, I do the work, structure, package, and publisize it because I believe in FOSS. https://gitlab.com/oddsolutions
3. Seriously - I can't state enough how annoying threats are when it's a hobby - if you'd just said "hey, is there any kernel source difference in the unofficial? If so can I have it?" - I would have just said "No differences, but enjoy all the other stuff I open sourced too!"
That said, have fun, I'm off to enjoy my Thanksgiving vacation
EDIT: One additional piece here - the officials were supposed to launch a month ago - our infrastructure people have been struggling to get signing to work - 20.0 will literally launch randomly some day soon when they figure it out - so I made the threads to get feedback from users ahead of time on device-specific bugs so that when the official launched, I just un-strike through the download link and let people enjoy.4
You are wrong on that point.Hey @npjohnson I am so sorry if you took this the wrong way It was never a threat bro
and never will, I appreciate your hard work and all your doing for the community so please don't take this as a threat rather a misunderstanding, All I want to understand is the link to the source is for linked to official kernel source since you know unofficial builds does not pass safety net and never did so in order to do that framework-base and few other pieace of the source code needs to be modified so all I am saying is the source for the unofficial build should be provided as well jot just official.
Every developer here provides the links to the source code, How is that a threat bro?
If I do something Like this you can tell me the same thing and I would never take it personally and I will always provide links to all the source code.
Everyone has the right to inspect the source code tell me If I am wrong?
From a legal perspective, there is no "right" to inspect source code.
You may want to go read about licenses a little bit. Android - the frameworks and system side, is licensed Apache2 - which just states that you can use it - has no requirement to be published - at all - ever wondered why we don't get source for Samsung OneUI? Because they don't legally have to.
The linux kernel, and a few other pieces of external modules are GPL licensed, which requires release of accompanying source code, which is linked as per the kernel source in the OP to comply with XDA requirements that GPL modules be linked in the OP.
Again, regardless of that - I provide the source code anyway.
I use a tool called ih8sn to pass safety net - if you looked at the link I provided in my last post, you'd see that, and find a link to coral's specific configuration to use with it.
I even provide nice prebuilt local_manifests that you can snag and sync to build this 1:1 with ease.3
Not quite...not all devices can run GSIs, generally only those that are Project Treble compliant
A Generic System Image is just that. It doesn't include a kernel or anything else and is designed to be used with a separate kernel. A ROM on the other hand generally means the "whole package" that includes a kernel. A system image cannot be "booted" as you describe; you can only do this with a boot image, which contains the kernel.
But, this is all outside the scope of this thread.
I try my best to ensure the information I share is accurate, but I'm only human. As far as I'm aware, I haven't stated anything that's untrue or incorrect in this discussion, and I can provide a source for everything I say.
All I'm asking you to do is consider the tone of your messages and how they may be received by others. I'm just here to help people, as I'm sure you are as well. Try to avoid questioning someone's credibility, or telling them what they should or shouldn't share, but rather provide your insight as to why or why not something is relevant.
I don't want to derail this thread any further, so if you wish to continue this discussion, PM me.3
