ROM ❯ PIXEL 2 XL ❯ OFFICIAL ❯ ProtonAOSP 11.3.0

[hfmls]

I have an issue. I cant open clock app and when i try to install Google one it bugs

 

[GROOVYJOSHCLARK]

I have an issue. I cant open clock app and when i try to install Google one it bugs

Doesnt happen here on my Pixel 2 XL (running Proton), using the native, built-in clock app. I set my alarms like normal without issue. What is your install process and what add-ons have you installed (MAGISK/KERNES/MAGISK MODULES/GAPPs/ETC)? I suspect its something you added or otherwise edited out of the standard ROM. It works lovely for me so without the ability to reproduce it, I cant assist solving it, but I would review the process you used and what was installed. Its possible an overlay is just crashing the app.

 

[hfmls]

Doesnt happen here on my Pixel 2 XL (running Proton), using the native, built-in clock app. I set my alarms like normal without issue. What is your install process and what add-ons have you installed (MAGISK/KERNES/MAGISK MODULES/GAPPs/ETC)? I suspect its something you added or otherwise edited out of the standard ROM. It works lovely for me so without the ability to reproduce it, I cant assist solving it, but I would review the process you used and what was installed. Its possible an overlay is just crashing the app.

Hi, i cleared cache now i can open it. But it detects in store as Google clock but it is the stock. In store says update then gives error. I installed NikGapps macro

I installed Proton without Gapps, and flashed NikGapps, then flashed magisk via fastboot boot twrp.

All seems ok other than clock. I see stock image/app but at playstore it detects it as Google Clock and asks me to update. Instead of installing it side to other app.

 

[73sydney]

Hi, i cleared cache now i can open it. But it detects in store as Google clock but it is the stock. In store says update then gives error. I installed NikGapps macro

I installed Proton without Gapps, and flashed NikGapps, then flashed magisk via fastboot boot twrp.

All seems ok other than clock. I see stock image/app but at playstore it detects it as Google Clock and asks me to update. Instead of installing it side to other app.

Fwiw i used NikGapps Full with config file (which had Google Clock set to replace stock clock by default) and have perfectly working Google Clock thats updated several times correctly

Check your NikGapps zip file, if you explore the afzc folder you should find the nikgapps.config file. In that id be shocked if there wasnt a line that says GoogleClock=1

In the full package its installed by default, dont imagine it isnt in the macro, but im downloading to check

Also i always flash magisk the exact same way, never had an issue and it wouldnt explain this, so dont worry about magisk

Did you:

1) Erase userdata before flashing the ROM (making sure you have a backup of anything you love from internal memory beforehand)
2) fastboot boot trwp
3) flash the ROM
4 )reboot to bootloader
then
5) fastboot boot trwp (again)
6) flash NikGapps
etc

That reboot after flashing the ROM is important


Other than the above tips, i have nothing to explain it

 

[Green-Bot]

Do not flash TWRP. Just fastboot it. Flashing TWRP in Android 11 causes issues. You can't install Proton with the stock recovery.

Just to be sure, fast booting the TWRP should be done using the .IMG file only rather than using .ZIP file. Using zip file will install it permanently? If I use command "fastboot boot path/to/twrp.img" file, it should be good, right?
Also, is there a guide/article to follow since I am stock 11 rom. And I am a bit confused whether to start with root my device first or Fastboot TWRP or install Magisk or install ROM. etc. Sorry for asking help here but it seems checking multiple articles has confused me I want to start from 100% stock 11 ROM to go ahead and install this ROM with OGapps......not sure about the correct steps/path.

 

[73sydney]

Just to be sure, fast booting the TWRP should be done using the .IMG file only rather than using .ZIP file. Using zip file will install it permanently? If I use command "fastboot boot path/to/twrp.img" file, it should be good, right?
Also, is there a guide/article to follow since I am stock 11 rom. And I am a bit confused whether to start with root my device first or Fastboot TWRP or install Magisk or install ROM. etc. Sorry for asking help here but it seems checking multiple articles has confused me I want to start from 100% stock 11 ROM to go ahead and install this ROM with OGapps......not sure about the correct steps/path.

Correct, only fastboot twrp

And yes the cmd is fastboot boot path/to/twrp.img


This is the way i did it, from a fresh stock 11 flash pretty much as i do every ROM

I used NikGapps full, but you can substitute Open-Gapps (warning, theyre horribly outdated) for the same steps...

