Database Info

[Q] Can an Android phone be used as JUST a PDA?

I need to know if I can use an Android phone JUST for the PDA functionality - It would be used on WiFi only, and never for phone calls.
I know the simple answer seems to be 'yes', but has anyone actually done it? I'm worried that some phones might require activation before even getting into the phone (like my Fascinate did.) I know you can dial a keypad combination in the dialer to override that, but this is going to be for my 68 year old father who just wants the advanced GPS functionality (logging, geotagging photos) for use with offline GPS programs like CoPilot or Sygic, along with whatever other non-internet-connected apps he might want to use.
Furthermore, I've heard that AT&T & TMo phones will display an error about a missing or inactive SIM, but I've not heard whether you can move past that and just use the device as a mini-tablet.... I've been a VZW victim since the Droid's hit the market, so I don't know if this is a concern or not.
So, bottom line, my question is this - if I buy a no-contract phone (even [gasp] one with a bad ESN from eBay) and never activate it with the cell provider, can I use the device as just a PDA, and are there any special considerations I've overlooked?
Thanks to all who offer help!!!

lenknermj said:
I need to know if I can use an Android phone JUST for the PDA functionality - It would be used on WiFi only, and never for phone calls.
I know the simple answer seems to be 'yes', but has anyone actually done it? I'm worried that some phones might require activation before even getting into the phone (like my Fascinate did.) I know you can dial a keypad combination in the dialer to override that, but this is going to be for my 68 year old father who just wants the advanced GPS functionality (logging, geotagging photos) for use with offline GPS programs like CoPilot or Sygic, along with whatever other non-internet-connected apps he might want to use.
Furthermore, I've heard that AT&T & TMo phones will display an error about a missing or inactive SIM, but I've not heard whether you can move past that and just use the device as a mini-tablet.... I've been a VZW victim since the Droid's hit the market, so I don't know if this is a concern or not.
So, bottom line, my question is this - if I buy a no-contract phone (even [gasp] one with a bad ESN from eBay) and never activate it with the cell provider, can I use the device as just a PDA, and are there any special considerations I've overlooked?
Thanks to all who offer help!!!
Click to expand...
Click to collapse
I have an att Captivate NO SIM that I play with all the time. I even use GrooveIP to make phone calls via wifi over Google Voice! You dont HAVE to have a SIM in the phone for it to function!

[MOD] Enable "Phone" Features on T-Mobile T869

To give you a little context, I came over to the T869 from the Galaxy Tab 2 7.0, which is basically the WiFi-only sibling of the "Plus" T869 that T-Mobile now sells. Being a WiFi only device, it had the "phone" parts of the GUI disabled, like the Phone and Messaging apps won't show up or run and you can't sync BlueTooth headsets. The T869 has the MMS app enabled, but no phone, so the same mod I did on the P3113 is useful on this one.
Thankfully, even though it seems fairly arcane, Wes Foster made a nice utility to make this much easier (and more n00b friendly) to do.
To do this (and other framework mods), first you should pull the framework-res.apk file out of the ROM.zip file you're using. Open the zip and go into /system/framework. In there you'll find framework-res.apk, which you should extract.
Drop that file into the "place-framework-res-here" folder within the Mod tool, then run the tool and enter option 1.
This will unpack the files to the "files-to-edit" folder.
Inside there you'll need to go to \framework-res.apk\res\values\
You'll need to modify the file bools.xml. Find this line and change "false" to "true":
Code:
[B]<bool name="config_voice_capable">false</bool>[/B]
Once you make that change, you're all set to "enable" phone features. You can also make other changes as desired.
Here's a partial guide: http://www.igottadroid.com/ModMarket/Listings/Darkside Agent1621289.html
Once you're done modifying the file, save it, and then run through options 2, 3, and 4 on the mod tool.
Once its done, you'll have a flashable ZIP file named "update.zip" inside the final-zip-file folder.
For extra safety, I reccomend making a copy of the update.zip called revert_framework.zip.
Open this copy in 7-Zip, go into the /system/framework folder, and delete the framework-res.apk file there. Replace it with the unmodified one from your ROM, then close 7-Zip. Now you have a second "flashable" ZIP that will put the untouched framework back onto your tablet, which comes in handy if you managed to break something and cannot boot
I did not make the tool, and found it in this thread: http://forum.xda-developers.com/showthread.php?t=1823701
I am simply reposting it over here since I found it very helpful

