Hi all,
I would like to know how to enable *diagnose mode* on Realme GT 5G because I want to run scat (https://github.com/fgsect/scat.git) to collect 5G NR signalling. Anything would be appreciated.
Thanks
are you looking for
*#*#426#*#*
Click to expand...
Click to collapse
@grown_man Thanks. But not this one, I mean diagnose mode is the mode to export Qualcomm processor's diag port to OS or USB. So I can use scat to collect baseband info such as LTE/5G signalling.
number 1 didnt work for me so i tried 2nd solution but i got some driver issues. i hope u wont face any issues
with this driver its ok
Enable DIAG Mode or COM Port on any Android Smartphone / Tablet
Want to activate Diag Mode or Enable Qualcomm Diagnostic Mode on your Android Phone or Tablet? Follow the 3 methods listed here and enable Diag COM port.
www.gizmoadvices.com
*updated post for driver information
Thank you @grown_man. Unfortunately, it failed on my phone. After running `setprop sys.usb.config diag,adb`, the phone automatically disconnects from the laptop and I can not re-connect it unless I re-active developer option.
WingPig99 said:
Hi all,
I would like to know how to enable *diagnose mode* on Realme GT 5G because I want to run scat (https://github.com/fgsect/scat.git) to collect 5G NR signalling. Anything would be appreciated.
Thanks
Click to expand...
Click to collapse
*#*#717717#*#*
The link @grown_man supplied has the code incorrectly. The code starts with *#*# and not #*#*.
Related
After I seen two threads regarding QPST/CDMA Workshop, I decided to give it a try too.
However, I had the problem with drivers, which I luckily solved.
Drivers source: http://catalog.update.microsoft.com...updateid=14df499c-c71f-4152-a63b-1c1e40cfc14c
So, here's the solution for everyone:
1. Unzip the attached archive.
2. adb shell, su, echo 1 > /sys/devices/virtual/usb_composite/modem/enable
3. Open Device Manager. Under unknown devices you'll find two "SEMC HSUSB" devices.
4. For both, install drivers from the folder.
You'll get unsigned driver warning, ignore and continue with installation.
5. Reboot phone.
6. adb shell, su, echo 1 > /sys/devices/virtual/usb_composite/diag/enable
7. QPST/CDMA workshop should detect the phone now.
I won't link QPST (I don't know if there are any copyright barriers), but you can find it extremely easy on Google. You want QPST 2.7 build 355.
If you're asked for SPC code, it's default 000000.
Now, I need testers: anyone with locked bootloader, or bootloader unlocked with Omnius/SEtool, please open EFS Explorer and tell me if there's anything inside cert, client-cert and client-key folders. Alternatively, try to find any SE/SEMC certificates in EFS.
Best regards
64 bit vista won't let me install. any chances you can make this.
trent6gol said:
64 bit vista won't let me install. any chances you can make this.
Click to expand...
Click to collapse
Strange. What error are you getting?
Thanks no error messages at all!
Good. Is your bootloader locked?
No new hardware are detected, even with modem enable set to 1
Im in Xperia arc unlocked by setool
Alejandrissimo said:
No new hardware are detected, even with modem enable set to 1
Im in Xperia arc unlocked by setool
Click to expand...
Click to collapse
Just turn on modem mode and install provided drivers for both HSUSB devices in Device Manager.
Blagus said:
Just turn on modem mode and install provided drivers for both HSUSB devices in Device Manager.
Click to expand...
Click to collapse
When I set the modem to 1 the adb stop working and the sa102 dissapear from the device manager but there is now new hardware detected.
Yes, that's what should happen - you should have two or three HSUSB devices under unknown ones. Install drivers for them.
Blagus said:
Yes, that's what should happen - you should have two or three HSUSB devices under unknown ones. Install drivers for them.
Click to expand...
Click to collapse
Nop. There is no unknown devices at all :S
Im runing a custom kernel, maybe need to run stock?
link up my video also and claim its yours atleast give credit
also guys if your on stock rom verizon to enter DIAG mode you enter ##3424
edokassiah said:
link up my video also and claim its yours atleast give credit
also guys if your on stock rom verizon to enter DIAG mode you enter ##3424
Click to expand...
Click to collapse
Which video?
Fyi for those using cdma workshop, You dont need to do the adb commands, phone wont "read" the info for general stuff, just goto security, send the spc code, it will unlock, then continue to upload your PRL stuff and change nam settings. Worked fine. =)
what is this exactly? and what is DIAG/QPST/CDMA workshop?
For cdma phones to change out which carrier its on, you need diag mode (which is the programming mode thats seperate from rom flashing as it tells the phone which tower to connect to) qpst and cdma workshop, are tools we use to program this stuff easier. Cdma workshop costs 100$ for a license tho.
x64 Drivers that WORK!!!!!!!!!!!
i dunno if this even matters anymore but i just made these x64 drivers and they have been tested and work just fine htey are not signed but they will install on win 7 x64
Will this driver let us who use custom rom to using DIAG mode?
since most of custom ROM kill the DIAG ability, so nothing will happen when u press #3424
no they wont unforutnatly
I have found about 10 various manuals how to do it and I tried all of them to activate this mode but unsuccessfully. I heared somewhere that it disabled in Android kernel, so may be someone knows how to enable or to get it round or something? I will explain why do I need it: I want to connect with phone by QPST to unlock Bands like described here - https://forum.xda-developers.com/cr...ad-progress-please-leave-im-updating-t2871269. I just thought that if E2312 has the same SOC on a bort as his brothers so it could be possible to unlock LTE Bands on it. But It contained in NVM of the Quallcomm processor.
If anyone has some experience or any idea how to realize it - make me know please.
Hello everyone,
I've been browsing this forum to figure out the answer to this.
I am trying to get the IMEI of a connected Android device, the fastest way possible.
From what I have been reading, there are two paths from here.
1. Going the ADB way: if I use this I need to enable the developer mode, and then USB debugging. Is there a way to enable developer mode without having to tap seven times on the build number?
2. Not using ADB. Is there a way to get the IMEI without using ADB? So far I haven't found any.
Thanks in advance for your help!
soviel said:
Hello everyone,
I've been browsing this forum to figure out the answer to this.
I am trying to get the IMEI of a connected Android device, the fastest way possible.
From what I have been reading, there are two paths from here.
1. Going the ADB way: if I use this I need to enable the developer mode, and then USB debugging. Is there a way to enable developer mode without having to tap seven times on the build number?
2. Not using ADB. Is there a way to get the IMEI without using ADB? So far I haven't found any.
Thanks in advance for your help!
Click to expand...
Click to collapse
Have you tried *#06# code from your phone dialer to get Imei number of your model
Ashwinrg said:
Have you tried *#06# code from your phone dialer to get Imei number of your model
Click to expand...
Click to collapse
Hi Ashwinrg, thank you for your answer. This is what I am trying to avoid. I would like to have as little manual input as possible.
I am able to do this on iOS devices, via imobiledevices. I just plug the device in and get the IMEI with ideviceinfo
This is what I had to do to fix the Unknown caller ID issue with 4G Calling enabled in the respective SIM settings:
Installed QPST Tool on my computer.
With USB debugging enabled in Developer Settings and Magisk for root access, enabled DIAG mode using adb:
Code:
$ adb shell
surya:/ $ su
surya:/ # setprop sys.usb.config diag,serial_cdev,rmnet,adb
In QPST >> PDC activated the respective profile for Sub0 and Sub1 and removed the originally automatically chosen profile (otherwise it kept reversing the desired setting on reboot).
Checked status with *#*#INFO#*#*.
Can this be done without root, I'm having the same issue on a Meizu device without root access & don't have a option to disable VoLTE
TheInfiniteAndroid said:
Can this be done without root, I'm having the same issue on a Meizu device without root access & don't have a option to disable VoLTE
Click to expand...
Click to collapse
If on an original ROM, there should be a way to access a service menu where you can switch on the diag mode that's necessary to be able to use PDC by using the phone dialer.
You may want to search for how to enable diag mode for your device (on my previous OnePlus with OxygenOS firmware it was somthing like *#*#801#*#* or *#*#808#*#*).
Master One said:
If on an original ROM, there should be a way to access a service menu where you can switch on the diag mode that's necessary to be able to use PDC by using the phone dialer.
You may want to search for how to enable diag mode for your device (on my previous OnePlus with OxygenOS firmware it was somthing like *#*#801#*#* or *#*#808#*#*).
Click to expand...
Click to collapse
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
TheInfiniteAndroid said:
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
Click to expand...
Click to collapse
Do you happen to know if there's a way to find it through Activity Manager, finding it hard to navigate
@TheInfiniteAndroid, sorry, can't help with this, don't know Activity Manager.
Hi, I have switched my profiles on my Mi 8 to DT_Greece to activate VoWiFi and deleted the original ROW_Commercial profile.
Whenever a call is getting through VoWiFi or VoLTE i still get unknown caller ID.
Do you perhaps have any other idea to fix that?
razenxd said:
Hi, I have switched my profiles on my Mi 8 to DT_Greece to activate VoWiFi and deleted the original ROW_Commercial profile.
Whenever a call is getting through VoWiFi or VoLTE i still get unknown caller ID.
Do you perhaps have any other idea to fix that?
Click to expand...
Click to collapse
You may want to try another profile in that case, as there is no other way to solve this.
Master One said:
You may want to try another profile in that case, as there is no other way to solve this.
Click to expand...
Click to collapse
Aah really? That sux
Ι've tried more than the half configs listed and only DT_greece seems to enabling VoWiFi for Vodafone Greece carrier
razenxd said:
Aah really? That sux Ι've tried more than the half configs listed and only DT_greece seems to enabling VoWiFi for Vodafone Greece carrier
Click to expand...
Click to collapse
Indeed, sucks if not working, but I have no other idea. Try the second half of configs as well, maybe there is one that just works with your carrier.
Master One said:
Indeed, sucks if not working, but I have no other idea. Try the second half of configs as well, maybe there is one that just works with your carrier.
Click to expand...
Click to collapse
That's what i'm doing at the moment.
No luck so far
On RN10 Pro my carrier works just fine, I already have extracted the .mbns from RN10 Pro's firmware but now i need to find which one is actually is using and a way to insert it to my device!
Master One said:
This is what I had to do to fix the Unknown caller ID issue with 4G Calling enabled in the respective SIM settings:
Installed QPST Tool on my computer.
With USB debugging enabled in Developer Settings and Magisk for root access, enabled DIAG mode using adb:
Code:
$ adb shell
surya:/ $ su
surya:/ # setprop sys.usb.config diag,serial_cdev,rmnet,adb
In QPST >> PDC activated the respective profile for Sub0 and Sub1 and removed the originally automatically chosen profile (otherwise it kept reversing the desired setting on reboot).
Checked status with *#*#INFO#*#*.
Click to expand...
Click to collapse
Thanks for posting on this, but what do you mean by qpst>>pdc? When I run qpst I see no active devices, pdc doesn't either. So no clue how to proceed.
treebaard said:
Thanks for posting on this, but what do you mean by qpst>>pdc? When I run qpst I see no active devices, pdc doesn't either. So no clue how to proceed.
Click to expand...
Click to collapse
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after connecting?
Master One said:
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after
Master One said:
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after connecting?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yes, up to the step of my phone being recognized, as it isn't automatically recognized at all by qpst config. And since there is no faq of any kind on what to do if the phone isn't recognized by QPST, I'm stuck.
I presume the issue is that I don't see any ports listed in the ports view. But I installed the Qualcomm usb driver already, so not sure how to fix that
per https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-85746887 , did you fix this in LOS 17.1, or 18?
treebaard said:
per https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-85746887 , did you fix this in LOS 17.1, or 18?
Click to expand...
Click to collapse
I'm not a developer and I can't really help as I'm not currently using LOS. You may want to find out if DIAG mode is supported and working in LOS.
TheInfiniteAndroid said:
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
Click to expand...
Click to collapse
PDC you will find it in the folder with the installed program QPST.
I did it. Sorry for my English.
Master One said:
I'm not a developer and I can't really help as I'm not currently using LOS. You may want to find out if DIAG mode is supported and working in LOS.
Click to expand...
Click to collapse
Another user said this procedure worked with LOS 17.1, but not 18.1 which we now run. I don't see a new device added in windows task manager, so I guess something's changed, and the QPST folks need to look into it.
treebaard said:
Another user said this procedure worked with LOS 17.1, but not 18.1 which we now run. I don't see a new device added in windows task manager, so I guess something's changed, and the QPST folks need to look into it.
Click to expand...
Click to collapse
The QPST folks have nothing to do with this, maybe (I mean hopefully) @gardiol can comment on DIAG mode support in the current version of LOS.
Can this have anything to do with the MUIU vs. OSS vendor?
I'm still running an older version of ArrowOS with the MIUI vendor, but possibly the DIAG mode problem came up with the move to OSS vendor?
How to disable pocket mode on oneplus nord 2 5G. _I have a DN2103 version of oxigenOS V11.3 with android 11. This new "feature" has been activated without my permission and I don't see where to turn it off. Thanks.
You can't, the option doesn't exist (for now) in the Oxygen OS version of the Nord 2.
sirwuku said:
You can't, the option doesn't exist (for now) in the Oxygen OS version of the Nord 2.
Click to expand...
Click to collapse
You can already say that you have seen one that has pocket mode and that to deactivate it you have to go into developer options and uncheck the lock screen, the problem is that the phone is left without any security system (fingerprint, code, etc). OnePlus Spain, after an hour in the chat, we have not been able to find how to disconnect said screen without going into developer options. If you know of any solutions, it would be appreciated. Thanks for answering.
edulcorante1 said:
You can already say that you have seen one that has pocket mode and that to deactivate it you have to go into developer options and uncheck the lock screen, the problem is that the phone is left without any security system (fingerprint, code, etc). OnePlus Spain, after an hour in the chat, we have not been able to find how to disconnect said screen without going into developer options. If you know of any solutions, it would be appreciated. Thanks for answering.
Click to expand...
Click to collapse
The only way I was able to find is with a rooted device, as explained in this thread.
Basically you would go to your Phones files:
Code:
/system/etc/feature_list
Then add:
Code:
,\n {\n "featureName": "OP_FEATURE_ENABLE_POCKETMODE_SWITCH"\n }\n
to the list
Python + MTK client + update DN2103 A19 = working. Update from A19 to A20, ok, wipe data, plus +adb reboot fastboot + fastboot flashing lock= bootloader lock. In original recovery delete data and reboot. Install official update and no more re-rooting the phone, at least this one. I give it to a family member. The order of the bootloader lock is not exact, but if it is done after installing update 20 it is done with a single command.
How can I turn off pocket mode on a OnePlus Nord 2 5G with a DN2103 version of OxygenOS V11.3 and Android 11, Flip an image as it was activated without my consent and I cannot locate the option to disable it?
vinny000 said:
How can I turn off pocket mode on a OnePlus Nord 2 5G with a DN2103 version of OxygenOS V11.3 and Android 11, Flip an image as it was activated without my consent and I cannot locate the option to disable it?
Click to expand...
Click to collapse
Settings>Utility>Pocket Mode
In this case, the proximity sensor has failed. It was canceled and the problem disappeared.
For Android 11, go to "Settings > Utilities > Pocket Mode" to turn the feature off
geometry dash