The following assumes you have the platform tools and the ROM, NikGapps/G-Apps and magisk in the same folder OR you have the platform tools in your PATH....

1) backup anything you love/need on internal storage
2) enable usb debugging via developer options

All following commands at command prompt in platform tools folder OR from folder with ROM etc and platform tools in PATH

3) adb reboot bootloader
4) fastboot format userdata

Note: this will erase userdata, hence the earlier prompt to save anything on internal data you love/need..

5) fastboot boot twrp-xxxxxxx.img
6) adb push proton-aosp_taimen_11.2.0.zip /tmp
7) adb shell twrp install /tmp/proton-aosp_taimen_11.2.0
8) adb reboot bootloader
9) fastboot boot twrp-xxxxxxx.img
10) adb push gapps-xxxxxxxx.zip /tmp
11) adb shell twrp install /tmp/gapps-xxxxxxxx.zip
12) adb wipe data
13) adb reboot system

Complete setup, and enable USB debugging in Developer Settings

And for magisk.....

All following commands at command prompt in platform tools folder OR from folder with ROM etc and platform tools in PATH, again

1) adb reboot bootloader
2) fastboot boot twrp-xxxxxxx.img
3) adb push magisk-xxxxxxx.zip /tmp
4) adb shell twrp install /tmp/magisk-xxxxxxx.zip

 

[GROOVYJOSHCLARK]

Hi, i cleared cache now i can open it. But it detects in store as Google clock but it is the stock. In store says update then gives error. I installed NikGapps macro

I installed Proton without Gapps, and flashed NikGapps, then flashed magisk via fastboot boot twrp.

All seems ok other than clock. I see stock image/app but at playstore it detects it as Google Clock and asks me to update. Instead of installing it side to other app.

I only use OpenGapps, not Niko and do not have any issues like you face, I can't reproduce it with OpenGapps. I try (and tried) to push all users to use a single GAPP package to avoid this type of issue, but users are free to do and listen to whatever advice they wish. The problem with this is that I cant assist when I cannot reproduce the said issue, so I cannot really help here. It works fine for me, but I used OpenGapps only, and nothing else.

On that note, it is important to say that I am just about done with my 2XL and supporting custom ROMs for the 2XL. With the 2XL being dropped from Google, there's no need for me to support it any longer. I plan to sell off my 2XL and 3XL to buy either the 4 or 5 (I haven't decided yet which one), but only from Google so it will be an outright purchase. This means whatever is cheaper and more reasonable when I am ready to buy it will be my deciding factor.

All that to say this, I am about to remove all custom ROMs and code from my workstations and roll my 2XL into the last 11 official ROM and prep it to sell off. This means I wont be reproducing anything for anyone anymore, and will eventually stop my posts in the 2XL within the next few weeks, then finally drop and stop supporting the 2XL forums for good altogether. It may be sooner, but it may be after Christmas, it all depends on timing and what's available when I am ready to jump off. I am only going with Google, so it will be a pixel variant of some sort but once I move to another device, I will drop out of the 2XL forums and move to those forums to support users there. I know at least one user will be happy to hear this I will be available for the next few days/weeks but I may not be running a custom ROM much longer on my 2XL.

 

[73sydney]

Please, stop spreading misinformation about Nik Gapps, again...we went through this like 2 days ago....please stop it

I know you like to come in, contradict my posts to troll me, but youre misinforming members about the hard work of devs on here, and thats an entirely different thing from being a troll and bully and picking on me

Also advised the Nik Gapps team that youre spreading malicious information about their work.

Please for the last time leave me alone, i come here to purely help people, not be victimised by you and your ego. Youve be warned enough to stop.

 

[karandpr]

M'Kay, I don't even know what to say.
Use whatever gapps you want.
Whatever works works. If Nik gapps don't work, use open gapps, if Open gapps don't work then use Nik Gapps.
If both don't work then use microg.

Moderators are already over-burdened with the migration & spam attacks so we hope you will keep aside your differences for few days.

Good day Peeps.
- XDA Staff

 

[73sydney]

Just for extra choices when it comes to G-Apps folks, noted dev for our device @Eamo5 posted on another thread that there is a known issue with OpenGapps under certain circumstances which may manifest itself in apps like Google Maps crashing on open. as he notes, and as i pointed out the other day when recommending a different G-Apps, Open G-Apps is not updated regularly in test phase just after a new major release comes along, and is quite out of date at the moment.

[ROM][UNOFFICIAL] Lineage OS 18.1 for Pixel 2 / 2 XL [January 8, 2021]