I stumbled across this thread when I was about to ask about the international version...is there any chance you could post a video of this in action? Not that I don't believe this works, but I remember following a thread for the T-Mobile Springboard where a few people said a certain update would allow for phone/SMS, but then others who actively tried were unable to do so because of how T-Mobile picks up the IMEI (and doesn't let you use a phone SIM with a tablet).
If this works (and if it also keeps T-Mobile 4G), then this would be a MUCH better solution than buying an international 7.0 Plus (which is not only ~$200 more expensive on average but would only work on 2G on T-Mobile US).

Well, the T869 has SMS enabled natively. I got a "data only" pay-as-you-go plan for a 4G / WiFi hotspot earlier this year, and recently got the T869 with a contact. Both of these came with a 10 digit phone number for administrative purposes, and even the hotspot had the ability to receive SMS.
This particular trick doesn't do anything to the back end services themselves, so its not like you magically get phone service just by doing this.
I use a combination of SIP and Google Voice to do phone-type stuff without a phone.
I prefer this hack because it enables the native dialer, and pretty much all the good softphone solutions allow you to "integrate" with the native call log & dialer setup, so you just go to the normal "People" app and click someone's phone # and are then given an option to call them.
Without this hack, you must go into whatever 3rd party app you're using and initiate phone calls from there.
Remember, I initially started doing this on my WiFi Only GT-P3113 (which is basically a T869 without 4G or vibration).
I was never able to get the "Native" messaging app to behave quite right. There's a Google Voice SMS Integration app, and it can sync your GV texting into the native SMS app's text history, but it can't (or couldn't) trigger native SMS notifications correctly.
I am kinda over texting in general, as I have it piped through GoogleTalk. I receive SMS at my GoogleVoice phone #, and they are automatically forwarded to GoogleTalk via a third party web service called GVMax, which is free. GV Max is basically a GoogleVoice to XMPP bridge. After federating in my other IM accounts, GoogleTalk is now my one-stop-shop for textual communications.
Just my $0.02.
Isn't the "International" version so-called because its got a quad band radio that works on like any carrier?
Also, I have heard (though this is not confirmed) that the "International" edition doesn't come with an IR blaster, whereas the T869 does. I dunno if that's true or something you'd care about, but food for thought
magus57 said:
I stumbled across this thread when I was about to ask about the international version...is there any chance you could post a video of this in action? Not that I don't believe this works, but I remember following a thread for the T-Mobile Springboard where a few people said a certain update would allow for phone/SMS, but then others who actively tried were unable to do so because of how T-Mobile picks up the IMEI (and doesn't let you use a phone SIM with a tablet).
If this works (and if it also keeps T-Mobile 4G), then this would be a MUCH better solution than buying an international 7.0 Plus (which is not only ~$200 more expensive on average but would only work on 2G on T-Mobile US).
Click to expand...
Click to collapse

Well from what I remember, the reviews I read about the 7.0 Plus were regarding the international version and all of them mentioned an IR blaster - but regardless, that'd be one of my least-used features of the tablet. Kinda disappointed that it'd still only be calls over data - I think I'd pay the extra $200 and suffer 2G speeds (at least until T-Mobile 1900Mhz roll-out comes to Chicago) for GSM calls alone, as I'd rather not deal with a separate data plan or tethering data off my phone to get calls.

magus57 said:
Well from what I remember, the reviews I read about the 7.0 Plus were regarding the international version and all of them mentioned an IR blaster - but regardless, that'd be one of my least-used features of the tablet. Kinda disappointed that it'd still only be calls over data - I think I'd pay the extra $200 and suffer 2G speeds (at least until T-Mobile 1900Mhz roll-out comes to Chicago) for GSM calls alone, as I'd rather not deal with a separate data plan or tethering data off my phone to get calls.
Click to expand...
Click to collapse
Yeah that's kindof a deal breaker. Out here in Portland OR we have 4G in most places, and I'm either at work (in an office) or at home 90% of the time, where I have a high speed WiFi hookup, AND I almost never talk on the phone, so the data-only setup is perfect for guys like me.
GSM only would pretty much make that a dealbreaker, since I suspect the audio quality would be pretty terrible.

