[ROM][OFFICIAL][bramble] LineageOS 20

TULOA · Nov 11, 2021

Anyone else having issues with trying to open App Info and the settings app crashing on any attempt to get to any app info page?

If not what would I need to filter to get a good logcat for looking into this?

Edit: Apparently its being caused by some combination of Magisk version and boot image I guess. But I will test a bit before I get that resolved. Since I would rather have samsung pay at the moment instead of settings app info.

Deleted member 6200352 · Nov 21, 2021

Currently rocking this on my bramble w/ root from extracted payload.bin and patched via magisk and flashed. Runs good. I even get 5g sub 6 in some areas. The lineage instructions about "temp" flashing lineage recovery is kinda a misnomer as it will still be on there when everything is said and done--which is fine. I might try flashing a different kernel to play with twrp. I'm glad I got a 4a5g and not a 6.

pepa 77 · Nov 23, 2021

Hi can you use USB otg in Lineage recovery during first installation?

aleasto · Nov 23, 2021

pepa 77 said:
Hi can you use USB otg in Lineage recovery during first installation?

Yes. Under Apply Update there will be a new option once you've inserted your thumb drive.

pepa 77 · Nov 23, 2021

aleasto said:
Yes. Under Apply Update there will be a new option once you've inserted your thumb drive.

did I understand correctly that I need to cut back to android 11 before installing Lineage OS?

aleasto · Nov 23, 2021

pepa 77 said:
did I understand correctly that I need to cut back to android 11 before installing Lineage OS?

Yes, otherwise Lineage Recovery won't boot for the first install

pepa 77 · Nov 29, 2021

aleasto said:
Yes, otherwise Lineage Recovery won't boot for the first install

Hi on Saturday I gave Lineage OS

1. Flash recovery.img via Flash Tool 2. Via Lineage recovery and USB flash drives ROM.zip , open gapps( nano) and Magisk reboot all O.K

On Sunday came Ota download + install, reboot and everything O.K in place, great job thanks.

Just one request can turn on the automatic call recording in phone's application ?

KJ7LNW · Dec 1, 2021

Hi @aleasto, thank you for maintaining this rom!

After installing the stock "bramble-rq3a.211001.001" from google I wasn't able to install LineageOS. It would just spin the initial animation (single moving circle) and never get to the three lineageos circles.

However, I was able to install @dic1911 's unofficial ROM from here: https://xdaforums.com/t/rom-unofficial-lineageos-18-1-microg-edition.4196221/

Now after installing @dic1911's version I could install your official version.

Any idea why flashing his first and then yours would fix the problem?

-Eric

Here is the flash of @dic1911's zip:

