Hello,
I'm on CM13 for Honor 4x Indian version. My problem is that if I enter into the diag mode by entering the command 'setprop sys.usb.config diag,adb' with sudo privileges the QPST doesn't show the phone as connected.
After the entry of the above command I could see the Qualcomm driver 901D detected by the device manager of Windows 10 lappy. On opening QPST I could see the port getting populated which is same as the port detected by device manager. But the 'Phone ' column says 'No Phone'. And further is I open the QXDM with the port enabled, I dont see the fields enabled like say NV(no white background) and instead shows grey background indicating the phone is not detected. I have another Qualcomm chipset Android smartphone with which I could see the phone getting detected by QPST& QXDM and could see various NV fields.
Please guide me in solving this problem.
Thanks
Embeddednut said:
Hello,
I'm on CM13 for Honor 4x Indian version. My problem is that if I enter into the diag mode by entering the command 'setprop sys.usb.config diag,adb' with sudo privileges the QPST doesn't show the phone as connected.
After the entry of the above command I could see the Qualcomm driver 901D detected by the device manager of Windows 10 lappy. On opening QPST I could see the port getting populated which is same as the port detected by device manager. But the 'Phone ' column says 'No Phone'. And further is I open the QXDM with the port enabled, I dont see the fields enabled like say NV(no white background) and instead shows grey background indicating the phone is not detected. I have another Qualcomm chipset Android smartphone with which I could see the phone getting detected by QPST& QXDM and could see various NV fields.
Please guide me in solving this problem.
Thanks
Click to expand...
Click to collapse
fixed your issue?
Embeddednut said:
Hello,
I'm on CM13 for Honor 4x Indian version. My problem is that if I enter into the diag mode by entering the command 'setprop sys.usb.config diag,adb' with sudo privileges the QPST doesn't show the phone as connected.
After the entry of the above command I could see the Qualcomm driver 901D detected by the device manager of Windows 10 lappy. On opening QPST I could see the port getting populated which is same as the port detected by device manager. But the 'Phone ' column says 'No Phone'. And further is I open the QXDM with the port enabled, I dont see the fields enabled like say NV(no white background) and instead shows grey background indicating the phone is not detected. I have another Qualcomm chipset Android smartphone with which I could see the phone getting detected by QPST& QXDM and could see various NV fields.
Please guide me in solving this problem.
Thanks
Click to expand...
Click to collapse
Is your issue solved? If yes, Can you provide the steps to the solution?
Related
Hello,
I'm on CM13 for Honor 4x Indian version. My problem is that if I enter into the diag mode by entering the command 'setprop sys.usb.config diag,adb' with sudo privileges the QPST doesn't show the phone as connected.
After the entry of the above command I could see the Qualcomm driver 901D detected by the device manager of Windows 10 lappy. On opening QPST I could see the port getting populated which is same as the port detected by device manager. But the 'Phone ' column says 'No Phone'. And further is I open the QXDM with the port enabled, I dont see the fields enabled like say NV(no white background) and instead shows grey background indicating the phone is not detected. I have another Qualcomm chipset Android smartphone with which I could see the phone getting detected by QPST& QXDM and could see various NV fields.
I works be thankful of anyone can help me getting into the diagnostic mode
Thanks in advance
I can't access to fastboot mode, i can't do anything.
PC Recognizes like "QHSUSB_DLOAD" in "devices and printers" but like "Care Suite Emergency Connectivity" in devices manager.
I can't unbrick because in devices manager recognizes like Care Suite Emergency Connectivity and i can't update the driver (for do the classic method for fullbrick)
When i try to install the qualcomm drivers it says that there is a better driver called "care suite emergency connectivity" and does not appear the qualcomm device with the port number.
Someone can help me
My Redmi K20 Pro lost IMEI, MAC Address and Baseband, every "unknown".
I fastboot TWRP and ROOT, activate USB Debug, push in Laptop, enable diagnostic mode by cmd commands, in Device Manager show Port Qualcomm HS-USB Android DIAG 901D (COM4). Open QPST ver 2.7.480, It show My Phone is SM8150. I try to restore QCN with QCN i download on internet (i dont backup it before). It error "Received an invalid command from the phone."
I try QFIL choose Port and Restore but when it run to "Checking if phone is connected...", it repeat "Checking for phone connection: 4" again again and to much again... Finally it notification "Phone is not connected to: 4" and "Restore Fail"
I dont know reason. Anybody can help me, I was stuck for 3 days. Thank you
I think you messed it up badly, take it to a service center and see if you can get it fixed.
Press F to pay respects.
Ps, don't mess with things you don't know how to fix
bacdi said:
My Redmi K20 Pro lost IMEI, MAC Address and Baseband, every "unknown".
I fastboot TWRP and ROOT, activate USB Debug, push in Laptop, enable diagnostic mode by cmd commands, in Device Manager show Port Qualcomm HS-USB Android DIAG 901D (COM4). Open QPST ver 2.7.480, It show My Phone is SM8150. I try to restore QCN with QCN i download on internet (i dont backup it before). It error "Received an invalid command from the phone."
I try QFIL choose Port and Restore but when it run to "Checking if phone is connected...", it repeat "Checking for phone connection: 4" again again and to much again... Finally it notification "Phone is not connected to: 4" and "Restore Fail"
I dont know reason. Anybody can help me, I was stuck for 3 days. Thank you
Click to expand...
Click to collapse
did you manage to fix that?
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Hi I am using LG v40 Version on Hovac 3.8 Custom Rom (Android 10) , rooted with Magisk. I Am trying to Put phone to Diag mode to get it recognized by Qfil to repair its imei. I have tried Services code method , Adb command method as well as terminal command method but my cell is not being recognized as Diag 901d port. Any leads?
Basically in the same boat here.
I have the bootloader unlocked, rooted through magisk, adb and fastboot working fine. I've tried the usual adb commands:
su
setprop sys.usb.config diag,adb
and it does nothing. I've lost count of the amount of dialer codes I've tried. Drivers are installed correctly (EDL mode is recognised just fine).
Any idea about this or does this phone just *not have a diag mode?
(For reference, setprop sys.usb.config mtp,adb does a disconnect then reconnect sound so everything works right.)
Found the problem. The phone *does actually go into diag mode after adb command. It just doesn't say it has and neither does device manager show 901D ports for QFIL. You can backup/restore QCN on QFIL once you've done the adb command; just choose the regular COM port (you'll have to tick show NonQDLoader/Diag Port option in QFIL).
Do tell me if you managed to restore your IMEI. I'm stuck on either 0 or null depending on what I do. Restoring QCN seems to have no effect (through QFIL). Through QPST, I keep getting "invalid command from phone error." Any ideas?
FLAmbuRNE1 said:
Basically in the same boat here.
I have the bootloader unlocked, rooted through magisk, adb and fastboot working fine. I've tried the usual adb commands:
su
setprop sys.usb.config diag,adb
and it does nothing. I've lost count of the amount of dialer codes I've tried. Drivers are installed correctly (EDL mode is recognised just fine).
Any idea about this or does this phone just *not have a diag mode?
(For reference, setprop sys.usb.config mtp,adb does a disconnect then reconnect sound so everything works right.)
Found the problem. The phone *does actually go into diag mode after adb command. It just doesn't say it has and neither does device manager show 901D ports for QFIL. You can backup/restore QCN on QFIL once you've done the adb command; just choose the regular COM port (you'll have to tick show NonQDLoader/Diag Port option in QFIL).
Do tell me if you managed to restore your IMEI. I'm stuck on either 0 or null depending on what I do. Restoring QCN seems to have no effect (through QFIL). Through QPST, I keep getting "invalid command from phone error." Any ideas?
Click to expand...
Click to collapse
only verizon roms doesnt have imei write protection (idk about A10 but for Pie its working)
if you imei on v40 already null you can try this guide
but use v40 verizon rom
on verizon rom for diag mode enable try this hidden menu code ##7764726405 and hit the call button type service code 000000
All guides seem to point towards the device being called HB-USB Diag 901D in the device manager.
I feel like this is a critical step towards being able to write protected NV items.
Trying to connect to the phone using QXDM tools does not work since the phone isn't recognized as being in Diag mode.
I've tried soooo many ways at this point but don't want to give up just yet.
Let me know if anyone has any luck in getting V40 to correctly connect in Diag mode - or prove to me that diag mode is achieved with the hidden menu (I don't see it working for me - guide me in case I'm misunderstanding something).
FLAmbuRNE1 - I stand corrected - via experimentation.
I was not seeing any ports change in Device Manager or any other application after issuing the
Code:
setprop sys.usb.config diag,adb
command as a super user or after enabling the diag port from the hidden menu.
QFIL's QCN Backup+Restore functionality kinda indicated that these commands do indeed make a difference. When QFIL Restoring QCN on my phone I noticed that QFIL was unable to reset the phone after sending data to the phone - unless I had done both of the above steps. As soon as I did, it would be able to restart my phone and verify that restore was completed.
I have some additional experiments on the way to try and figure out the exact memory locations in
Code:
modemst1, modemst2 & fsg
to modify and flash in order to restore my original IMEI. Fingers crossed...
I'll circle back here with what I find, or don't find. If I don't follow up, anyone interested, message me.
setprop sys.usb.config diag,adb
not work
C:\adb>adb shell
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
flashlmdd:/ $ su
flashlmdd:/ # setprop sys.usb.config diag,adb
flashlmdd:/ #
My Chinese version OnePlus 10 pro get into crash dump mode, can't get into bootloader mode. Volume down+up and power button directly leads to crash dump mode. MSM tool requires login and nowhere to get one. Windows device setting shows HS 900 divice.
There's some info displaying? That was caused by some mod or something?
Anyway someone shared the Chinese msmtool, probably you can use it
Xda comment
RokCruz said:
There's some info displaying? That was caused by some mod or something?
Anyway someone shared the Chinese msmtool, probably you can use it
Xda comment
Click to expand...
Click to collapse
just says crash dump mode, no other words. can detect 900E mode.
evanxyj said:
just says crash dump mode, no other words. can detect 900E mode.
Click to expand...
Click to collapse
I just remember that back on my old OP 7 pro when I had a crash dump i take log with QPST software, it automatically reboot into system so you can try it.
Now the process to take the log is this(taken from a telegram group of some old OP7Pro custom ROM)
## CrashDump Logs (Windows Only) ##
Download and Install QPST
Download Archives - QPST Tool
qpsttool.com
Ensure proper OP Drivers
Qualcomm HS_USB
Launch Utility
- Start > QPST > QPST Configuration
Dump Logs
- While on CrashDump screen, plug phone into USB
- Ports tab will display a progress bar and Sahara Memory Dump
Troubleshooting
- During CrashDump screen, Device Manager should list device as Qualcomm HS-USB Diagnostics 900E
- If it does not, right click > Uninstall Device > Delete the driver software for this device
- Reboot and install above driver set
RokCruz said:
I just remember that back on my old OP 7 pro when I had a crash dump i take log with QPST software, it automatically reboot into system so you can try it.
Now the process to take the log is this(taken from a telegram group of some old OP7Pro custom ROM)
## CrashDump Logs (Windows Only) ##
Download and Install QPST
Download Archives - QPST Tool
qpsttool.com
Ensure proper OP Drivers
Qualcomm HS_USB
Launch Utility
- Start > QPST > QPST Configuration
Dump Logs
- While on CrashDump screen, plug phone into USB
- Ports tab will display a progress bar and Sahara Memory Dump
Troubleshooting
- During CrashDump screen, Device Manager should list device as Qualcomm HS-USB Diagnostics 900E
- If it does not, right click > Uninstall Device > Delete the driver software for this device
- Reboot and install above driver set
Click to expand...
Click to collapse
the second i connect the cable, phone restart into crash dump mode, and again. computer detects 900E mode. dont know why it bootloop the crash dump mode upon connect.