When will it be getting official and updated to December patch?

forum.xda-developers.com

And so, as he posted in link above, you can try also try Razorloves Gapps nano here as flagged by him:

https://sourceforge.net/projects/razorloves-lineage/files/gapps/open_gapps-arm64-11.0-nano-20201121.zip/download

A Gapps Nano package is generally viewed as the most safe package for G-Apps as it contains just the basics, with any additonal apps available from the Google Play Store

So trouble free G-Apps options at time of writing are:

RazorLoves Gapps:
Download folder (various package sizes ): https://sourceforge.net/projects/razorloves-lineage/files/gapps/
Recent build (nano): https://sourceforge.net/projects/ra...n_gapps-arm64-11.0-nano-20201121.zip/download

Nik-Gapps:
Download folder (various package sizes ): https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/
Recent build (omni - equiv of nano): https://sourceforge.net/projects/ni...ps-omni-arm64-11-20201122-signed.zip/download
Support site, faq and documentation: https://nikgapps.com

 

[2x4]

hey guys been away for a few years but interested in this ROM - what's the flashing process for ROMs on the Pixel 2XL? i've been reading it's different due to the A/B partitioning so no traditional permanent TWRP?

 

[73sydney]

hey guys been away for a few years but interested in this ROM - what's the flashing process for ROMs on the Pixel 2XL? i've been reading it's different due to the A/B partitioning so no traditional permanent TWRP?

One way is explained by me above, that's the general way I flash ROMs, but always read the opening post of each ROM thread for specific steps in case of specific needs

And yes, when you first come to an A/B device, it feels a bit weird not flashing everything in one TWRP session, when you've been doing that for eons....but the reboots between ROM flash and G-Apps is to switch to the (new)active slot (A/B) before installing G-Apps. Feels weird the first few times...

 

[phantranphuc]

Using opengapp version of this rom for few weeks in my main phone. No issue at all in performance and battery. Google pay and paypal work fine. But today I faced an issue:

It is first time I use my credit card to make payment for online shopping (I used to use paypal). Payment went through no problem and transaction appeared in my bank app. However the store cancelled my order straight away due to fraud detection. It is ok when I used my ipad. Not sure it is rom issue or other. I reckon it is because I used MicroG.

Anyone knows the reason or have same problem?

 

[73sydney]

Using opengapp version of this rom for few weeks in my main phone. No issue at all in performance and battery. Google pay and paypal work fine. But today I faced an issue:

It is first time I use my credit card to make payment for online shopping (I used to use paypal). Payment went through no problem and transaction appeared in my bank app. However the store cancelled my order straight away due to fraud detection. It is ok when I used my ipad. Not sure it is rom issue or other. I reckon it is because I used MicroG.

Anyone knows the reason or have same problem?

"I used MicroG"

 

[Yourboymusti]

Hi guys,