Code:

]# fastboot -w update dic1911-rom/LineageOS-18.1-microG-bramble-20210913-userdebug-signed.zip
--------------------------------------------
Bootloader Version...: b5-0.3-7241846
Baseband Version.....: g7250-00132-210419-B-7294132
Serial Number........: 0A221JECB06293
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 OKAY [  0.070s]
Setting current slot to 'b'                        OKAY [  0.155s]
Snapshot cancel                                    (bootloader) update cancelled
OKAY [  0.075s]
extracting boot.img (96 MB) to disk... took 0.491s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB)                        OKAY [  2.585s]
Writing 'boot_b'                                   OKAY [  0.547s]
extracting dtbo.img (16 MB) to disk... took 0.053s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB)                        OKAY [  0.520s]
Writing 'dtbo_b'                                   OKAY [  0.210s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB)                          OKAY [  0.140s]
Writing 'vbmeta_b'                                 OKAY [  0.078s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.140s]
Writing 'vbmeta_system_b'                          OKAY [  0.078s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.270s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (98304 KB)                 OKAY [  2.580s]
Writing 'vendor_boot_b'                            OKAY [  0.570s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot                            OKAY [  0.070s]
< waiting for any device >
Sending 'super' (4 KB)                             OKAY [  0.001s]
Updating super partition                           OKAY [  0.006s]
Resizing 'product_b'                               OKAY [  0.004s]
Resizing 'system_b'                                OKAY [  0.004s]
Resizing 'system_ext_b'                            OKAY [  0.004s]
Resizing 'system_a'                                OKAY [  0.004s]
Resizing 'vendor_b'                                OKAY [  0.004s]
Resizing 'vendor_a'                                OKAY [  0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (408 MB) to disk... took 2.863s
archive does not contain 'product.sig'
Resizing 'product_b'                               OKAY [  0.004s]
Sending sparse 'product_b' 1/2 (258756 KB)         OKAY [  6.766s]
Writing 'product_b'                                OKAY [  1.550s]
Sending sparse 'product_b' 2/2 (159724 KB)         OKAY [  4.122s]
Writing 'product_b'                                OKAY [  0.991s]
extracting system.img (1044 MB) to disk... took 6.781s
archive does not contain 'system.sig'
Resizing 'system_b'                                OKAY [  0.041s]
Sending sparse 'system_b' 1/5 (258808 KB)          OKAY [  6.756s]
Writing 'system_b'                                 OKAY [  1.542s]
Sending sparse 'system_b' 2/5 (258064 KB)          OKAY [  6.660s]
Writing 'system_b'                                 OKAY [  1.510s]
Sending sparse 'system_b' 3/5 (258064 KB)          OKAY [  6.678s]
Writing 'system_b'                                 OKAY [  1.532s]
Sending sparse 'system_b' 4/5 (251476 KB)          OKAY [  6.528s]
Writing 'system_b'                                 OKAY [  1.522s]
Sending sparse 'system_b' 5/5 (43352 KB)           OKAY [  1.112s]
Writing 'system_b'                                 OKAY [  0.294s]
extracting system_ext.img (238 MB) to disk... took 1.389s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_b'                            OKAY [  0.004s]
Sending 'system_ext_b' (244184 KB)                 OKAY [  6.297s]
Writing 'system_ext_b'                             OKAY [  1.466s]
extracting system_other.img (61 MB) to disk... took 0.357s
archive does not contain 'system.sig'
Resizing 'system_a'                                OKAY [  0.004s]
Sending 'system_a' (62740 KB)                      OKAY [  1.612s]
Writing 'system_a'                                 OKAY [  0.397s]
extracting vendor.img (678 MB) to disk... took 3.932s
archive does not contain 'vendor.sig'
Resizing 'vendor_b'                                OKAY [  0.004s]
Sending sparse 'vendor_b' 1/3 (262140 KB)          OKAY [  6.819s]
Writing 'vendor_b'                                 OKAY [  1.444s]
Sending sparse 'vendor_b' 2/3 (262140 KB)          OKAY [  6.800s]
Writing 'vendor_b'                                 OKAY [  1.577s]
Sending sparse 'vendor_b' 3/3 (170356 KB)          OKAY [  4.445s]
Writing 'vendor_b'                                 OKAY [  1.049s]
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
Erasing 'userdata'                                 OKAY [  7.289s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'                                 OKAY [  0.005s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 129.421s

aleasto · Dec 2, 2021

KJ7LNW said:

Hi @aleasto, thank you for maintaining this rom!

After installing the stock "bramble-rq3a.211001.001" from google I wasn't able to install LineageOS. It would just spin the initial animation (single moving circle) and never get to the three lineageos circles.

However, I was able to install @dic1911 's unofficial ROM from here: https://xdaforums.com/t/rom-unofficial-lineageos-18-1-microg-edition.4196221/

Now after installing @dic1911's version I could install your official version.

Any idea why flashing his first and then yours would fix the problem?

-Eric

Here is the flash of @dic1911's zip:

Code:

]# fastboot -w update dic1911-rom/LineageOS-18.1-microG-bramble-20210913-userdebug-signed.zip
--------------------------------------------
Bootloader Version...: b5-0.3-7241846
Baseband Version.....: g7250-00132-210419-B-7294132
Serial Number........: 0A221JECB06293
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 OKAY [  0.070s]
Setting current slot to 'b'                        OKAY [  0.155s]
Snapshot cancel                                    (bootloader) update cancelled
OKAY [  0.075s]
extracting boot.img (96 MB) to disk... took 0.491s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB)                        OKAY [  2.585s]
Writing 'boot_b'                                   OKAY [  0.547s]
extracting dtbo.img (16 MB) to disk... took 0.053s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB)                        OKAY [  0.520s]
Writing 'dtbo_b'                                   OKAY [  0.210s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB)                          OKAY [  0.140s]
Writing 'vbmeta_b'                                 OKAY [  0.078s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.140s]
Writing 'vbmeta_system_b'                          OKAY [  0.078s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.270s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (98304 KB)                 OKAY [  2.580s]
Writing 'vendor_boot_b'                            OKAY [  0.570s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot                            OKAY [  0.070s]
< waiting for any device >
Sending 'super' (4 KB)                             OKAY [  0.001s]
Updating super partition                           OKAY [  0.006s]
Resizing 'product_b'                               OKAY [  0.004s]
Resizing 'system_b'                                OKAY [  0.004s]
Resizing 'system_ext_b'                            OKAY [  0.004s]
Resizing 'system_a'                                OKAY [  0.004s]
Resizing 'vendor_b'                                OKAY [  0.004s]
Resizing 'vendor_a'                                OKAY [  0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (408 MB) to disk... took 2.863s
archive does not contain 'product.sig'
Resizing 'product_b'                               OKAY [  0.004s]
Sending sparse 'product_b' 1/2 (258756 KB)         OKAY [  6.766s]
Writing 'product_b'                                OKAY [  1.550s]
Sending sparse 'product_b' 2/2 (159724 KB)         OKAY [  4.122s]
Writing 'product_b'                                OKAY [  0.991s]
extracting system.img (1044 MB) to disk... took 6.781s
archive does not contain 'system.sig'
Resizing 'system_b'                                OKAY [  0.041s]
Sending sparse 'system_b' 1/5 (258808 KB)          OKAY [  6.756s]
Writing 'system_b'                                 OKAY [  1.542s]
Sending sparse 'system_b' 2/5 (258064 KB)          OKAY [  6.660s]
Writing 'system_b'                                 OKAY [  1.510s]
Sending sparse 'system_b' 3/5 (258064 KB)          OKAY [  6.678s]
Writing 'system_b'                                 OKAY [  1.532s]
Sending sparse 'system_b' 4/5 (251476 KB)          OKAY [  6.528s]
Writing 'system_b'                                 OKAY [  1.522s]
Sending sparse 'system_b' 5/5 (43352 KB)           OKAY [  1.112s]
Writing 'system_b'                                 OKAY [  0.294s]
extracting system_ext.img (238 MB) to disk... took 1.389s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_b'                            OKAY [  0.004s]
Sending 'system_ext_b' (244184 KB)                 OKAY [  6.297s]
Writing 'system_ext_b'                             OKAY [  1.466s]
extracting system_other.img (61 MB) to disk... took 0.357s
archive does not contain 'system.sig'
Resizing 'system_a'                                OKAY [  0.004s]
Sending 'system_a' (62740 KB)                      OKAY [  1.612s]
Writing 'system_a'                                 OKAY [  0.397s]
extracting vendor.img (678 MB) to disk... took 3.932s
archive does not contain 'vendor.sig'
Resizing 'vendor_b'                                OKAY [  0.004s]
Sending sparse 'vendor_b' 1/3 (262140 KB)          OKAY [  6.819s]
Writing 'vendor_b'                                 OKAY [  1.444s]
Sending sparse 'vendor_b' 2/3 (262140 KB)          OKAY [  6.800s]
Writing 'vendor_b'                                 OKAY [  1.577s]
Sending sparse 'vendor_b' 3/3 (170356 KB)          OKAY [  4.445s]
Writing 'vendor_b'                                 OKAY [  1.049s]
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
Erasing 'userdata'                                 OKAY [  7.289s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'                                 OKAY [  0.005s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 129.421s

I don't know, probably you had not formatted data?

KJ7LNW · Dec 6, 2021

aleasto said:
I don't know, probably you had not formatted data?

Possibly. I thought I had done `fastboot format:ext4 userdata`

aleasto · Dec 7, 2021

KJ7LNW said:
Possibly. I thought I had done `fastboot format:ext4 userdata`

This device expects f2fs userdata (see fstab).
Install instructions suggest to use the Recovery entry for formatting data.

J0kker · Jan 23, 2022

Helle guys, just one maybe stupid question, but is there a way to keep one slot (let's say slot a) unrooted while the other would be flashed with magisk ?
I managed to to this but i'm wondering how i would be able to update only on slot b to keep my slot a untouched.
If this is possible, should i adb sideload to update while beeing in slot a from inside the lienageos recovery, or slot b ?
Or maybe it would be just more simple to boot in slot a (unrooted) and update from the updater, i guess it would flash the update to the other slot, so slot b ?
If it's even possible obviously.
Edit: Seems like it works, but you need to sideload magisk zip again after the update as the slot a is copied over slot b, then it's updated.
So still no way to achieve that without connecting the phone to a computer.
Might be doable with twrp but all i got from updating through twrp is a bootloop.

hajkan · Feb 27, 2022

I am having an issue with Bluetooth audio broadcasting with lineage_bramble-userdebug 11 RQ3A.211001.001 10039687

This used to work fine in previous builds I do not know why I can't broadcast Bluetooth audio anymore. Does anyone have an issue with it too?

KJ7LNW · Apr 20, 2022

Hello all,

I've been running on LineageOS 18.1 bramble for a few months now:

Code:

lineage_bramble-userdebug 11RQ3A.211001.001eng.root.20211116.211454 dev-keys

We are using AT&T and have been having LTE trouble sometime after the 3G shutdown (it worked fine for months before that). Most of the time inbound/outbound VoLTE works fine. However, after the phone has been booted for a week or so the calls stop coming in and outbound calls disconnect immediately. I can reliably "fix" the problem by rebooting my phone but since I don't know when the problem happens I'm unable to know when I should reboot my phone to fix the problem! Texts and voicemail notification work fine, this is only a problem with calls.

Logcat shows the following, note the disconnect cause=ERROR_UNSPECIFIED.

Ideas?

JavaScript:

04-20 14:59:04.247  1338  2481 I Telecom : Event: RecordEntry TC@33: SET_DIALING, successful outgoing call: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC(cap/cast)@E-E-I6o
04-20 14:59:04.248  1338  2481 I Telecom : InCallController: Sending updateCall [Call id=TC@33, state=DIALING, tpac=ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}, cmgr=ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}, handle=tel:**********86, vidst=A, childs(0), has_parent(false), cap=[ sup_hld mut !v2a], prop=[]]: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC(cap/cast)@E-E-I6o
04-20 14:59:04.261  1338  2481 I Telecom : CallsManager: setCallState DIALING -> DIALING, call: [Call id=TC@33, state=DIALING, tpac=ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}, cmgr=ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}, handle=tel:**********86, vidst=A, childs(0), has_parent(false), cap=[ sup_hld mut !v2a], prop=[]]: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC(cap/cast)@E-E-I6o
04-20 14:59:04.262  2475  2475 I TelecomFramework: TelephonyConnectionService: notifyCreateConnectionComplete TC@33_1: (...->CSW.hCCC)->CS.crCoC->H.CS.crCoC(cap/cast)@E-E-E-I6o
04-20 14:59:04.267  2475  2475 I Telephony: : onDisconnect: callId=TC@33_1, cause=ERROR_UNSPECIFIED
04-20 14:59:04.276  2475  2475 V Telephony: GsmConnection: Update state from DIALING to DISCONNECTED for TC@33_1
04-20 14:59:04.279  2475  2475 V Telephony: onStateChanged, state: DISCONNECTED

ShitHawk · Apr 20, 2022

KJ7LNW said:
Hello all,

I've been running on LineageOS 18.1 bramble for a few months now:

Code:

lineage_bramble-userdebug 11RQ3A.211001.001eng.root.20211116.211454 dev-keys

We are using AT&T and have been having LTE trouble sometime after the 3G shutdown (it worked fine for months before that). Most of the time inbound/outbound VoLTE works fine. However, after the phone has been booted for a week or so the calls stop coming in and outbound calls disconnect immediately. I can reliably "fix" the problem by rebooting my phone but since I don't know when the problem happens I'm unable to know when I should reboot my phone to fix the problem! Texts and voicemail notification work fine, this is only a problem with calls.

Logcat shows the following, note the disconnect cause=ERROR_UNSPECIFIED.

Ideas?

JavaScript:

04-20 14:59:04.247 1338 2481 I Telecom : Event: RecordEntry TC@33: SET_DIALING, successful outgoing call: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC(cap/cast)@E-E-I6o 04-20 14:59:04.248 1338 2481 I Telecom : InCallController: Sending updateCall [Call id=TC@33, state=DIALING, tpac=ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}, cmgr=ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}, handle=tel:**********86, vidst=A, childs(0), has_parent(false), cap=[ sup_hld mut !v2a], prop=[]]: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC(cap/cast)@E-E-I6o 04-20 14:59:04.261 1338 2481 I Telecom : CallsManager: setCallState DIALING -> DIALING, call: [Call id=TC@33, state=DIALING, tpac=ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}, cmgr=ComponentInfo{com.android.phone/com.android.services.telephony.TelephonyConnectionService}, ***, UserHandle{0}, handle=tel:**********86, vidst=A, childs(0), has_parent(false), cap=[ sup_hld mut !v2a], prop=[]]: (...->CS.crCo->H.CS.crCo->H.CS.crCo.pICR)->CSW.hCCC(cap/cast)@E-E-I6o 04-20 14:59:04.262 2475 2475 I TelecomFramework: TelephonyConnectionService: notifyCreateConnectionComplete TC@33_1: (...->CSW.hCCC)->CS.crCoC->H.CS.crCoC(cap/cast)@E-E-E-I6o 04-20 14:59:04.267 2475 2475 I Telephony: : onDisconnect: callId=TC@33_1, cause=ERROR_UNSPECIFIED 04-20 14:59:04.276 2475 2475 V Telephony: GsmConnection: Update state from DIALING to DISCONNECTED for TC@33_1 04-20 14:59:04.279 2475 2475 V Telephony: onStateChanged, state: DISCONNECTED