DivinityCycle said:
Yeah that's kindof a deal breaker. Out here in Portland OR we have 4G in most places, and I'm either at work (in an office) or at home 90% of the time, where I have a high speed WiFi hookup, AND I almost never talk on the phone, so the data-only setup is perfect for guys like me.
GSM only would pretty much make that a dealbreaker, since I suspect the audio quality would be pretty terrible.
Click to expand...
Click to collapse
While I do have a pretty stable 4G connection wherever I go (except for my brother's apartment, where ALL reception is horrible) or have access to my home's faster Wifi connection, and I don't talk much, I still get much better GSM service everywhere and can still get calls when I have to turn off data to save battery (since I use the data connection quite a bit when I'm away from a charger). And I haven't really had complaints with GSM audio or found voice over 4G/Wifi to be much clearer especially when the person on the other end is usually using GSM too..

I mean if you were doing some sorta data-only internet phone setup like SIP or GrooveIP or something. That's what I am using, and for it to sound alright you need decent bandwidth. Actually I ought to test out my stuff on a 2G connection and see how bad it is Should be interesting!

will this trick work on stock ICS build?

Galaxy t869
Does anyone know if this will allow making "regular" calls using my "regular" SIM CARD?
Thanks,
Jonathan

jon5407 said:
Does anyone know if this will allow making "regular" calls using my "regular" SIM CARD?
Thanks,
Jonathan
Click to expand...
Click to collapse
I seriously doubt it, no way to be truly sure without trying it though.

T869UVLG7 ICS phone call hack
Hey I'm one the noobs mentioned in your post. I'm living in the Bahamas and a proud owner of the T869.First I have no idea what the ROM.zip is and whether this is supposed to be done on a desktop or the tab itself.I am rooted but running UVLG7 ICS UPDATE.It'd be awesome if I could get this working .My sim card is data and 3g/4g ready.Could you please /anyone inform. Thanks to u guys with your mod skills they're mad skills.Thanks man

Thanks mate~~
I did this on the T869 originally locked to T-Mobile, and it worked without a problem~!!!!
PS: >>> Be sure to first wipe cache. I skipped that the first time and i almost created an atomic bomb
PPS: >>> Also, the backup revert.zip is a brilliant idea, it's what i used when i messed up the first time!

Hey mate!
thanks again for the tutorial!
I have followed it to completion.
I however, can only do simple things like loading airtime [our networks are prepaid] and check balance,
but I can't seem to be able to make calls
I have an unlocked T869
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
dubblecup said:
Hey I'm one the noobs mentioned in your post. I'm living in the Bahamas and a proud owner of the T869.First I have no idea what the ROM.zip is and whether this is supposed to be done on a desktop or the tab itself.I am rooted but running UVLG7 ICS UPDATE.It'd be awesome if I could get this working .My sim card is data and 3g/4g ready.Could you please /anyone inform. Thanks to u guys with your mod skills they're mad skills.Thanks man
Click to expand...
Click to collapse
Hey,
are you trying to follow the tutorial and are having problems???
Please be a little more clear where you're stuck so we can help

-accidental double post-

Read the thread.
To quote myself: "This particular trick doesn't do anything to the back end services themselves, so its not like you magically get phone service just by doing this."
Also I have upgraded a couple of times since I posted about this crap and no longer use my Samsung (now using a Nexus 7 2013 which is way better)

Skype Lockscreen Bypass Bug

