yashsingh1/xdaforums huggingface dataset:
[OnePlus 12] snowwolf725:
I’m glad to see you’ve updated the list.

However, I suggest you separate the files for the global version and the European version.

Although they have the same model number CPH2581, the files are not interchangeable.

You can't use GLO OTA file to local update EU model, vice versa.

Ref:

[OnePlus 12][ROM][OTA][BOOT][Oxygen OS] Repo of Oxygen OS Builds

As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note : This is not a support thread for issues you may have with...

xdaforums.com
[OnePlus 12] gozzaa:
There is a difference? Which files are which?
[OnePlus 12] AmirulAndalib:
608 is Global, 604 is Europe
[OnePlus 12] AmirulAndalib:
Yes currently there is no way and it will confuse people instead it's a must to separate the region.
[OnePlus 12] Benni231990:
I installed the 608 to my GLO phone but i dont have the AI Eraser?? Why? need i enable a setting or what?
[OnePlus 12] snowwolf725:
1. Change region to Thailand, Malaysia,Indonesia, Vietnam, India, Mexico, or Philippines.

2. Clear app data of "AIUnit" and "Photos"
[OnePlus 12] Benni231990:
when i change the Region to india for example get i any disadvantages? or something?
[OnePlus 12] AmirulAndalib:
You can fallback to your own region once you did those changes, nothing to worry about.
[OnePlus 12] snowwolf725:
No, you can change back to your region, after you enable AI eraser.
[OnePlus 12] Benni231990:
and will the AI eraser still enable after i change back to my Region?
[OnePlus 12] AmirulAndalib:
Yes bro, it will stay there as is ...
[OnePlus 12] Benni231990:
Guys you got damn right thanks a lot :)
[OnePlus 12] easyrider77:
604 is also NA
[OnePlus 12] _MartyMan_:
Spoiler content hidden.

Spoiler content hidden.
[OnePlus 12] gozzaa:
Thank you!

Do you know if there is any difference between global and eu?
[OnePlus 12] _MartyMan_:
They are basically the same if you ask me, but EU will get updates more frequently.
[OnePlus 12] null0seven:
If you live in Europa :

- Glo is bad/slow on updates.

- Eu is fast in updates.
[OnePlus 12] alp47470:
Fow now, I've seperated the links of which i could find. If you have more links feel free to DM me or comment here.
[OnePlus 12] AmirulAndalib:
Its just version numbers they are same, difference is model and region
[OnePlus 12] acasmc:
No update for EU? 🤔
[OnePlus 12] 0kti:
Nope
[OnePlus 12] wd789:
Bro, how did you install this global version, do you think you can share the process with me? I have the European version but I want to install the global one
[OnePlus 12] L3m0$:
It came from China already as OOS 14 GLO.
[OnePlus 12] wd789:
Oka Bro
[OnePlus 12] roosteroffer.:
Thank you so much for the amazing job. Can I ask you how did you get the ROM in the first place? I mean what is the process to obtain it?
[OnePlus 12] snowwolf725:
If you rooted your device, you can use luckytool to obtain the OTA information.

Ref:

Home

@docnok63 give a non-rooted way to obtain ota url.
[OnePlus 12] snowwolf725:
OxygenOS-CPH2573_14.0.0.610(EX01) (Incremental OTA)

https://gauss-componentotacostmanual-in.allawnofs.com/remove-3c8980c4bd62b06818ac40d4bb31c0dc/component-ota/24/04/20/cd0f505f576549f1a846877005b1fd01.zip

OxygenOS-CPH2573_14.0.0.610(EX01) (Full OTA)

