[Guide] Enabling VoLTE/VoWiFi v2

[HomerSp]

Hey HomerSp, can you think of anything that I may have missed when trying to enable VoWIFI? If not dont worry about it, but thank you so much for the development and what I have so far, it is a blessing having VoLTE on tmobile!

Were you able to get it working with the mbn @blueblur mentioned? I'm afraid I don't have much to add other then that; if an mbn exists for your carrier it should enable all ims functions (volte, vowifi etc), and if it doesn't most likely that mbn doesn't contain all of the required parameters.
There are some mbns here that you can try as well: https://github.com/JohnBel/QualcommMBNs

the command ro force open vowifi please?

The persist.vendor.dbg.wfc_avail_ovr property will force vowifi to be available, but you need to have an mbn flashed that supports it.

 

[narcosis34]

i take an error at adb shell with the last command for vowifi, is there anything else to try?

 

[HomerSp]

i take an error at adb shell with the last command for vowifi, is there anything else to try?

What error do you get? You will have to run those as root on the Android 10 beta, but if you're on Android 9 I *think* you can run them without root.

 

[narcosis34]

No want to go back to stock and if the modem survive from locking the bootloader, I want the commands to open the switches

 

[Donlavon1]

I tried to restore the modem settings with the fastboot erase modemst1 and fastboot erase modemst2 but now I have no service. Any way to fix this issue?

 

[VZTech]

I tried to restore the modem settings with the fastboot erase modemst1 and fastboot erase modemst2 but now I have no service. Any way to fix this issue?

Do you have an IMEI #?

 

[narcosis34]

I try to unlock the phone with the official application but the app reports the phone is unlocked but bootloader is still locked.

 

[Donlavon1]

Do you have an IMEI #?

It's not showing on the phone.

 

[VZTech]

It's not showing on the phone.

Ugh. Your IMEI is gone. You might be f'd.

 

[HomerSp]

It's not showing on the phone.

I'm currently looking at this issue. Erasing modemst1 and modemst2 is supposed to restore them back to defaults, but it seems like that's not happening for you. Are you available via skype or similar (send me a PM)? Need someone to test some things so I can figure out what's going on.

 

[Donlavon1]

I can send you a PM. Flashing Erasing modemst1 and modemst2 seems to have removed the IMEI number for both sim slots. Check the IMEI using *#06* and it say IMEI unknown.

---------- Post added at 04:38 PM ---------- Previous post was at 04:28 PM ----------

I'm currently looking at this issue. Erasing modemst1 and modemst2 is supposed to restore them back to defaults, but it seems like that's not happening for you. Are you available via skype or similar (send me a PM)? Need someone to test some things so I can figure out what's going on.

Yes I can PM you. Flashing Erasing modemst1 and modemst2 seems to have removed both slot 1 and 2 IMEI from the phone.

 

[TawkinTrash]

I can send you a PM. Flashing Erasing modemst1 and modemst2 seems to have removed the IMEI number for both sim slots. Check the IMEI using *#06* and it say IMEI unknown.

---------- Post added at 04:38 PM ---------- Previous post was at 04:28 PM ----------


Yes I can PM you. Flashing Erasing modemst1 and modemst2 seems to have removed both slot 1 and 2 IMEI from the phone.

Nice I'm not the only one. I also ran these commands and have no SIM card service. Hopefully we can figure this out.

 

[VZTech]

Ouch...no imei numbers are bad. People need to backup efs partition on twrp.

 

[HomerSp]

Ouch...no imei numbers are bad. People need to backup efs partition on twrp.

Yeah, I'm not sure at all what's going on here. I've been debugging a bit with @TawkinTrash, and it actually seems to restore the modemst partitions properly, but for some reason or other they result in no IMEI number. The fsg partition contains the information required to rebuild the partitions, so as long as you don't mess with that it should just work.
Very confused about what might be causing this.

 

[VZTech]