Tested with Skype version 3.2.0.6673 (released 1st July 2013) on various
Android devices (Sony Xperia Z, Samsung Galaxy Note 2, Huawei Premia 4G
The Skype for Android application appears to have a bug which permits the
Android inbuilt lockscreen (ie. pattern, PIN, password) to be bypassed
relatively easily, if the device is logged into Skype, and the "attacker"
is able to call the "victim" on Skype.
This can be reproduced as follows with 2 Skype accounts, and 2 separate
devices to use with Skype. The target phone is presumed to have an Android
lockscreen configured and in use, and to be locked during the test.
1. Initiate a Skype call to the target device, which will cause it to
wake, ring, and display a prompt on the screen to answer or reject the call
2. Accept the call from the target device using the green answer button
on the screen
3. End the call from the initiating device (ie. the device used to call
the target phone)
4. The target device will end the call, and should display the
lockscreen.
5. Turn off the screen of the target device using the power key, and
turn it on again
6. The lockscreen will now be bypassed. It will remain bypassed until
the device is rebooted
Similar to (ironically enough):
http://arstechnica.com/security/201...een-lock-on-up-to-100-million-android-phones/.
Seems that internet based calling apps might well be "unlucky".
I suggest logging out of skype when not using it, until there is a fix.
Thanks to Turl for originally bringing this to my attention.

Greetings pulser_g2,
Thanks for posting this. I found that all these screenlock bypass vulns (including yours) won't work if a enterprise policy is enforced on the target device. I've tested with 2 different smartphones, Note 8.0 and Note 2. Both with the current stock firmware. Can you or anyone else confirm this?
Cheers,
Michael

c0rnholio said:
Greetings pulser_g2,
Thanks for posting this. I found that all these screenlock bypass vulns (including yours) won't work if a enterprise policy is enforced on the target device. I've tested with 2 different smartphones, Note 8.0 and Note 2. Both with the current stock firmware. Can you or anyone else confirm this?
Cheers,
Michael
Click to expand...
Click to collapse
Hi Michael,
Thanks for the tip. However, forcing enterprise policy onto a device that does not need it should not be a solution for a bug like this (not ranting against you, please don't take it that way). Skype was already informed about this a couple of weeks ago and nothing has been done afaik.
I received a Skype update today from the market, so I guess it might be worth checking if the bug can be repeated or if it has been fixed.

Hi egzthunder1,
I don't take your post personal. My post was not made with the intent to be a bugfix. I just want someone else who also has access to provisioned devices to confirm my observation. Additionally if my observation is correct then it should be mentioned in a security advisory that enterprise provisioned devices with an enforced password seem to not be affected by all these lockscreen bypasses. I'm just discussing here

Does andybody know which wrong usage of the Android-API might be used here? I'm developing myself an app which switches the Screen on and shows information without the need to unlock the device. Know I'm concerned that I might use the API wrong, too. There were also such bugs in other apps in the past month, so there must be some wrong usage type. Saidly I didn't find anything about it via googling. If you have links, please share.

SamsungPisser said:
Does andybody know which wrong usage of the Android-API might be used here? I'm developing myself an app which switches the Screen on and shows information without the need to unlock the device. Know I'm concerned that I might use the API wrong, too. There were also such bugs in other apps in the past month, so there must be some wrong usage type. Saidly I didn't find anything about it via googling. If you have links, please share.
Click to expand...
Click to collapse
It seems to be related to the use of the permission to disable the lockscreen.
I.e. http://stackoverflow.com/questions/12021800/disable-delay-android-lock-screen-programmatically
You want to ensure you definitely disable the option once done. I suggest you create a test plan and ensure even if everything goes wrong, the lock will still get enabled again in the end.

c0rnholio said:
Hi egzthunder1,
I don't take your post personal. My post was not made with the intent to be a bugfix. I just want someone else who also has access to provisioned devices to confirm my observation. Additionally if my observation is correct then it should be mentioned in a security advisory that enterprise provisioned devices with an enforced password seem to not be affected by all these lockscreen bypasses. I'm just discussing here
Click to expand...
Click to collapse
Hmmm that is interesting actually.
I need to see if I can replicate this by forcing provisioning manually.
I don't have an exchange server unfortunately (I use my own mail server that uses the protocol but doesn't do the complex provisioning.)
I'll have a look though as I think it supports provisioning in the configuration where it emulates Exchange. I believe this likely is a workaround for enterprise users.
This would be enough motivation actually to look at setting up proper provisioning of my devices.
Thanks for letting me know

Fix if you lost RCS

Just wanted to post that if you lost RCS today try disabling dsds mode and rebooting.
I lost the RCS hack today around 1600 PST yesterday, I was able to reenable it by going into the dialer and entering the debug menu(*#*#4636#*#*) and disabling dsds mode, rebooting then reapplying the hack.

what is the dsds??

Dual sim dual standby

calinorg said:
Dual sim dual standby
Click to expand...
Click to collapse
how do you do that

comptonhubbard said:
how do you do that
Click to expand...
Click to collapse
Google dsds

comptonhubbard said:
how do you do that
Click to expand...
Click to collapse
Luigi really told all in the first post...
luigi90210 said:
I was able to reenable it by going into the dialer and entering the debug menu(*#*#4636#*#*) and disabling dsds mode, rebooting then reapplying the hack.
Click to expand...
Click to collapse

I realize this is personal preference, but I'm not sure why people would start changing options like that in an effort to keep RCS. The RCS "hack" is so limited to begin with that it seems silly to try to chase after it. Don't get me wrong, I did the RCS hack on my family's phones (and it's still working just fine as of the time of this post), but I'm not going to start changing other settings in an effort to keep it. If it works, great. If not, oh well. Easy come and easy go.

sic0048 said:
I realize this is personal preference, but I'm not sure why people would start changing options like that in an effort to keep RCS. The RCS "hack" is so limited to begin with that it seems silly to try to chase after it. Don't get me wrong, I did the RCS hack on my family's phones (and it's still working just fine as of the time of this post), but I'm not going to start changing other settings in an effort to keep it. If it works, great. If not, oh well. Easy come and easy go.
Click to expand...
Click to collapse
Google has since fixed the dsds bug with RCS so it's working again in dsds mode. I prefer to use RCS over sms for many reasons, the biggest one being the fact that I can send higher quality photos and videos of my daughter to my fiance and family as well as knowing that my fiance has seen any messages I sent her.
It's not really limited, you get full RCS services doing the hack(which isn't even really a hack anymore as Google made it available to people with the latest messages beta), I also used the time that it was disabled to move from the sandbox url to the official Verizon url(I'm on Verizon) but my mom and fiance are still using the sandbox url without issue.

luigi90210 said:
It's not really limited, you get full RCS services doing the hack(which isn't even really a hack anymore as Google made it available to people with the latest messages beta).......
Click to expand...
Click to collapse
I meant limited because it primarily only works with other people that have enabled this "hack" (at least in the USA). Obviously the RCS capabilities are full featured, but simply not available unless both phones/sides of the text stream are RCS capable.