https://gauss-componentotacostmanual-in.allawnofs.com/remove-3c8980c4bd62b06818ac40d4bb31c0dc/component-ota/24/04/20/f9c66a5a103049aab52e818bc0a016aa.zip
[OnePlus 12] lutherkingmartin:
Thank you for the links. Sad that's EU don't have 608 and IN already have 610. :(
[OnePlus 12] Mr-Zhag:
According to the information above, there's CPH2853, what version should be? I'm in U.S and that version is in my device. I bought dirrectly from ONEPLUS website.
[OnePlus 12] galaxys:
There is no 2853. My latest version on my US 1+12 is CPH2583_14.0.0.604(EX01)
[OnePlus 12] alp47470:
Updated, thanks 💯
[OnePlus 12] ashkan-khatar:
Hey, so if I'm going to lose data, will it tell me before the update? Or how would I know in advance?
[HTC U12+ Questions & Answers] Jack Android:
Hello,

I bought my HTC U12+ in January 2020 and right from the start I’ve had 2 major problems with the phone:

The speakerphone doesn’t work

The volume buttons sometimes don’t work and they live their own life, i.e. the volume can slide up to maximum by itself even when I simply keep my fingers away from the aforementioned buttons or don’t touch the phone at all

I know I’m not the only person in the world who has those problems as either both or at least one of them affects the majority of users.

Just to clarify, the phone is up-to-date, i.e. Android 9 with the 2.55.401.1 firmware and 1 July 2019 security patches, which is the latest EU soft possible (I bought it in Poland).

The first problem was briefly fixed a couple of years ago after getting in touch with the HTC tech support and receiving an OTA speakerphone fix as a result, which is why I didn’t officially get the 2.55.401.3 firmware update with 1 August 2020 security patches.

However, after HTC stopped providing their tech support to that particular smartphone model the aforementioned fix stopped working as well and I’ve had the same problem with the speakerphone again for over a year now.

The second problem, in turn, has never been addressed by HTC, as it seems to affect less people than the first one.

Nevertheless, I’m planning to sell the phone next year at the latest, but I’m afraid that nobody will be willing to buy it from me unless I somehow fix those problems.

Taking into consideration the above, any idea how to fix them?

Is there any possibility to reinstall the original soft from scratch and see if that helps?

Or maybe I should install a custom firmware instead?

Will any of the above work or are those hardware-related problems that cannot be fixed at all?

I would really appreciate any suggestions fom you, guys.
[HTC U12+ Questions & Answers] Jack Android:
Anyone?

Guys, simple question - will reinstalling the original firmware or installing a custom one fix the hardware issues with the speakerphone and haptic buttons?
[HTC U12+ Questions & Answers] TheMadKing:
If it's a hardware issue I'm assuming that it won't, but if it's somehow software-related then reinstalling the original firmware might fix things.

I've recently bought a U12+ myself - the ghost touches do happen from time to time and I think that it's a general issue with all phones, though they happen very rarely and usually only when the phone is laying down on a table.

And my speaker works perfectly.
[HTC U12+ Questions & Answers] mariosaraylian:
First off there is no "custom firmware" for this phone so thinking anymore about that is pointless. Second, which variant do you have out of these 3 below? I'm not sure what you meant by why you "didn't receive" the 2.55.401.3 incremental OTA update. If you are all stock on the device without being rooted and have the Stock Pie ROM and Stock Recovery, then you should receive the notification to download the 2.55.401.3 FW.

My speakerphone as well has always worked fine and I am using the Dual SIM Asia/TW variant.

I will say that I have absolutely noticed that different cases for the phone that cover the "buttons" seem to make it act more crazy than usual, so I'd recommend a case that does not cover them (if thats possible. I actually had to modify a case myself using careful cutting with a hot knife).

Let's start with which variant you have first and see how you reply to get you to the next step.

htc_imedugl: 2Q5510000, EMEA/Aisa TW/RUS/SEA India Dual-SIM

htc_imedtwl: 2Q5530000, CHINA, Dual-SIM

htc_imeuhl: 2Q5520000, EMEA/US Ulocked, Single-SIM
[HTC U12+ Questions & Answers] Jack Android:
What about ViperExperience, Pyrana, CleanSlate, LeeDrOiD, Kirisakura NEXT, etc.?

If you’d read THIS thread then you’d know that those who directly asked the HTC tech support for the speakerphone fix didn’t receive the 2.55.401.3 update. Now it’s too late, becase HTC no longer provides any kind of support for that model.

I’ve been suspecting that myself lately, but the thing is that I modified my case in a similar fashion as soon as I got it and ghost touches do occur every now and then nonetheless.

I really don’t know. How can I check that? I’m from Poland, so I clearly must have a European variant.
[HTC U12+ Questions & Answers] TheMadKing:
If you reboot into download mode you should be able to see the variant model
[HTC U12+ Questions & Answers] Jack Android:
I dunno how to do that either, but never mind. The label on the box says 2Q55100

PS I've also edited my previous post, because you wrote that there had been no custom firmware for this phone, but in reality there are a couple to choose from, so please check the above once again.
[Xiaomi Poco F1 Questions & Answers] MSDarwish:
TLDR: I no longer can connect my phone to PC in fastboot, ADB, or MTP modes. Data transfer can only be used when the phone is host as when using OTG or occasionally when using EDL mode. I really need to flash a custom recovery. Can anyone suggest a way to do this?

My charging port probably wore out and failed to connect to PC or OTG devices. I tried:

Replacing the port with a one that I can find locally. It didn't work and made the network worse so I returned it.

Ordering an "original" one from AliExpress. The network is fine, OTG now works, but still PC doesn't detect the phone.

Trying different cables and different PCs.

Factory resetting it.

Re-flashing the original ROM from MIUI's built-in updater.

Setting default USB mode to "MTP" back and force in developer options.

Entering EDL which worked only twice after trying for 2 hours, and the PC detected the phone but I cannot do anything with it. When I tried to flash an original ROM replacing its recovery with a custom one using a modified MiFlash tool, I got "cannot receive hello packet". I'm not sure if it is due to failed authentication or due to my problem.

Now, I can use OTG devices and maybe I can re-enter EDL mode. Any suggestions how to fix the situation or to workaround it to install a custom recovery on the device? Thank you in advance.
[Xiaomi Poco F1 Questions & Answers] Renate:
Are you occasionally getting "device descriptor failed" messages? Does your computer go "bong" when you plug in your device? This is Windows?
[Xiaomi Poco F1 Questions & Answers] MSDarwish:
Thank you for your quick reply. Sadly, no. Neither the computer nor the phone gives any sign of connection. No, "device descriptor failed" messages, and even device manager doesn't re-scan for devices when I plug it in. Only the phone starts charging as if the cable is charging only but it is not.

Yes the computer is Windows. Also, I tried connecting the phone using OTG with a samsung phone. If the Poco F1 is the host, it can properly browse and open files on the Samsung phone. If I flipped the cable so that the Samsung is now the host, it doesn't recognize the Poco F1. Also, when I try to change "the connection is controlled by:" on the Samsung device, it fails.

In summary, the OTG works great if the Poco F1 is the host: no disconnections or so. When the Poco F1 is connected to another host, it doesn't even recognize it.
[Xiaomi Poco F1 Questions & Answers] Renate:
Well, you can congratulate yourself on having a weird one.

It's more typical to lose all connectivity to a bad connection on the data lines.

This is USB Type C connector, but only USB 2.0

I'm thinking this can only be software problem with dual-role or a problem with the CC1 or CC2 line on the USB connector.

Has this ever had a problem with wetness? Have you blown the dust out of the connector?

5k from a CC to ground switches the port to OTG.

I'm not saying that yours is like this, but if you can run a terminal app, can you see:

cat /sys/class/dual_role_usb/otg_default/uevent

Mine says (when plugged in as peripheral, i.e. device, ADB):

DUAL_ROLE_NAME=otg_default
DUAL_ROLE_SUPPORTED_MODES=ufp dfp
DUAL_ROLE_MODE=ufp
DUAL_ROLE_POWER_ROLE=sink
DUAL_ROLE_DATA_ROLE=device

Ok, one of my devices shows this as:

cat /sys/devices/platform/soc/1c40000.qcom,spmi/spmi-0/spmi0-00/1c40000.qcom,spmi:qcom,pm2250@0:qcom,qpnp-smblite/typec/port0/data_role

To find this obscure one:

cd /sys
find . -name data_role 2>/dev/null
[Xiaomi Poco F1 Questions & Answers] MSDarwish:
Thank you for your reply. That's really weird. The only similar problem that I found online is this. It seems that the OP gave up.

The older, replaced port could have got some wetness into it occasionally, but I cannot remember that this caused the issue. Also, the new charging port was just taken out of its package. Does the CC-to-ground issue only apply to the charging port and its board or may be some short circuit is there on the main board or flex?

Unfortunately, running any of these commands results in permission denied errors as the phone have stock ROM without root. Except the last command which doesn't return anything probably due to no permissions as well.
[Xiaomi Poco F1 Questions & Answers] Renate:
Well, try this. Install UsbMode.apk (from my sig).

Without anything plugged in, hit the "View USB" button.

Does it say that it has a controller or no controller? Any details?

Hit back to launcher.

Now plug in a cable to another Android that you say works together and check again.

If it says "controller" (and details) both times, we can see that it's always in OTG mode (even without being plugged in).

If that is the case and you can easily take it apart, disconnect the flex cable to the USB and see what it now says.
[Xiaomi Poco F1 Questions & Answers] MSDarwish:
Thank you for your reply. I apologize for late responses. I have tried your awesome utility.

When there are no connected devices or when the phone is connected as a peripheral. I get:

No host controller found

While if I connect another phone or flash drive, I get:

[1] ????:????:?, 1 EPs)
[2] ????:????:?, 1 EPs)