Yeah, I'm not sure at all what's going on here. I've been debugging a bit with @TawkinTrash, and it actually seems to restore the modemst partitions properly, but for some reason or other they result in no IMEI number. The fsg partition contains the information required to rebuild the partitions, so as long as you don't mess with that it should just work.
Very confused about what might be causing this.

I think the Chinese twrp backs up fsg partition. Is that where imei is? If so, might be a good idea to back that up. Or maybe the latest twrp builder could integrate it if it doesn't. This is not a good situation. I'm assuming the only ones losing imei are using the fastboot erase modem command? Might want to stay away from that for now.

 

[HomerSp]

I think the Chinese twrp backs up fsg partition. Is that where imei is? If so, might be a good idea to back that up. Or maybe the latest twrp builder could integrate it if it doesn't. This is not a good situation. I'm assuming the only ones losing imei are using the fastboot erase modem command? Might want to stay away from that for now.

fsg contains the stock efs and nv items, so yeah, it contains the imei amongst other things. It's encrypted though, so there's no way of extracting any info from there. As a test I did a backup of modemst1, modemst2, fsc, fsg and fsgCA, cleared fsg and fsgCA (NEVER DO THIS WITHOUT A BACKUP), and booted. Of course it was still fine, but as soon as I cleared modemst1 and modemst2 I got the same no IMEI/no service problem, because fsg and fsgCA were empty and it didn't have the necessary information to be able to rebuild the modemst partitions. It did create them, though. I flashed back the fsg backups and it was fine again.
I suspect something has happened to their fsg partitions, but I currently have no confirmation of this. Just to clarify, none of the commands I have posted touch the fsg partition and you should never, ever modify this, I don't know why it isn't write-protected.

I've added a warning to the guide before the commands, and have hidden them by default until we sort this out.

 

[VZTech]

fsg contains the stock efs and nv items, so yeah, it contains the imei amongst other things. It's encrypted though, so there's no way of extracting any info from there. As a test I did a backup of modemst1, modemst2, fsc, fsg and fsgCA, cleared fsg and fsgCA (NEVER DO THIS WITHOUT A BACKUP), and booted. Of course it was still fine, but as soon as I cleared modemst1 and modemst2 I got the same no IMEI/no service problem, because fsg and fsgCA were empty and it didn't have the necessary information to be able to rebuild the modemst partitions. It did create them, though. I flashed back the fsg backups and it was fine again.
I suspect something has happened to their fsg partitions, but I currently have no confirmation of this. Just to clarify, none of the commands I have posted touch the fsg partition and you should never, ever modify this, I don't know why it isn't write-protected.

I've added a warning to the guide before the commands, and have hidden them by default until we sort this out.

OK, then EVERYONE should do a fsg backup, and store it safely just in case.

 

[elmik]

*#*#3642623344#*#*
After this code we also need write mbn? Is there option to write mbn wihout root?

 

[HomerSp]

*#*#3642623344#*#*
After this code we also need write mbn? Is there option to write mbn wihout root?

Yes, you also need to write the mbm - that code is only used to force volte when you have the proper settings in modem (which is what the mbn writes). Unfortunately I don't think you can enable diag mode without root, so there is currently no way of doing this without root.

 

[deltarz]

Just want to say the older QDLoader HS-USB Driver_64bit_Setup work with this method if the newer drivers dont.

Didn't get any errors in CLI, but no VoLTE on telstra australia.

is the mcfg_autoselect_by_uim file supposed to be 0 kb? this doesnt look like something containing 3 config files.

Are the xiaomi mbns all confirmed to have volte for the 9t itself?

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

is uploadDIrectory literal or supposed to be replaced by something like the current directory?


There's someone else who got telstra working, how odd. The only difference is I edited some configs from the testing thread to always enable volte option showing, and I'm on boost instead of telstra. But boost is 99% telstra for all intents and purposes as they are a MVNO with a very special relationship to telstra, a lot of their backend doesnt distinct between them unlike other MVNOs. Or maybe a firmware difference?

It shouldn't be so wildly different, sigh.