2D 3G Shutdown: Pixel 3 4G Compatilbility

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › 2D 3G Shutdown: Pixel 3 4G Compatilbility

1 | 2 | 3

Asteros

421 posts

Ultimate Geek
+1 received by user: 216

#3383666 13-Jun-2025 15:14

No offence OP but the Pixel 3 is 6-7 years old and lost software support 3-4 years ago. It is ancient hardware in phone terms. It was never sold new here and probably the reason why they never installed the profile into the OS. It’s not like the old days pre VoLTE where if the operating bands lined up the phone would work. Perhaps the manufacturer doesn’t want the phone to work here and specified this SKU accordingly. It’s good that you’re trying to get it to work but I’d go back to whoever sold you the refurbished phone last year and try to get a refund.

SamF

1642 posts

Uber Geek
+1 received by user: 259

Trusted

#3383668 13-Jun-2025 15:19

Asteros:

No offence OP but the Pixel 3 is 6-7 years old and lost software support 3-4 years ago. It is ancient hardware in phone terms. It was never sold new here and probably the reason why they never installed the profile into the OS. It’s not like the old days pre VoLTE where if the operating bands lined up the phone would work. Perhaps the manufacturer doesn’t want the phone to work here and specified this SKU accordingly. It’s good that you’re trying to get it to work but I’d go back to whoever sold you the refurbished phone last year and try to get a refund.

Yeah, we've been over that mate; the point is that by all accounts the phone is technically capable of VoLTE, and works with VoLTE in many other countries, but because the right software / settings aren't available it won't work here.

tripper1000

1659 posts

Uber Geek
+1 received by user: 1185

#3383695 13-Jun-2025 16:02

If feel your pain O.P. I like to fix stuff myself too. I hate it when in an effort to both grow your skill set and avoid buying a new one, you come to geekzone seeking a (potentially) geeky solution or a geeky in depth explanation of the issue at heart and receive defeatist and mind shrinking advice like "buy a new one".

I've already worked out that the chipset in my phone was never able to do VoLTE so there is no hacking/updating it. (but it has VoWiFi so how to get it to hot-spot to itself?).

I'm going to do what I do to avoid roaming charges: take my never-used VoIP home phone on the road via a SIP app and forward my cell # to that. Otherwise I may go retro and one of those ~$100 4G VoLTE Nokia "feature" dumb phones a try - probably one with Bluetooth so it continues to sync up with the car hands-free.

SamF

1642 posts

Uber Geek
+1 received by user: 259

Trusted

#3383697 13-Jun-2025 16:11

tripper1000:

If feel your pain O.P. I like to fix stuff myself too.

Appreciate the support my man!

tripper1000:

I'm going to do what I do to avoid roaming charges: take my never-used VoIP home phone on the road via a SIP app and forward my cell # to that.

Now that's a very interesting idea! :D

Rodimvs

41 posts

Geek
+1 received by user: 8

#3384144 14-Jun-2025 21:20

I'm in the same boat - my Pixel 3 currently does everything I need, but looks like I'll be upgrading too. If you discover a magic way to enable VoLTE I'd love to hear it.

SamF

1642 posts

Uber Geek
+1 received by user: 259

Trusted

#3384145 14-Jun-2025 21:25

Rodimvs:

I'm in the same boat - my Pixel 3 currently does everything I need, but looks like I'll be upgrading too. If you discover a magic way to enable VoLTE I'd love to hear it.

Will do, likewise for you!

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

tn71

14 posts

Geek
+1 received by user: 6

#3503633 17-Jun-2026 07:37

This is a non-exhaustive method for enabling VoLTE on a Pixel 3 for a specific carrier, and for people that already understand this type of method. For reference, this was completed on Android 11.

Disclaimer: you will lose all your data, I am not responsible for what happens to your device or any of this, I will not be able to provide further advice as half of this I don't understand...

1 - this is the method: https://github.com/stanislawrogasik/Pixel2XL-VoLTE-VoWiFi/tree/main/QPSTMethod (other links below are where files are that may be missing in this method or where they're easier to apply)

2 - install magisk and root the phone