So, it doesn't seem that the phone is always operating in OTG mode, does it?
[Xiaomi Poco F1 Questions & Answers] Renate:
No, that all looks correct.

I'm thinking that the USB is just not being configured.

Can you first:

getprop | grep usb

Then try:

setprop sys.usb.config adb
getprop sys.usb.state

Erm, your terminal may not let you setprop.
[Xiaomi Poco F1 Questions & Answers] MSDarwish:
You are right that I don't have the necessary permissions, but the props seems to be fine:

~ $ getprop | grep usb
[init.svc.usbd]: [stopped] [miui.usb.dialog]: [1]
[persist.data.df.dev_name]: [rmnet_usb0]
[persist.sys.usb.config]: [adb]
[persist.sys.usb.ffbm-02.func]: [adb]
[ro.boot.usbcontroller]: [a600000.dwc3]
[ro.vendor.audio.soundfx.usb]: [true] [sys.usb.config]: [mtp,adb]
[sys.usb.configfs]: [1]
[sys.usb.controller]: [a600000.dwc3] [sys.usb.ffs.ready]: [1]
[sys.usb.state]: [mtp,adb] [vendor.audio.feature.usb_offload.enable]: [true]
[vendor.audio.feature.usb_offload_burst_mode.enable]: [false]
[vendor.audio.feature.usb_offload_sidetone_volume.enable]: [false]
[vendor.audio.usb.disable.sidetone]: [true]
[Xiaomi Poco F1 Questions & Answers] Renate:
Have you tried with a USB 2 cable (no blue plastic in connector) or through a USB hub?

