Related
anyone can tell me hwo to enter diag mode?
I wanna use qxdm to monitor the radio protocol .thank u very much!
You need the QC diag drivers installed just do a search under mtty just rtask b then you will be prompted to install drivers it installs three devices ,one of them is the ZTE Diagnostics Interface 6000 CDMA , you connect qxdm or qpst via a com port.
I also want to know, but still can not understand what's meknb said,
Can explain more detail how to do.
ex: where to get drivers, what's mtty? Thanks
I had know how to use mtty, and also install the diag driver.
but while i reboot the phone, the diag interface also can not appear.
It only can appear while in bootloader mode(3 color display mode)
So how to let the diag also can appear while in normal mode, and use QXDM to take a log, since i want to catch some call log or data throughtput log.
Thanks.
Don't think you can do that it's either diag mode,normal or download mode.If you put the phone in diag mode in qpst you can use the efs file explorer to download the call and data log i think.
Do You Like To Flash Custom Stuffs On Your Android phone? Or Are You A Developer? But You Can't Able To Do It Because You're Facing Some Problems with Your Adb & fastboot. All Of This Problems Are Only Because Of One Thing And That is Drivers.
And If you agree With Anyone Of This Situations Then You're At The Right Place Because Today I Am Going To Tell You That How You Can Install The Adb Drivers For Your Specific Android Phone On Your Pc.
Adb drivers are necessary if you want to flash a android device through Fastboot mode or if you're a android developer. Usually Our PC installs the adb drivers automatically for the specific android device but sometimes it can't so you have to install it manually.
This will also help you to solve adb errors like Device is offline, USB debugging Authorize pop-up not showing in android And etc adb errors. Make sure that your USB debugging option in developer mode is enabled on your Android device Because without this you can't use adb.
Steps:-
*So first go http://adbdriver.com to and download the "adb driver installer (Universal)". Then extract it.
*Now connect your Android phone to your PC using USB cable. Then Open the application.
*Now you will see something like Adb interface drive and with a red Cross at left side. Make sure to refresh if driver option is not shown.
*Now Just Click On install To install your device adb drivers. Then it will Install the adb drivers for your specific android phone in just under 2 minutes.
*Then Allow The USB debugging On your Android phone. Then the adb drivers will get successfully installed.
*If still adb can't recognize your device then try to connect your phone in PTP Mode instead of MTP or Charging only modes.
*If still it doesn't work for you then Revoke USB debugging Authorizations in developer mode. So that's how you can install the adb drivers for your Android Phone.
Video Tutorial - https://goo.gl/a6QgtH
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Unable to connect to usb
I installed Carbon-cr-5.1-moo-release-bacon-20180202-1444.
I am unable to get usb connection working and having tried many different things...
-I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
-In Android Studio SDK Tools I have installed Google USB Driver v12.
-I have developer options turned on and Android Debugging turned on.
-When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
- when I go into developer options and hit 'select usb configuration' my selection of mtp or whatever is always ignored and charging selectiomn remains
-Device Manager / Portable or Other devices does not have the phone beneathn it.
-When I run adb devices in cmd there are no devices attached.
-I cannot find a OnePlus One adb usb driver. I thought I found one but I have no way to verify and after installing it made no difference
I want to update to the latest rom in case this may be the cause, but after I download it to the phone and click flash
I just get the oneplus icon forever and the recover app twrp does not come up. It used to be there but then after I installed
the first rom after a couple of uses it disappeared for some reason or at least will not boot to it.
When I installed that first custom rom I folowed instructions for rooting and on completion it says to open up the installed
su app but when you open it it says there is a more up to date version but when you try to install that it fails.
Now all the apps that will not run if your app is rooted say it is rooted and all the apps that will not run unless it is rooted
say it is not rooted.
I think I need connection via usb in order to reinstall the twrp recovery app in order to install an up to date rom, hoping this may help
me solve the usb issue, but I cannot get the usb connection working as described above,
any hehlop would be appreciated.
Same Situation
hardya said:
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Click to expand...
Click to collapse
but my phone connects in edl mode just for 10 seconds and then automatic
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
I tried everything but no success yet to find my s22 U as diag mode on the win device manager
Tried via Adb
Tried via *#0808#
Tried via Terminal emulator
Rooter via Magisk
Any help?
Thanks
Samsung Android ADB Interface. It shows the correct device when you install the drivers. First he Diagnostics menu is on the phone, you don't need to plug it into your PC.
Dial *#0*# for one of the menus.
Try *#9090#
Also google "S22 DIALER CODES".
Download the Official Samsung Mobile USB drivers from the samsung site in order to get your device to show up in device manager in Windows, BTW.
g2g if I don't want to get slapped by my old lady for being on the puter again.
...
?!!
perfectswanson said:
Samsung Android ADB Interface. It shows the correct device when you install the drivers. First he Diagnostics menu is on the phone, you don't need to plug it into your PC.
Dial *#0*# for one of the menus.
Try *#9090#
Also google "S22 DIALER CODES".
Download the Official Samsung Mobile USB drivers from the samsung site in order to get your device to show up in device manager in Windows, BTW.
g2g if I don't want to get slapped by my old lady for being on the puter again.
...
?!!
Click to expand...
Click to collapse
Yea i went through the Dm+Modem+Adb option by *#0808# but does not show on device manager as Diag.
i have the samsung drivers from their site
Yeah, cause it's not going to. Read my post.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
For Service Mode,
DIAL:
*#27663368378#
Also Check this out:
perfectswanson said:
Yeah, cause it's not going to. Read my post.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
For Service Mode,
DIAL:
*#27663368378#
Also Check this out:
Click to expand...
Click to collapse
Nothing changed.
It doesn't change the device in device manager when you change the USB mode. It always says the same thing, only time the device changes in device manager, is when it's in fastboot mode, Download Mode, or EDL mode. You can change the usb settings back and forth and it will not change the device in windows. I think we're talking about different things. Try Holding Vol+ While plugging in the phone to the computer, while the phone is off, AND without touching the side-key or power button. But I think that is just High Verbosity logging. Just out of curiosity, what are you trying to accomplish?
All guides i saw show the phone as Diag on the win device manager...
I lost my imei. You have replied my other post asking about the phone is Sm-s908e.
I'm trying to backup Qcn so i can rewrite imei
Following this guide https://www.hovatek.com/forum/thread-26051.html
But not success to put the phone on Diag mode to be recognized on Qfil
Now I'm trying to flash original rom to see any change
Thanks for the help
I have managed to put the phone on diag mode using Adb.
There was a diferent code on Adb
I was using: "
Code:
setprop sys.usb.config diag,adb
"
And the code that managed to put the s22U into diag is: "
Code:
setprop sys.usb.config rndis,diag,adb
"
(Thx to this This thread)
Now that i have access to my Qcn file it looks corrupted (Or encrypted) comparing to a generic Qcn that i found here on the forum
looking what i can accomplish