I hope to open the Qualcomm diag port to modify the relevant files to support China Telecom 4g. Can the third-party ROM support it?
myyuanyu said:
I hope to open the Qualcomm diag port to modify the relevant files to support China Telecom 4g. Can the third-party ROM support it?
Click to expand...
Click to collapse
this is the development section for the pixel 2 and is reserved for ROM development and testing. any questions you may have need to be posted in the Q&A section of the pixel 2 and not here.
Sent from my Pixel 2 using Tapatalk
I am not even sure why you are spamming this forum after spamming the threads.
https://forum.xda-developers.com/showpost.php?p=78318905&postcount=98
I mentioned in my thread but you dont seem to listen or understand.
YOU DO NOT NEED A CUSTOM ROM TO ENABLE DIAG MODE. YOU NEED ROOT AND IT CAN BE DONE ON STOCK ROM.
why is it so difficult for you to google/baidu/yandex?
Code:
adb devices
adb shell
su (you will get pop up on your phone to give root authorization for ADB, authorize it)
setprop sys.usb.config diag,adb (this will open your phone diagnostic port)
Because I compiled two versions of the rom, 8.1 can open diag to modify the file but 9.0 can not open, do not understand the reasons, I would like to ask.
munchy_cool said:
I am not even sure why you are spamming this forum after spamming the threads.
https://forum.xda-developers.com/showpost.php?p=78318905&postcount=98
I mentioned in my thread but you dont seem to listen or understand.
YOU DO NOT NEED A CUSTOM ROM TO ENABLE DIAG MODE. YOU NEED ROOT AND IT CAN BE DONE ON STOCK ROM.
why is it so difficult for you to google/baidu/yandex?
Code:
adb devices
adb shell
su (you will get pop up on your phone to give root authorization for ADB, authorize it)
setprop sys.usb.config diag,adb (this will open your phone diagnostic port)
Click to expand...
Click to collapse
Hi
I try this method based on Pixel 2 with Android Pie magisk root, but failed to open diag port. Did you try it successfully? Thank you.
lycheejet said:
I am not even sure why you are spamming this forum after spamming the threads.
https://forum.xda-developers.com/showpost.php?p=78318905&postcount=98
I mentioned in my thread but you dont seem to listen or understand.
YOU DO NOT NEED A CUSTOM ROM TO ENABLE DIAG MODE. YOU NEED ROOT AND IT CAN BE DONE ON STOCK ROM.
why is it so difficult for you to google/baidu/yandex?
Hi
I try this method based on Pixel 2 with Android Pie magisk root, but failed to open diag port. Did you try it successfully? Thank you.
Click to expand...
Click to collapse
Can't open
Hi, I want to extract qcn file of my pixel 3 and followed other steps. After stressful searches, I was almost done with the following links
1) https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967
2) https://forum.xda-developers.com/pixel-3/help/qxdm-pixel-3-limited-success-help-t3887152
steps I followed
1) bootloader unlock
2) factory image (android 9) from official google
3) Twrp recovery
4) Magisk from link 1
5) Module (Pixel 2 diag port.zip) from link 1
6) Mi5 Qualcomm drivers from link 2
and with that, I got diag port somehow opened but it only gets on MTP connection via USB but no proper detection in QPST. I tried to backup qcn file with partial detection of COM port but it says "checking connection" and then "backup failed no phone attached".
Is there any way for this? I'm really stuck with my mobile network problem. :crying:
P.S: just to make it clear, my question is not for VoLTE or PDC.
Update:-
I managed to get detected properly via Modem port but not in QFIL.
1) Magisk and Module from link 1
2) "QUD.WIN.1.1 Installer-10037.3 Setup" Qualcomm Drivers
3) Put phone in MTP connection
4) Following commands in adb
Code:
adb shell
su
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
5) open "QPST Configuration"
6) Add port
7) Add Modem port
With these steps, i get manage to get detected in QPST Download and able to make a backup of "*.xqcn". But after editing and restoring, there is no such change. Am i missing something?
any usfull info here? https://gist.github.com/julian-alarcon/53f9a782008b5d5f879bf6fa878f87f3
Hello sir i lost my physical sim card on pixel 3a only shows esim option please help
luqman.mirza said:
Hi, I want to extract qcn file of my pixel 3 and followed other steps. After stressful searches, I was almost done with the following links
1) https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967
2) https://forum.xda-developers.com/pixel-3/help/qxdm-pixel-3-limited-success-help-t3887152
steps I followed
1) bootloader unlock
2) factory image (android 9) from official google
3) Twrp recovery
4) Magisk from link 1
5) Module (Pixel 2 diag port.zip) from link 1
6) Mi5 Qualcomm drivers from link 2
and with that, I got diag port somehow opened but it only gets on MTP connection via USB but no proper detection in QPST. I tried to backup qcn file with partial detection of COM port but it says "checking connection" and then "backup failed no phone attached".
Is there any way for this? I'm really stuck with my mobile network problem. :crying:
P.S: just to make it clear, my question is not for VoLTE or PDC.
Update:-
I managed to get detected properly via Modem port but not in QFIL.
1) Magisk and Module from link 1
2) "QUD.WIN.1.1 Installer-10037.3 Setup" Qualcomm Drivers
3) Put phone in MTP connection
4) Following commands in adb
Code:
adb shell
su
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
5) open "QPST Configuration"
6) Add port
7) Add Modem port
With these steps, i get manage to get detected in QPST Download and able to make a backup of "*.xqcn". But after editing and restoring, there is no such change. Am i missing something?
Click to expand...
Click to collapse
Can you share the XQCN file with me??
I was able to use QPST and PDC on my OnePlus Nord (AC2003) when it was running Android 10 / Oxygen 10.5
After this weekends update to Android 11 / Oxygen 11 my phone is no longer recognised. I've tried all sorts of USB drivers I could find using some Google Fu, but none of them recognises it anymore.
Does anyone have USB drivers for the OnePlus Nord (AC2003) that works with Android 11?
Thank you
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Jaansburger said:
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Click to expand...
Click to collapse
Thank you for this. Managed to get mine working with VoLTE and VoWIFI.
I have added all the drivers needed and some instructions here : https://gitlab.com/sorinfatu/opnord-volte-vowifi
If anyone wants to contribute to the profiles list feel free.
Thank you again Jaansburger
Jaansburger said:
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Click to expand...
Click to collapse
No need to root?
Thanks
ippo18 said:
No need to root?
Thanks
Click to expand...
Click to collapse
Nope, no need
Jaansburger said:
Nope, no need
Click to expand...
Click to collapse
Thanks, I got blocked at the PDC step: no options available in the devices list.
Do I need a special version of PDC?
Tks
Thanks, it worked in the end, good job!
sorfat said:
Thank you for this. Managed to get mine working with VoLTE and VoWIFI.
I have added all the drivers needed and some instructions here : https://gitlab.com/sorinfatu/opnord-volte-vowifi
If anyone wants to contribute to the profiles list feel free.
Thank you again Jaansburger
Click to expand...
Click to collapse
I have no gitlab account, you may add, on the profiles Markdown file:
WindTre Italy ---> Italy-Volte-Vodafone profile works properely!
ippo18 said:
I have no gitlab account, you may add, on the profiles Markdown file:
WindTre Italy ---> Italy-Volte-Vodafone profile works properely!
Click to expand...
Click to collapse
Done
Just curious if anyone's tried the method of adding MBNs to this phone yet? Basically using the method for ROG Phone 2 or 3. Want to see if anyone's had success first before I try it.
Some what noob here, What is MBN?
Specifically: https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/
I know this method worked for me on ROG Phone 2,but I'm not sure if it would work on ROG Phone 5. The method of doing this seems pretty uniform across devices. But Im guessing we probably need a compatiable MBN (To answer your question, in this case, its a file that has config information for the modems to use carrier features, such as VOLTE and VOWIFI in some cases).
xbamaris1` said:
Specifically: https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/
I know this method worked for me on ROG Phone 2,but I'm not sure if it would work on ROG Phone 5. The method of doing this seems pretty uniform across devices. But Im guessing we probably need a compatiable MBN (To answer your question, in this case, its a file that has config information for the modems to use carrier features, such as VOLTE and VOWIFI in some cases).
Click to expand...
Click to collapse
I am unable to run DIAG mode on my ROG 5. Had a ROG 2 previously so I knew the steps.
Nchls said:
I am unable to run DIAG mode on my ROG 5. Had a ROG 2 previously so I knew the steps.
Click to expand...
Click to collapse
Hey Mate, Did you ever figure it out ?
xbamaris1` said:
Specifically: https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/
I know this method worked for me on ROG Phone 2,but I'm not sure if it would work on ROG Phone 5. The method of doing this seems pretty uniform across devices. But Im guessing we probably need a compatiable MBN (To answer your question, in this case, its a file that has config information for the modems to use carrier features, such as VOLTE and VOWIFI in some cases).
Click to expand...
Click to collapse
I don't believe anybody has been successful with injecting MBNs to unofficially support VoLTE & VoWiFi features that aren't officially supported out of the box on Rog 5.
I'm crazily checking every few hours (xda and Google) to see if somebody has managed to do it, especially for Australian carriers, who are all unsupported as far as those features are considered. I'm also secretly hoping that ASUS themselves will implement them for our market, but I've been hoping for too long.
nexusnerdgeek said:
I don't believe anybody has been successful with injecting MBNs to unofficially support VoLTE & VoWiFi features that aren't officially supported out of the box on Rog 5.
I'm crazily checking every few hours (xda and Google) to see if somebody has managed to do it, especially for Australian carriers, who are all unsupported as far as those features are considered. I'm also secretly hoping that ASUS themselves will implement them for our market, but I've been hoping for too long.
Click to expand...
Click to collapse
Thanks Mate! Happy to know Im not alone, for the past few days I was battling with old posts, codes and stuff to make something work.
So far from what I have learned, the PDC mode / Diag mode is closed in Android 11.
But OnePlus guys, Zenfone guys have found loops that makes it work. So far for the ROG, nothing ...
Has anybody figured anything out?
nexusnerdgeek said:
I don't believe anybody has been successful with injecting MBNs to unofficially support VoLTE & VoWiFi features that aren't officially supported out of the box on Rog 5.
I'm crazily checking every few hours (xda and Google) to see if somebody has managed to do it, especially for Australian carriers, who are all unsupported as far as those features are considered. I'm also secretly hoping that ASUS themselves will implement them for our market, but I've been hoping for too long.
Click to expand...
Click to collapse
JazonX said:
Thanks Mate! Happy to know Im not alone, for the past few days I was battling with old posts, codes and stuff to make something work.
So far from what I have learned, the PDC mode / Diag mode is closed in Android 11.
But OnePlus guys, Zenfone guys have found loops that makes it work. So far for the ROG, nothing ...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hey guys anybody figured anything out?
With all the flurry of highly appreciable recent community development work -- such as twrp and custom kernels -- I remain hopeful that unofficial VoLTE and VoWiFi support (for the carriers ASUS hasn't implemented) might be probable, if not possible, in the near future.
I'm going bananas checking all of the threads on XDA so many times everyday! I have no skills myself to accomplish this, but I'm happy to pay some community members who may .
nexusnerdgeek said:
With all the flurry of highly appreciable recent community development work -- such as twrp and custom kernels -- I remain hopeful that unofficial VoLTE and VoWiFi support (for the carriers ASUS hasn't implemented) might be probable, if not possible, in the near future.
I'm going bananas checking all of the threads on XDA so many times everyday! I have no skills myself to accomplish this, but I'm happy to pay some community members who may .
Click to expand...
Click to collapse
Go through my progress in this thread ~ (Edit)
I managed upload a MBN to the first slot as well, But never got a hold of VoLTE.
Give it a try if you have some spare time, Maybe you might be able to succeed.
JazonX said:
Go through my progress in this thread. .
I managed upload a MBN to the first slot as well, But never got a hold of VoLTE.
Give it a try if you have some spare time, Maybe you might be able to succeed.
Click to expand...
Click to collapse
May want to double check the link
JazonX said:
Go through my progress in this thread ~ (Edit)
I managed upload a MBN to the first slot as well, But never got a hold of VoLTE.
Give it a try if you have some spare time, Maybe you might be able to succeed.
Click to expand...
Click to collapse
Thanks JazonX for your follow up. I've consulted that rather informative thread.
Although I prefer Linux in general, to get VoLTE/VoWiFi working on Rog Phone 5 for my preferred mobile carrier ASUS lacks support for, I'll tolerate Windows 10 .
I've installed:
1. platform-tools_r31.0.2-windows (for adb/fastboot etc.)
2. Qualcomm_USB_Driver_v1.0.zip (from https://gsmusbdriver.com/asus-rog-phone-5)
3. usb_driver_r13-windows.zip (from https://gsmusbdriver.com/asus-rog-phone-5)
4. EfsTools 0.14.0.14 (from https://github.com/JohnBel/EfsTools/releases/tag/v.0.14 for efstools to execute, had to install dotnet-runtime-5.0.10-win-x64 from https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-5.0.10-windows-x64-installer)
Upon connecting the phone, Windows' Device Manager lists it as "Rog Phone 5" under "Portable Devices".
The "adb devices" works; so is "adb shell". I get successful su prompt. Then executing "setprop sys.usb.config diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" crashes the su prompt (no way of knowing its exit code), however "setprop sys.usb.config rndis,diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl" executes successfully (returning exit code 0).
Then when I execute, "efstools efsInfo", it throws this error message:
Use serial port 'COM3'
Critical error. Access Denied: COM3
(I think COM3 is wrong. I reckon, it ought to be a higher number, though I don't know what it ought to be or how to make such a port available.)
I'm stuck there. Couldn't progress further. Sorry. If supplied, I'll be happy to try any steps required. Thanks.
Edit: My Rog 5 is running Kirisakura_Anakin_R_1.1.0 kernel
JazonX said:
Go through my progress in this thread ~ (Edit)
I managed upload a MBN to the first slot as well, But never got a hold of VoLTE.
Give it a try if you have some spare time, Maybe you might be able to succeed.
Click to expand...
Click to collapse
Yeah I think I am in the same boat. Cannot get a hold of VoLTE. Uploaded Pixel AUNZ Telstra, for my Telstra carrier and no VoLTE or VoWIFI. Damn it.
Hey Vojtek12, glad to meet you, a fellow Telstra user trying to activate VoLTE/VoWiFi on Rog 5.
nexusnerdgeek said:
Hey Vojtek12, glad to meet you, a fellow Telstra user trying to activate VoLTE/VoWiFi on Rog 5.
Click to expand...
Click to collapse
Hey brother, Its rough isn't it. I have tried a bunch of the Pixel MBNs, none worked. I don't really know which ones to try at this point, hoping someone can chime in towards a good direction.
nexusnerdgeek said:
Thanks JazonX for your follow up. I've consulted that rather informative thread.
Although I prefer Linux in general, to get VoLTE/VoWiFi working on Rog Phone 5 for my preferred mobile carrier ASUS lacks support for, I'll tolerate Windows 10 .
I've installed:
1. platform-tools_r31.0.2-windows (for adb/fastboot etc.)
2. Qualcomm_USB_Driver_v1.0.zip (from https://gsmusbdriver.com/asus-rog-phone-5)
3. usb_driver_r13-windows.zip (from https://gsmusbdriver.com/asus-rog-phone-5)
4. EfsTools 0.14.0.14 (from https://github.com/JohnBel/EfsTools/releases/tag/v.0.14 for efstools to execute, had to install dotnet-runtime-5.0.10-win-x64 from https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-5.0.10-windows-x64-installer)
Upon connecting the phone, Windows' Device Manager lists it as "Rog Phone 5" under "Portable Devices".
The "adb devices" works; so is "adb shell". I get successful su prompt. Then executing "setprop sys.usb.config diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" crashes the su prompt (no way of knowing its exit code), however "setprop sys.usb.config rndis,diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl" executes successfully (returning exit code 0).
Then when I execute, "efstools efsInfo", it throws this error message:
Use serial port 'COM3'
Critical error. Access Denied: COM3
(I think COM3 is wrong. I reckon, it ought to be a higher number, though I don't know what it ought to be or how to make such a port available.)
I'm stuck there. Couldn't progress further. Sorry. If supplied, I'll be happy to try any steps required. Thanks.
Edit: My Rog 5 is running Kirisakura_Anakin_R_1.1.0 kernel
Click to expand...
Click to collapse
Make sure your CMDs or powershells are running as admin. Make sure you got the good drivers. I found that having qualcomm drivers was pointless. Just manually install the Diag driver yourself. Thats what I did, in device manager. Also make sure you are using the right COM port, check in device manager for the COM port number.
nexusnerdgeek said:
Thanks JazonX for your follow up. I've consulted that rather informative thread.
Although I prefer Linux in general, to get VoLTE/VoWiFi working on Rog Phone 5 for my preferred mobile carrier ASUS lacks support for, I'll tolerate Windows 10 .
I've installed:
1. platform-tools_r31.0.2-windows (for adb/fastboot etc.)
2. Qualcomm_USB_Driver_v1.0.zip (from https://gsmusbdriver.com/asus-rog-phone-5)
3. usb_driver_r13-windows.zip (from https://gsmusbdriver.com/asus-rog-phone-5)
4. EfsTools 0.14.0.14 (from https://github.com/JohnBel/EfsTools/releases/tag/v.0.14 for efstools to execute, had to install dotnet-runtime-5.0.10-win-x64 from https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-5.0.10-windows-x64-installer)
Upon connecting the phone, Windows' Device Manager lists it as "Rog Phone 5" under "Portable Devices".
The "adb devices" works; so is "adb shell". I get successful su prompt. Then executing "setprop sys.usb.config diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" crashes the su prompt (no way of knowing its exit code), however "setprop sys.usb.config rndis,diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl" executes successfully (returning exit code 0).
Then when I execute, "efstools efsInfo", it throws this error message:
Use serial port 'COM3'
Critical error. Access Denied: COM3
(I think COM3 is wrong. I reckon, it ought to be a higher number, though I don't know what it ought to be or how to make such a port available.)
I'm stuck there. Couldn't progress further. Sorry. If supplied, I'll be happy to try any steps required. Thanks.
Edit: My Rog 5 is running Kirisakura_Anakin_R_1.1.0 kernel
Click to expand...
Click to collapse
Hey Mate,
Would you be able to check your driver version from the control panel?
This is mine;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The drive in the above folder has an older version (From 2019 - before the ROG 5).
Most sites do not update their drive files, just keep reposting the same one.
Try to find a newer one if you can, Im just checking whether I saved the exe file, as I too finally got it off a random site.
The latest version I found was 1.00.61
JazonX said:
Hey Mate,
Would you be able to check your driver version from the control panel?
This is mine;
View attachment 5412659
The drive in the above folder has an older version (From 2019 - before the ROG 5).
Most sites do not update their drive files, just keep reposting the same one.
View attachment 5412661
Try to find a newer one if you can, Im just checking whether I saved the exe file, as I too finally got it off a random site.
The latest version I found was 1.00.61
Click to expand...
Click to collapse
The Qualcomm USB Drivers For Windows I had was 1.0.0.57. I've download at least half a dozen from the Net. Unfortunately, everything turned out to be even lower than .57! Would appreciate if you can supply me .61 from your downloads. Or perhaps URL from where you have downloaded yours from, which I understand isn't easy to figure out .
nexusnerdgeek said:
Thanks JazonX for your follow up. I've consulted that rather informative thread.
Although I prefer Linux in general, to get VoLTE/VoWiFi working on Rog Phone 5 for my preferred mobile carrier ASUS lacks support for, I'll tolerate Windows 10 .
I've installed:
1. platform-tools_r31.0.2-windows (for adb/fastboot etc.)
2. Qualcomm_USB_Driver_v1.0.zip (from https://gsmusbdriver.com/asus-rog-phone-5)
3. usb_driver_r13-windows.zip (from https://gsmusbdriver.com/asus-rog-phone-5)
4. EfsTools 0.14.0.14 (from https://github.com/JohnBel/EfsTools/releases/tag/v.0.14 for efstools to execute, had to install dotnet-runtime-5.0.10-win-x64 from https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-5.0.10-windows-x64-installer)
Upon connecting the phone, Windows' Device Manager lists it as "Rog Phone 5" under "Portable Devices".
The "adb devices" works; so is "adb shell". I get successful su prompt. Then executing "setprop sys.usb.config diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" crashes the su prompt (no way of knowing its exit code), however "setprop sys.usb.config rndis,diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl" executes successfully (returning exit code 0).
Then when I execute, "efstools efsInfo", it throws this error message:
Use serial port 'COM3'
Critical error. Access Denied: COM3
(I think COM3 is wrong. I reckon, it ought to be a higher number, though I don't know what it ought to be or how to make such a port available.)
I'm stuck there. Couldn't progress further. Sorry. If supplied, I'll be happy to try any steps required. Thanks.
Edit: My Rog 5 is running Kirisakura_Anakin_R_1.1.0 kernel
Click to expand...
Click to collapse
JazonX said:
Hey Mate,
Would you be able to check your driver version from the control panel?
This is mine;
View attachment 5412659
The drive in the above folder has an older version (From 2019 - before the ROG 5).
Most sites do not update their drive files, just keep reposting the same one.
View attachment 5412661
Try to find a newer one if you can, Im just checking whether I saved the exe file, as I too finally got it off a random site.
The latest version I found was 1.00.61
Click to expand...
Click to collapse
Hey man, and for our fellow Telstra mates. I have found an MBN that semi-works for me, from the mi9t. It is the Korean SKT. It holds VoLTE forever, but the calls end immediately. I am not sure what that means.
nexusnerdgeek said:
Hey Vojtek12, glad to meet you, a fellow Telstra user trying to activate VoLTE/VoWiFi on Rog 5.
Click to expand...
Click to collapse
Hey man, and for our fellow Telstra mates. I have found an MBN that semi-works for me, from the mi9t. It is the Korean SKT. It holds VoLTE forever, but the calls end immediately. I am not sure what that means.