Question Request for help to successfully activate VoLTE/VoWiFi in Australia

I've a VoLTE/VoWiFi activated Telstra/Boost SIM that's confirmed to work fine with both stock-standard Moto G 5G Plus & iPhone 11 Pro Max, delivering those features in Australia.
Rog Phones in general & Rog phone 5 in particular are known to lack VoLTE/VoWiFi features with all of the Australian carriers. ASUS Zentalk forum has a few threads about it. (Of course, I too escalated it there for any official help, but none will be forthcoming anytime soon, from what I understand ). I'm genuinely in need of VoLTE at work due to terrible 3G but decent 4G there; and at home in need of VoWiFi due to terrible 3G but excellent WiFi backed by snappy fibre Internet connection.
My phone is an ASUS_I005DA model with build number WW_18.0840.2106.86. Neither "4G Calling" nor "Wi-Fi calling" settings are visible by default, but upon dialling "*#*#3642623344#*#*", those options become available. Though those features can be activated/toggled (and they stick around till the next reboot), they actually don't really make those features work (i.e., phone still drops down to 3G when making phone calls; similarly, calls simply don't go through WiFi, as is proven in airplane mode with WiFi on). This I understand is due to lack of .mbn files for the modem to support Australian carriers in general, Telstra in particular. (I gather that with previous Rog phone models, by injecting .mbn file(s) into the modem image, folks were able to get VoLTE and VoWiFi working in Australia.) I'm essentially looking for precise/tested/proven steps to accomplish just that but on Rog Phone 5.
This is where I've had it both boot loader unlocked & the system rooted with Magisk, in preparation for undertaking any and all such steps.
Has anybody been able to successfully access modem (i.e., Qualcomm Snapdragon X60 modem on Snapdragon 888 SoC found on this phone) from Windows or Linux systems for this sort of work? If yes, especially for Windows, what drivers did you use? (name, version info & where to download them from would greatly help) What additional software did you use on the Windows computer end (such as QPST) & on the phone end (such as QCOMDiagMode.apk & what version & from where was it sourced please?) etc. would be of great help.
A dumb question: Would it be at all possible to flash modem with updated image (incorporating the necessary .mbn file(s)) from within Android itself? Or Android itself doesn't have ADB to help with such tasks?? Just curious as I'm fine to work off either Windows or Linux end.
Thanks in advance for any useful guidance & direction.

The most likely answer would be to find how they made or picked the files with the 3 and try to make or find parallel 5 versions. The files should be compatible with fastboot (mbn is one of the extensions they use for firmware images).
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
It's also going to be an extremely experimental process, so the only tested and proven way will be to let someone else do it first. Hopefully you can find someone else in Australia with the same issue that is willing to put their device up for testing.

