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
Related
Dear Folks,
I want to access the diagnosis port on my Nexus 5x on Linux machine to run a python script to extract the UE logs. This is my first post in XDA Forum.
Do I need to have a driver if I am working on Linux environment? My phone is rooted and I can view the device shown when I ran adb devices. Does this mean that I have the correct drivers installed? I tried the command setprop sys.usb.config diag,adb and it was accepted without any errors.
Where can I find the drivers to enter into diagnostic mode on Nexus 5x on my Linux machine? After this, how can I find the correct diagnostic port on my device?
ashishkurian said:
Dear Folks,
I want to access the diagnosis port on my Nexus 5x on Linux machine to run a python script to extract the UE logs. This is my first post in XDA Forum.
Do I need to have a driver if I am working on Linux environment? My phone is rooted and I can view the device shown when I ran adb devices. Does this mean that I have the correct drivers installed? I tried the command setprop sys.usb.config diag,adb and it was accepted without any errors.
Where can I find the drivers to enter into diagnostic mode on Nexus 5x on my Linux machine? After this, how can I find the correct diagnostic port on my device?
Click to expand...
Click to collapse
You shouldn't need any drivers.
Since you're working eith USB comnectivity, you might need to make sure that you have libUSB and Udev rules properly setup for your device, but if you have adb and commands are working then you might have it all correct already.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You shouldn't need any drivers.
Since you're working eith USB comnectivity, you might need to make sure that you have libUSB and Udev rules properly setup for your device, but if you have adb and commands are working then you might have it all correct already.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you Droidriven, Can you then help me how I can identify the diagnostic port coming up on my machine?
ashishkurian said:
Thank you Droidriven, Can you then help me how I can identify the diagnostic port coming up on my machine?
Click to expand...
Click to collapse
I don't know the answer to that part, I'll try to find what you need.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
The basic setprop command used here is useful for every android but I am able to do it WITHOUT ROOT on the MetroPCS Coolpad Defiant 3632A. I stumbled across this playing around in the Net Monitor trying to obtain the Communications section password (still haven't yet..). I was unable to do this earlier by simply putting in "adb shell setprop sys.usb.config diag,adb". So enabling Download Mode assisted in this i'm assuming. Else I have something other I have configured that assisted with or without that mode enabled. The below should be correct though..
1. Download Quick Shortcut Maker
2. Open and under "Activities" scroll down to "Net Monitor". Launch the one directly below it - "com.yulong.android.cp_engmode/
com.yulong.android.cp_engmode.CPEngMode"
3. Scroll down to DownLoad mode on/off, press this and turn it on.
4. Open CMD (need ADB installed and setup) then type in this "adb shell setprop sys.usb.config diag,adb"
5. Check Device Manager and you will see the COM port open! Make sure you have the drivers installed.
RESET? BEFORE YOU REBOOT - RUN -> adb shell "setprop sys.usb.config charge_only,adb" or mtp,adb -> SHOULD RESET IT. AND OR REBOOT THEN -> unplug usb / plug back in and select File Transfer to correct the misconfigured drivers. Also disable and re enable USB Debugging to get ADB Device Interface back.
That's it!
-phonecapone
lol ...... Now for some reason I do not need to go through all the steps... Simply putting into CMD "adb shell setprop sys.usb.config diag,adb" enables DIAG. I need others to test and confirm this on their 3632A's. Earlier I was unable to do this. So perhaps there is a setting i enabled that i missed in my steps. I will be wiping the whole phone after an IMEI repair then I will try again and update this thread.
Thanks
Thanks for sharing!
No problem! =]
I found a way to enable the AT Modem also. I have seemed to enable something in diagnostics that has permanently enabled diag and modem ports if I do not have any operation selected for USB (default = charging). Getprop returns the same thing as it did before too.
help me
z3x5343 said:
help me
Click to expand...
Click to collapse
With what do you need assistance?
I need help as well
phonecapone said:
With what do you need assistance?
Click to expand...
Click to collapse
You think you can help me root my Coolpad 3632A?
TheRealDyNaMiX said:
You think you can help me root my Coolpad 3632A?
Click to expand...
Click to collapse
I'm not totally sure about a root for this phone. I *had* what should have been just a temporary root but when i rebooted it seemed to stick. I don't remember everything I did else I could help (yeah i need to keep more notes!). I still have the Coolpad 3632A I used but the problem is it is bricked (i did intentionally so I could unbrick it - learning purposes) and I haven't had time to unbrick it yet.
I can say though the method I used is the same that is on the coolpad toolkit (the one for a generic root i think it was) and you can find it searching through Coolpad threads on here or by downloading the coolpad toolkit which i think is posted around here on XDA somewhere.
phonecapone said:
I'm not totally sure about a root for this phone. I *had* what should have been just a temporary root but when i rebooted it seemed to stick. I don't remember everything I did else I could help (yeah i need to keep more notes!). I still have the Coolpad 3632A I used but the problem is it is bricked (i did intentionally so I could unbrick it - learning purposes) and I haven't had time to unbrick it yet.
I can say though the method I used is the same that is on the coolpad toolkit (the one for a generic root i think it was) and you can find it searching through Coolpad threads on here or by downloading the coolpad toolkit which i think is posted around here on XDA somewhere.
Click to expand...
Click to collapse
I got the Coolpad Toolkit, but the Coolpad 3632A isn't supported yet, how did you get the root?
phonecapone said:
I'm not totally sure about a root for this phone. I *had* what should have been just a temporary root but when i rebooted it seemed to stick. I don't remember everything I did else I could help (yeah i need to keep more notes!). I still have the Coolpad 3632A I used but the problem is it is bricked (i did intentionally so I could unbrick it - learning purposes) and I haven't had time to unbrick it yet.
I can say though the method I used is the same that is on the coolpad toolkit (the one for a generic root i think it was) and you can find it searching through Coolpad threads on here or by downloading the coolpad toolkit which i think is posted around here on XDA somewhere.
Click to expand...
Click to collapse
Actually, I found the basic toolkit, but whenever i try to root with ADB Sideload, I keep getting an "Error 21" and E:unknown volume for path [/sideload/package.zip], I booted into android and i still didn't have the root.
TheRealDyNaMiX said:
Actually, I found the basic toolkit, but whenever i try to root with ADB Sideload, I keep getting an "Error 21" and E:unknown volume for path [/sideload/package.zip], I booted into android and i still didn't have the root.
Click to expand...
Click to collapse
Try one of the other root options that doesn't use adb sideload.
How to support the lineageOS rom to open the Qualcomm diag port
This is the development section of the Pixel 2 Forum and is not for people to ask questions. Any questions you do have need to be directed to the Q&A section of the Pixel 2 forum and not here
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)
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
Since Android 11 - VOLTE fails to work my carrier (Telstra AU) which worked perfectly on AOSP and MIUI with codes.
These below setprop commands require root.
And require these drivers or the qualcomm one atleast.
Xiaomi Poco F2 Pro USB Driver for Windows (Official Mobile Driver)
Download the official Xiaomi Poco F2 Pro USB Driver for your Xiaomi Mobile. We also provide all other Xiaomi Mobile drivers for free.
gsmusbdriver.com
Instructions for setting up EFS tools - this modded version is the only one that writes the mbn files correctly.
[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
And uploading the mbn instructions are in this post.
It took me ages to find the right setprop command to open the diag port. The below setprop commands work on MIUI or AOSP.
setprop sys.usb.config diag,diag_mdm,adb
This will open two com ports in device manage. You can only use the MDM one.
Then it will work with QPST, EFS Expolorer by selecting that port.
To use PDC you must use a different setprop command.
setprop sys.usb.config diag,diag_mdm,serial_cdev,rmnet,adb
adb shell
su
then setprop command.
Unplugging the USB cable will reset the setprop.
I have written the required mbn to /nv in the EFS however the ims_user_agent (/nv/item_files/ims) won't stick after a reboot which reverts to default. My carrier requires that file to have a header in it or it fails to register with their IMS server therefore no VOLTE on Android 11. The below link describes what's happening best.
https://c.mi.com/thread-3571499-1-0.html
I accomplished this task with efstools in the above link - it can be done with EFS Explorer but it doesn't write the files with the correct mode permissions.
I know there's a fair bit of info here, I share this incase anyone figures out a work around to fix this issue. I have tried all 4 Android 11 firmware's and they all do the same thing. Let me know if there's any questions.
I suggest to join the MIUI bugs telegram channel and complain that VOLTE isn't working.
https://c.mi.com/thread-2413060-1-0.html
Thank you. I recently bought a Mi 11 Ultra running EU ROM. Currently on Android 11 MIUI 12.5.12 and no VoLTE or VoWiFi. I am going to join the Telegram bug group to report the issue.
Edit: couldn't figure out the Telegram stuff so deleted the app. How else can I contact Xiaomi?