Can you see that sys.usb.state changes with selecting USB mode and/or USB debugging?

Just to check:

ls -l /config/usb_gadget

zcat /proc/config.gz | grep GADGET
...
CONFIG_USB_GADGET=y
...
[Xiaomi Poco F1 Questions & Answers] MSDarwish:
Yes, I have tried USB2 cables and USB2 ports on my PC and through my Display that has USB hub. The same problem happens.

Unfortunately, the commands result in permission denied.

I really appreciate your time and effort. If the problem became a waste of your time, I'm already thankful to you. Yet, I'd be delighted if there is some solution.
[Xiaomi Poco F1 Questions & Answers] MSDarwish:
I have some news about my problem. I retried flashing custom recovery using EDL mode and a modified Mi Flash tool which thankfully went OK. Now, I was able to install custom ROM and root my device though the data transfer still doesn't work.

This shows that the port is actually able to receive data from a host properly which gave me hope but also confusion. Something less important is that the transfer speed using OTG is actually slow (around 1MBps from a good Samsung drive) though it could be the low quality OTG cable.

Now, I ran the commands you told me to try and here are the results:

beryllium:/ # cat /sys/class/dual_role_usb/otg_default/uevent
DUAL_ROLE_NAME=otg_default
DUAL_ROLE_SUPPORTED_MODES=ufp dfp
DUAL_ROLE_MODE=ufp
DUAL_ROLE_POWER_ROLE=sink
DUAL_ROLE_DATA_ROLE=device