When all this stuff started happening last month or maybe Febrary, I had a moto g7 with LTE and VoLTE etc. It was supposed to work. However! It stopped working with all the same symptoms you are having. As soon as I dialed the phone, it would hang up. I could reconfigure my network to receive data, but no phone and for a while, I could reconfigure the network and the phone would work, but no data, but after 2 weeks of fighting it, the phone would no longer dial, no matter what I did. I use the phone in my garage to play songs as that is all it's good for next to becoming a boat anchor. I broke down and bought a Pixel 5 which works just fine with LineageOS, but I'm still pissed off about the Moto G7 because it was advertised to work when we lost 3G and I really liked that phone.

KJ7LNW · Apr 21, 2022

@****Hawk, that sucks, I'm not familiar with LG devices but it sounds like a nice phone. I'm sure lots of things changed at the LTE transition and carriers are likely still sorting out the issues. Perhaps my phone has had the problem all along but fell back to GSM when LTE breaks every so often. Maybe others will report the issue and LineageOS will fix it---or if its a radio firmware issue then the mfg's can deal with it.

Maybe its a radio firmware version issue or something, but I'm not really sure how to troubleshoot from here. I've thought of scheduling a reboot every night, seems like a bit excessive though!

I'm guessing LineageOS needs to re-init LTE or poke it to "re-register" (SIP terminology), or whatever the LTE layer needs to refresh its access token. Obviously it works at reboot, so I would think that something can re-init.