3 - install this magisk module: https://github.com/stanislawrogasik/Pixel2XL-VoLTE-VoWiFi/blob/main/QPSTMethod/MagiskModules/VoLTE%20and%20VoWiFi%20enabler%20Pixel%202%20xl.zip and reboot.

4 - Setup computer with necessary tools and drivers as per Step 1. EFSTools can be found here (the Qualcomm drivers are too): https://github.com/firdaus-edymainoe/volte-oneplus-enabler/tree/main - the EFSTools folder already has "MCFG_autoselect_by_uim"

5 - NZ mbn files can be found here and the appropriate mbn should be placed in the EFSTools folder as described in Step 1: https://github.com/swangjang/Pixel-Redbull-Carrier-Patch/tree/main/system/vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/generic/Pixel/NZ

Note, this will mean your phones is specifically set up for the chosen carrier - if you change carrier, you may need to do this again for that different carrier.

6 - run in CMD (ensure ADB debugging is sorted) (source: https://xdaforums.com/t/module-to-enable-5g-volte-vowifi-on-pixel4a-5g-pixel5.4207725/post-84648473 ):

adb shell

resetprop ro.bootmode usbradio

resetprop ro.build.type userdebug

setprop sys.usb.config diag,diag_mdm,adb

diag_mdlog

cancel the process (ctrl+c) once it starts to "hang" at failed to open diag socket
change the usb config (to file transfer, or to no file transfer)

7 - in Device Manager, you should see under Ports "Qualcomm HS-USB..." - if not, figure out how to get it to show up.

8 - open new CMD, change the directory to inside of the EFSTools directory and run:

EfsTools.exe efsInfo

There should be no error

EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim

EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v

The second one should complete a process with no errors.

9 - reboot.

SamF

1642 posts

Uber Geek
+1 received by user: 259

Trusted

#3503699 17-Jun-2026 10:26

Brilliant! Thanks @tn71, I'll definitely give that a try!

I assume you were able to complete the process successfully on a Pixel 3 amd gain full 4G operation?

tn71

14 posts

Geek
+1 received by user: 6

#3503705 17-Jun-2026 10:38

Yes. So far I've only tested on Spark and using stock Android 11 (I can make calls over the 4G network). I have yet to try it on a custom ROM.

The "VoLTE and VoWiFi enabler Pixel 2 xl" module helps to enable 4G calling (can probably be done using Shizuku and the Pixel IMS app, but Magisk is needed for root adb access), and the rest is (what I assume) to force the modem to use the NZ (Spark in my case) mbn profile.

For 2Degrees, for example, you'd place this mcfg_sw.mbn file into the EFSTools folder: https://github.com/swangjang/Pixel-Redbull-Carrier-Patch/tree/main/system/vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/generic/Pixel/NZ/2Degrees/pixel_Commercial

Note, I think 2Degrees has a stricter whitelist than Spark, so that may be an issue on it's own.

Good luck!

SamF

1642 posts

Uber Geek
+1 received by user: 259

Trusted

#3503726 17-Jun-2026 11:39

Great, thanks for that extra info!

Are you suggesting that 2D may be actively blocking "incompatible" phones from connecting to the network?

tn71

14 posts

Geek
+1 received by user: 6

#3503734 17-Jun-2026 11:58

That's what I've read in some places, but I could be completely wrong. I'd be interested to know how you get on as it might debunk that (given you're on 2Degrees). Hopefully you have two different carriers sim cards so you can try two setups/mbn configurations (I only currently have access to Skinny and One SIMs)

Dyson

Shop now for Dyson appliances (affiliate link).

SamF

1642 posts

Uber Geek
+1 received by user: 259

Trusted

#3503736 17-Jun-2026 12:00

I have a spark sim I could use for testing if needed.

I'll keep you posted!

tn71

14 posts

Geek
+1 received by user: 6

#3503840 17-Jun-2026 20:19

I got it running on a custom ROM (CRdroid). Note, when running this command, this was the resultant error:

blueline:/ # diag_mdlog
/system/bin/sh: diag_mdlog: inaccessible or not found

I continued to "change the usb config (in my case file transfer)" and it booted into Qualcomm "mode". I followed the remaining steps and it was all good.

1 | 2 | 3