Is there a working guide to enable the AsusVoLTE App on Android 11 ?
Mine keeps saying root is not available,
and the USB command to enable PDC mode -
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
doesnt work for me..
any ideas ?

JazonX said:
Is there a working guide to enable the AsusVoLTE App on Android 11 ?
Mine keeps saying root is not available,
and the USB command to enable PDC mode -
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
doesnt work for me..
any ideas ?
Click to expand...
Click to collapse
Can't detect root · Issue #2 · HomerSp/AsusVoLTE
Hi, I'm trying to use your app but any button returns: Failed enabling <feature>, are you rooted? The strange thing is that I have rooted my phone with Magisk and root checker is successful... Can ...
github.com
If you look at the code for the app, it is basically performing the setprop commands on your behalf. Not sure how far you'll get with the app fixed.
Regardless, I sent along a pull request to fix root detection
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com

twistedumbrella said:
Can't detect root · Issue #2 · HomerSp/AsusVoLTE
Hi, I'm trying to use your app but any button returns: Failed enabling <feature>, are you rooted? The strange thing is that I have rooted my phone with Magisk and root checker is successful... Can ...
github.com
If you look at the code for the app, it is basically performing the setprop commands on your behalf. Not sure how far you'll get with the app fixed.
Regardless, I sent along a pull request to fix root detection
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com
Click to expand...
Click to collapse
The setprop command didn't trigger anything like it did on the ROG II.
That why I wanted to try the app..
Just noticed the pull request! Hope @HomerSp would look into it.

JazonX said:
The setprop command didn't trigger anything like it did on the ROG II.
That why I wanted to try the app..
Just noticed the pull request! Hope @HomerSp would look into it.
Click to expand...
Click to collapse
AsusVoLTE/MainActivity.java at master · HomerSp/AsusVoLTE
Enable VoLTE/VoWiFi on the ROG Phone 2. Contribute to HomerSp/AsusVoLTE development by creating an account on GitHub.
github.com
It's literally running the setprop commands, but...
[MOD-ish] AsusVoLTE w/ Root Fix
This is a temporary solution to a pending pull request. This thread will be deprecated if or when the official release is updated. I don't have the original signing key, but there is really no reason to attempt reverse engineering an app that's...
forum.xda-developers.com
Edit: moved to a separate thread, since it is not specific to this issue

I've had VoLTE show up on mine from day one with no problems, using Vodafone AU. I don't get VoWifi though - I don't know if that's dependent on your ISP. I use TPG for broadband at home.

That's great to hear! Thanks for your confirmation.
"Vodafone Wi-Fi Calling is not available to customers on prepaid plans" in Australia, according to this: https://www.vodafone.com.au/support/device/wi-fi-calling
Perhaps you're their prepaid user?
Hopefully, official VoLTE and VoWiFi support for Telstra and Optus isn't too far, seeing how unofficial community support isn't ready just yet.

Did you managed to find a way to write .mbn? In AsusRogPhone2 it was easy (via Diag mode, efstools etc, with A10 though), but in AsusRogPhone5 efstools freezes every time at port listening stage, so this methos it's a no go for now, for some unknown reason.

Vodafone in Australia has VOLTE and WIFI calling for Rog 5. I went from Vodafone (had Volte) to Telstra (Had literally nothing, had 10 support tickets with telstra that first month in regards to getting volte, wifi calling and reception issues) said screw it, went right back to Vodafone, and boom had both Wifi calling and VOLTE on the Rog 5. Plus my reception is god tier. Telstra only supports certain phones (literally like 2 series) and thats it. So yeah. Thats how I solved the VOLTE issue. Should have just stuck with Voda to begin with, but wanted to give Telstra a go. Never again. Garbage service.

Just to wrap-up my original request, as of Nov 2021 firmware update, thanks to ASUS incorporating necessary MBN file(s) for Telstra (and Optus too from what I've heard at other forums) in that firmware update, after dialling Enhanced-4G code, VoLTE and VoWiFi functionalities become available in Settings. Toggling those options does successfully activate both of those functionalities on Telstra network. According to what I've heard on Whirlpool, even Optus is now supported in the same way.
Alas, those settings don't stick over a reboot, so what procedure needs to be done after every reboot. Perhaps ASUS will make them stick in a future firmware update.
It's possible to make them stick across reboots on a rooted phone, using setprop tool.
Thanks