beryllium:/ # cd /sys
beryllium:/sys # find . -name data_role 2>/dev/null
./devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-02/c440000.qcom,spmi:qcom,pmi8998@2:qcom,usb-pdphy@1700/usbpd/usbpd0/otg_default/data_role
beryllium:/sys # cat /sys/devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-02/c440000.qcom,spmi:qcom,pmi8998@2:qcom,usb-pdphy@1700/usbpd/usbpd0/otg_default/data_role
device

beryllium:/sys # getprop | grep usb
[init.svc.usbd]: [stopped]
[init.svc.vendor.usb-hal-1-0]: [running]
[init.svc_debug_pid.usbd]: []
[init.svc_debug_pid.vendor.usb-hal-1-0]: [1145]
[oplusboot.verifiedbootstate]: [green]
[persist.data.df.dev_name]: [rmnet_usb0]
[persist.sys.usb.config]: [adb]
[persist.vendor.usb.config.extra]: [none]
[ro.boot.usbcontroller]: [a600000.dwc3]
[ro.boottime.usbd]: [9182944474]
[ro.boottime.vendor.usb-hal-1-0]: [8171018954]
[ro.recovery.usb.adb.pid]: [D001]
[ro.recovery.usb.fastboot.pid]: [4EE0]
[ro.recovery.usb.vid]: [18D1]
[ro.vendor.audio.soundfx.usb]: [true]
[sys.usb.config]: [adb]
[sys.usb.configfs]: [1]
[sys.usb.controller]: [a600000.dwc3]
[sys.usb.ffs.ready]: [1]
[sys.usb.mtp.device_type]: [3]
[sys.usb.state]: [adb]
[vendor.audio.feature.usb_offload.enable]: [true]
[vendor.audio.feature.usb_offload_burst_mode.enable]: [false]
[vendor.audio.feature.usb_offload_sidetone_volume.enable]: [false]
[vendor.usb.configfs]: [1]
[vendor.usb.controller]: [a600000.dwc3]
[vendor.usb.diag.func.name]: [diag]
[vendor.usb.dpl.inst.name]: [dpl]
[vendor.usb.product_string]: [Xiaomi Pocophone F1]
[vendor.usb.qdss.inst.name]: [qdss]
[vendor.usb.rmnet.func.name]: [gsi]
[vendor.usb.rmnet.inst.name]: [rmnet]
[vendor.usb.rndis.func.name]: [gsi]
[vendor.usb.rps_mask]: [0]
[vendor.usb.use_ffs_mtp]: [0]
[vendor.usb.use_gadget_hal]: [0]

beryllium:/sys # ls -l /config/usb_gadget
total 0
drwxrwx--- 6 root root 0 2024-02-23 21:05 g1
drwxrwx--- 6 root root 0 1970-01-01 21:06 g2

beryllium:/sys # zcat /proc/config.gz | grep GADGET
# CONFIG_USB_DWC3_GADGET is not set
# CONFIG_USB_ISP1760_GADGET_ROLE is not set
CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
# CONFIG_USB_GADGET_DEBUG_FS is not set
CONFIG_USB_GADGET_VBUS_DRAW=500
CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2
# CONFIG_USB_GADGET_XILINX is not set
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dhinesh_cool:
View attachment 6070919Introducing PixelBuilds: Unleash a Pixel-like Experience on Your A14 Device!​