Installing Magisk doesn't work at all. I've held off posting here and read everything, followed all the advice (idk how the multi-quote thing works or if it will but I've done it).

fastboot to twrp and to flash the zip doesn't work but that method wasn't working on stock either. The main method of fastboot flash boot magisk_patched.img doesn't work too. adb push doesn't work too.

I followed GroovyJoshs advice (which is godly btw) and TWRp doesn't throw any errors anymore. After the clean installs and multiple formats, there are no module files in Magisk that stopped booting up like when android 11 first released. I'm not a complete noob, I've tried everything but this beyond me. I can provide any info that may help - just ask.

Ty,
Mus

edit: the posts I'm talking about are attached to the post below.

 

[Yourboymusti]

fwiw i just installed and this is the way i did it, pretty much as i do every ROM

I used NikGapps full (because open gapps currently only has a nano 11 package, i normally use Aroma, this is a as close as you can get to full gapps now) and had my custom config file under sdcard/NikGapps - i like to cherry pick whats installed

adb reboot bootloader
fastboot boot twrp.img
adb shell rm -r sdcard/Android (leave the rest of sdcard alone, avoid wiping everything, ymmv)
adb push proton-aosp_taimen_11.2.0.zip /tmp
adb shell twrp install /tmp/proton-aosp_taimen_11.2.0
adb reboot bootloader
fastboot boot twrp.img
adb push NikGapps-full-arm64-11-20201108-signed.zip /tmp
adb shell twrp install /tmp/NikGapps-full-arm64-11-20201108-signed
adb reboot system

complete setup, and enable USB debugging in Developer Settings

adb reboot bootloader
fastboot boot twrp.img
adb push magisk.zip /tmp
adb shell twrp install /tmp/magisk.zip

reinstalled my apps backup using migrate...

looking good so far!

I used the same process more or less and used the very latest MAGISK zip in TWRP and didnt loop, I did have a loop when I used MAGISK to patch the boot.img, but installing the latest .zip worked fine. I used the ROM+GAPP version, from BL, I ADB TWRP, wiped everything including /data format twice on everything, then rebooted BL and ADB TWRP again, then installed the ROM (ADB push to SD the ROM.zip because we previously wiped SD), then once the OS is installed, I wipe everything a second time (because now the partitions are correct, I.E vendor) so TWRP doesn't throw the errors. Then I reboot to BL again, ADB TWRP, install ROM (with GAPPS included), once ROM is installed, I reboot to system (do not install TWRP app). I then setup the device how I like it to be, then rebooted to BL, ADB TWRP, and installed MAGISK .zip (latest) from TWRP, reboot to system and done. Make sure it is the latest MAGISK since older ones were designed for 10 and not yet 11. The latest version works great for me.

Sorry didn't know I had to insert.

 

[73sydney]

Sorry didn't know I had to insert.

Both posts refer to installing magisk the exact same way (in fact i always flashed the magisk zip as it knows its job, and flashing the patched image had a high failure rate - people usually flashing to the wrong slot...the zip doesnt make that mistake), at the same point in the overall flashing procedure, flashing the zip via TWRP, and NOT trying to patch the boot image

Theres no difference, other than that ive put my post in step by step, line by line format, though for some reason in the middle he does a lot of arguably unnecessary wipes

The method i use is used by many (i.e. ive never claimed i invented it ), i just adapted it to use for most ROMs here i that i test , it uses standard and accepted commands and ive never had it fail on me, ever. Ive flashed 2 ROM's today to test...using that same method

Usually people forget to do reboots after installing the ROM and try and do all the flashes in one session...thats where you can get into trouble. thats why i point out the reboots . People trying to shortcut things often make their own misery...

Im not sure what this means though:

there are no module files in Magisk that stopped booting up like when android 11 first released

there should be no modules in magisk after a fresh install...

The only way im aware of that you can make a ROM not boot with regards to magisk is if you install TWRP and then flash magisk from it, and NOT as advised simply fastboot to twrp and flash from there

 

[Yourboymusti]

Usually people forget to do reboots after installing the ROM and try and do all the flashes in one session...thats where you can get into trouble. thats why i point out the reboots . People trying to shortcut things often make their own misery...
[/QUOTE]



I've booted up normally and mostly completed my setup. The real issue is that I cant flash Magisk post-boot still. Sorry if I didn't make that clear enough bud. Got any other ideas?

 

[73sydney]

Usually people forget to do reboots after installing the ROM and try and do all the flashes in one session...thats where you can get into trouble. thats why i point out the reboots . People trying to shortcut things often make their own misery...

I've booted up normally and mostly completed my setup. The real issue is that I cant flash Magisk post-boot still. Sorry if I didn't make that clear enough bud. Got any other ideas?
[/QUOTE]

No worries

I have no idea how youre failing, as above, after i run setup, i enable USB Debugging in Developer Options (if needed) and then from a command prompt with platform tools (adb/fastboot etc) AND magisk, i do:

1) adb reboot bootloader
2) fastboot boot twrp-xxxxxxx.img
3) adb push magisk-xxxxxxx.zip /tmp
4) adb shell twrp install /tmp/magisk-xxxxxxx.zip

and then reboot

 

[Yourboymusti]

I've booted up normally and mostly completed my setup. The real issue is that I cant flash Magisk post-boot still. Sorry if I didn't make that clear enough bud. Got any other ideas?

No worries

I have no idea how youre failing, as above, after i run setup, i enable USB Debugging in Developer Options (if needed) and then from a command prompt with platform tools (adb/fastboot etc) AND magisk, i do:

1) adb reboot bootloader
2) fastboot boot twrp-xxxxxxx.img
3) adb push magisk-xxxxxxx.zip /tmp
4) adb shell twrp install /tmp/magisk-xxxxxxx.zip

and then reboot
[/QUOTE]


I get "unselect Enable Digest verification to restore" error when I try to adb shell install. I think I remember that I got the command to work once but even that didn't work - still got bootloop.

I have also tried to turn off and on some of digest options in the TWRP settings, they didn't work either