appro77 · Apr 24, 2022

I've had LineageOS on my P4a 5G before but have been running A12 stock for a while. I tried to go back to LineageOS a few days ago but first flashing the final released version of A11 as instructed using the Google online flash tool. I then went through the LineageOS install procedure but couldn't get past the boot animation.

I then did all of the above 2 more times with the same result.....LineageOS wouldn't boot.

Not sure what's happening as I've had LineageOS on this phone before, as previously stated, plus on several other phones. I've never seen this issue before. Any clues as to the cause would be appreciated.

aleasto · Apr 24, 2022

appro77 said:
I've had LineageOS on my P4a 5G before but have been running A12 stock for a while. I tried to go back to LineageOS a few days ago but first flashing the final released version of A11 as instructed using the Google online flash tool. I then went through the LineageOS install procedure but couldn't get past the boot animation.

I then did all of the above 2 more times with the same result.....LineageOS wouldn't boot.

Not sure what's happening as I've had LineageOS on this phone before, as previously stated, plus on several other phones. I've never seen this issue before. Any clues as to the cause would be appreciated.

Format data

KJ7LNW · Apr 24, 2022

@appro77, @AleSto is probably right, something needs formatted.

I was able to install LineageOS+microG using this procedure (its P4XL "coral" but the procedure is about the same, just make sure you have the right build for your model):

https://xdaforums.com/t/how-to-inst...-4-xl-coral-w-microg-and-magisk-root.4357167/

After getting it loaded these are the Google vs. microG suggestions for apps and such:

https://xdaforums.com/t/getting-started-microg-how-i-degoogled-my-google-pixel.4393847/

appro77 · Apr 25, 2022

aleasto said:
Format data

Thanks. I'm an idiot. Somehow I was missing that step. Aaaaaahhhhh.

[ROM][OFFICIAL][bramble] LineageOS 20

Senior Member

Deleted member 6200352

Guest

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Member

Member

Member

Senior Member

Senior Member

Member

Senior Member

Similar threads

Top Liked Posts