Tired of sluggish performance, battery drain, and missing Pixel features on your A14 device? PixelBuilds is here to rescue your device and deliver a smooth, optimized, and Pixel-inspired experience!

Experience the Difference:

Dramatically improved battery life: Say goodbye to constant charging. PixelBuilds squeezes the most out of your battery, offering significantly longer runtime compared to other popular ROMs.

Reduced heating: Keep your device cool and running smoothly, even during demanding tasks.

Enhanced Performance: Experience smoother app launches, faster responsiveness, and improved multitasking with our kernel optimizations and custom schedulers

Rock-solid stability: Our meticulous development process ensures a reliable and enjoyable daily use experience.

Pixel-inspired features: Get a taste of the latest Pixel features on your older device.

checkout our blog

More Than Just Features:

We understand that every user has unique needs. That's why we're committed to:

Transparency: Open-source development guarantees full access to our code, fostering trust and collaboration.

Active community: Join our vibrant community to share experiences, get help, and stay updated on upcoming developments.

Continuous improvement: We're constantly refining PixelBuilds, incorporating user feedback and adding new features.

Ready to Unleash the Potential of Your Device?

Download:

Blueline

Crosshatch

Website: https://pixelbuilds.org/

Source Code:

b1c1 device repo: https://github.com/PixelBuilds-Devices/android_device_google_crosshatch

kernel repo: https://github.com/PixelBuilds-Devices/android_kernel_google_bluecross

vendor repo: https://gitlab.com/PixelBuilds/vendor-blobs

Android version: 14

Kernel version: 4.9.337
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dhinesh_cool:
reserved :
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dhinesh_cool:
If website say no build or something just refresh after 10 min or

Direct link

Crosshatch

Releases · PixelBuilds-Releases/crosshatch

Contribute to PixelBuilds-Releases/crosshatch development by creating an account on GitHub.

github.com

Blueline

Releases · PixelBuilds-Releases/blueline

Contribute to PixelBuilds-Releases/blueline development by creating an account on GitHub.

github.com
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] vogees:
please fix eSim on Pixel 3XL
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hugh1davies:
Thanks so much for this. We've been waiting so long!! Most grateful!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dhinesh_cool:
It is broken ,we cannot fix but there is workaround u need to flash stock enable esim then flash pixelbuilds active same sim it should work
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] publicanimal:
Thank you for the new build! Just booted it up.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ZEII:
Stable and smooth. Can you put funtion " Double tab to sleep" ?

thank you.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Slim2none4u:
Use PixelXpert https://github.com/siavash79/PixelXpert
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lpedia:
Try Settings > Display > Tap to sleep.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ZEII:
thank you.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mine Hashu:
What is dtbo.img file?

How to install it and is it mandatory to install it?

Thanks!

View attachment 6074982
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mine Hashu:
Share your review about the smoothness and errors you guys faced. Is it better then the pixel experience and evolutionX ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Slim2none4u:
No you don't need to flash it. But it's flashed like any other partition. fastboot flash dtbo dtbo.img . It's for those that flash custom kernels and need to go back to stock I believe.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mine Hashu:
i tried that Rom on my Pixel 3!

its good and stable rom and as same as we expect Pixel Experience Rom but its not smooth as it should be, it's just little bit laggy

otherwise it's awesome
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lttt.sea:
Please add "On/Off Screenshot Sound", it's quite noisy
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] beebenutz:
This rom is great, except I keep losing network signal when calling out. I can have full signal, then after I initiate a phone call, the signal goes to no signal.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] klemi71:
Any news concerning QR2 issues?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Slim2none4u:
April update is out!

If website say no build or something just refresh after 10 min or

Direct link

Blueline

PixelBuilds | blueline

PixelBuilds

pixelbuilds.org

Crosshatch

PixelBuilds | crosshatch

PixelBuilds

pixelbuilds.org
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dhinesh_cool:
Thnx for posting
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] svprm:
Thanks @dhinesh_cool for supporting Pixel 3 XL.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] franzpimp87:
Unlimited Google Photos on this ROM?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dhinesh_cool:
yes