Cannot connect in Diag mode on Aquaris X2
Cannot connect in Diag mode on Aquaris X2
05-10-2024, 05:48 PM
(04-10-2024, 09:02 PM)justshez(04-10-2024, 08:52 PM)VinceLx(04-10-2024, 08:27 PM)justshez(04-10-2024, 08:15 PM)VinceLx When I wrote: no changes, I meant: no changes in Device Manager.To troubleshoot further, could you please uninstall the previous Qualcomm drivers you installed, restart your PC, and then run the diag command again? Additionally, would you mind taking a screenshot of how your phone is being detected in device manager after running the command? This will help better understand the issue
All this section is about Device Manager:
"When I run adb devices: I get the serial number, no changes in Device Manager
"When I run adb shell, then su: no changes
"When I run setprop sys.usb.config diag,adb: I see the phone under Other devices: Active 1, with an exclamation mark.
I confirm the phone is rooted with Magisk.
I confirm that I gave access to SharedUID Shell as SU in Magisk.
Attached is the screenshot.
Nevertheless, I cannot enter Diag mode.
So I uninstalled the Qualcomm drivers, no more references about Qualcomm in Programs and features. As I mentioned previously, there was only one line related to Qualcomm: Qualcomm USB drivers, appearing after I installed the driver "Qualcomm USB Driver V1.0". But there was no new line when I installed "Qualcomm_Diag_QD_Loader_2016_driver". So not sure if this was properly uninstalled.
After removal I restarted the PC, and run the Diag command. Here are the screenshot, before (DM1 ) and after (DM2 ) I run the Diag command.
Kindly follow the instructions shared by @maxpayne above.
Update the Active 1 driver manually, please use the Qualcomm diag driver, which is available for download via the attached mega link. He also included a video tutorial to help you through the process.
Thank you both.
Unfortunately it did not work.
I first tried to update manually the Diag driver without installing previously the Qualcomm USB driver, but it did not work.
Then I installed the Qualcomm USB driver and tried again to install manually the Diag driver: same issue.
See attached the message from Windows.
I tried to install the driver from folder C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers
I have an Intel processor.
Out of curiosity I tried to install from the other folders, but no luck
This post was last modified: 05-10-2024, 05:53 PM by VinceLx.
05-10-2024, 06:40 PM
(05-10-2024, 05:48 PM)VinceLx(04-10-2024, 09:02 PM)justshez(04-10-2024, 08:52 PM)VinceLx(04-10-2024, 08:27 PM)justshez(04-10-2024, 08:15 PM)VinceLx When I wrote: no changes, I meant: no changes in Device Manager.To troubleshoot further, could you please uninstall the previous Qualcomm drivers you installed, restart your PC, and then run the diag command again? Additionally, would you mind taking a screenshot of how your phone is being detected in device manager after running the command? This will help better understand the issue
All this section is about Device Manager:
"When I run adb devices: I get the serial number, no changes in Device Manager
"When I run adb shell, then su: no changes
"When I run setprop sys.usb.config diag,adb: I see the phone under Other devices: Active 1, with an exclamation mark.
I confirm the phone is rooted with Magisk.
I confirm that I gave access to SharedUID Shell as SU in Magisk.
Attached is the screenshot.
Nevertheless, I cannot enter Diag mode.
So I uninstalled the Qualcomm drivers, no more references about Qualcomm in Programs and features. As I mentioned previously, there was only one line related to Qualcomm: Qualcomm USB drivers, appearing after I installed the driver "Qualcomm USB Driver V1.0". But there was no new line when I installed "Qualcomm_Diag_QD_Loader_2016_driver". So not sure if this was properly uninstalled.
After removal I restarted the PC, and run the Diag command. Here are the screenshot, before (DM1 ) and after (DM2 ) I run the Diag command.
Kindly follow the instructions shared by @maxpayne above.
Update the Active 1 driver manually, please use the Qualcomm diag driver, which is available for download via the attached mega link. He also included a video tutorial to help you through the process.
Thank you both.
Unfortunately it did not work.
I first tried to update manually the Diag driver without installing previously the Qualcomm USB driver, but it did not work.
Then I installed the Qualcomm USB driver and tried again to install manually the Diag driver: same issue.
See attached the message from Windows.
I tried to install the driver from folder C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers
I have an Intel processor.
Out of curiosity I tried to install from the other folders, but no luck
In the IMEI/baseband instruction manual, it says to flash the 4 partitions in fastboot: patched_vsmart, fsg, modemst1, modemst2. I hope that was also done.
You may need to use a different PC to run the diag command again.
06-10-2024, 01:51 PM
(05-10-2024, 06:40 PM)justshez(05-10-2024, 05:48 PM)VinceLx(04-10-2024, 09:02 PM)justshez(04-10-2024, 08:52 PM)VinceLx(04-10-2024, 08:27 PM)justshez To troubleshoot further, could you please uninstall the previous Qualcomm drivers you installed, restart your PC, and then run the diag command again? Additionally, would you mind taking a screenshot of how your phone is being detected in device manager after running the command? This will help better understand the issue
So I uninstalled the Qualcomm drivers, no more references about Qualcomm in Programs and features. As I mentioned previously, there was only one line related to Qualcomm: Qualcomm USB drivers, appearing after I installed the driver "Qualcomm USB Driver V1.0". But there was no new line when I installed "Qualcomm_Diag_QD_Loader_2016_driver". So not sure if this was properly uninstalled.
After removal I restarted the PC, and run the Diag command. Here are the screenshot, before (DM1 ) and after (DM2 ) I run the Diag command.
Kindly follow the instructions shared by @maxpayne above.
Update the Active 1 driver manually, please use the Qualcomm diag driver, which is available for download via the attached mega link. He also included a video tutorial to help you through the process.
Thank you both.
Unfortunately it did not work.
I first tried to update manually the Diag driver without installing previously the Qualcomm USB driver, but it did not work.
Then I installed the Qualcomm USB driver and tried again to install manually the Diag driver: same issue.
See attached the message from Windows.
I tried to install the driver from folder C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers
I have an Intel processor.
Out of curiosity I tried to install from the other folders, but no luck
In the IMEI/baseband instruction manual, it says to flash the 4 partitions in fastboot: patched_vsmart, fsg, modemst1, modemst2. I hope that was also done.
You may need to use a different PC to run the diag command again.
I had initially flashed these 4 partitions before trying to enter Diag mode, then because I redid the full process of flashing the emergency package several times, I did not flash them before trying again to connect in Diag mode.
So, here is what happened (as I did the very first time)
-I flashed these 4 partitions
-Root disapeared, SU grayed in Magisk, when I type the command "su" it says: No daemon is currently running!
-I flashed again the Magisk_patched.img file, gained access again to root with the command :
fastboot flash boot magisk_patchedX2.img
So maybe the problem is here? This action is against the previous command: fastboot flash boot_a patched_vsmart.img?
Anyway, I tried to install the Diag driver after that, and still not possible
07-10-2024, 03:08 PM
(06-10-2024, 01:51 PM)VinceLxThe patched_vsmart.img is essentially the boot.img file patched with Magisk, so you don't need to root again. Here's what to do next:(05-10-2024, 06:40 PM)justshez(05-10-2024, 05:48 PM)VinceLx(04-10-2024, 09:02 PM)justshez(04-10-2024, 08:52 PM)VinceLx So I uninstalled the Qualcomm drivers, no more references about Qualcomm in Programs and features. As I mentioned previously, there was only one line related to Qualcomm: Qualcomm USB drivers, appearing after I installed the driver "Qualcomm USB Driver V1.0". But there was no new line when I installed "Qualcomm_Diag_QD_Loader_2016_driver". So not sure if this was properly uninstalled.
After removal I restarted the PC, and run the Diag command. Here are the screenshot, before (DM1 ) and after (DM2 ) I run the Diag command.
Kindly follow the instructions shared by @maxpayne above.
Update the Active 1 driver manually, please use the Qualcomm diag driver, which is available for download via the attached mega link. He also included a video tutorial to help you through the process.
Thank you both.
Unfortunately it did not work.
I first tried to update manually the Diag driver without installing previously the Qualcomm USB driver, but it did not work.
Then I installed the Qualcomm USB driver and tried again to install manually the Diag driver: same issue.
See attached the message from Windows.
I tried to install the driver from folder C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers
I have an Intel processor.
Out of curiosity I tried to install from the other folders, but no luck
In the IMEI/baseband instruction manual, it says to flash the 4 partitions in fastboot: patched_vsmart, fsg, modemst1, modemst2. I hope that was also done.
You may need to use a different PC to run the diag command again.
I had initially flashed these 4 partitions before trying to enter Diag mode, then because I redid the full process of flashing the emergency package several times, I did not flash them before trying again to connect in Diag mode.
So, here is what happened (as I did the very first time)
-I flashed these 4 partitions
-Root disapeared, SU grayed in Magisk, when I type the command "su" it says: No daemon is currently running!
-I flashed again the Magisk_patched.img file, gained access again to root with the command :
fastboot flash boot magisk_patchedX2.img
So maybe the problem is here? This action is against the previous command: fastboot flash boot_a patched_vsmart.img?
Anyway, I tried to install the Diag driver after that, and still not possible
1. Flash the emergency Rom again.
2. Flash the additional 4 files in fastboot.
3. Install the Magisk Manager app.
4. Verify that root access is available.
5. Try running the diag command again.
consider using a different PC this time
08-10-2024, 11:20 AM
(07-10-2024, 03:08 PM)justshez(06-10-2024, 01:51 PM)VinceLxThe patched_vsmart.img is essentially the boot.img file patched with Magisk, so you don't need to root again. Here's what to do next:(05-10-2024, 06:40 PM)justshez(05-10-2024, 05:48 PM)VinceLx(04-10-2024, 09:02 PM)justshez Kindly follow the instructions shared by @maxpayne above.
Update the Active 1 driver manually, please use the Qualcomm diag driver, which is available for download via the attached mega link. He also included a video tutorial to help you through the process.
Thank you both.
Unfortunately it did not work.
I first tried to update manually the Diag driver without installing previously the Qualcomm USB driver, but it did not work.
Then I installed the Qualcomm USB driver and tried again to install manually the Diag driver: same issue.
See attached the message from Windows.
I tried to install the driver from folder C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers
I have an Intel processor.
Out of curiosity I tried to install from the other folders, but no luck
In the IMEI/baseband instruction manual, it says to flash the 4 partitions in fastboot: patched_vsmart, fsg, modemst1, modemst2. I hope that was also done.
You may need to use a different PC to run the diag command again.
I had initially flashed these 4 partitions before trying to enter Diag mode, then because I redid the full process of flashing the emergency package several times, I did not flash them before trying again to connect in Diag mode.
So, here is what happened (as I did the very first time)
-I flashed these 4 partitions
-Root disapeared, SU grayed in Magisk, when I type the command "su" it says: No daemon is currently running!
-I flashed again the Magisk_patched.img file, gained access again to root with the command :
fastboot flash boot magisk_patchedX2.img
So maybe the problem is here? This action is against the previous command: fastboot flash boot_a patched_vsmart.img?
Anyway, I tried to install the Diag driver after that, and still not possible
1. Flash the emergency Rom again.
2. Flash the additional 4 files in fastboot.
3. Install the Magisk Manager app.
4. Verify that root access is available.
5. Try running the diag command again.
consider using a different PC this time
I confirm that flashing these 4 files removed the SU.
I gained access to SU by transforming a boot image (boot_a.img that was in the Emergency package from the link) with Magisk, then flashing it, as per the instructions on how to root with Magisk. After that for sure I have SU. If I type su when I try to enter Diag mode, no error message is present.
After flashing these 4 files, SU access disapeared (greyed in Magisk), I got the mention " No daemon is currently running! " when I type su.
So I will try on another PC, but I don't have one now, it will take time.
Thank you for your support on this issue.
10-10-2024, 11:03 AM
(05-10-2024, 05:48 PM)VinceLx ..
Out of curiosity I tried to install from the other folders, but no luck
According to this error https://www.hovatek.com/forum/attachment.php?aid=11813
I suspect you didn't follow the instructions in the video. Probably you didn't click Browse my computer for driver software > Let me pick from a list of available drivers on my computer
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
11-10-2024, 06:30 PM
(10-10-2024, 11:03 AM)maxpayne(05-10-2024, 05:48 PM)VinceLx ..
Out of curiosity I tried to install from the other folders, but no luck
According to this error https://www.hovatek.com/forum/attachment.php?aid=11813
I suspect you didn't follow the instructions in the video. Probably you didn't click Browse my computer for driver software > Let me pick from a list of available drivers on my computer
You are right, I did not click on Let me pick...
So, now when I do that, I go to this place in the folders:
C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers
and I am proposed a lot of different models
But from all this list I don't see any reference to a Diag driver. When I read the procedure, I should have a Qualcomm HS-USB Android DIAG 901D
What to do next?
11-10-2024, 09:08 PM
(11-10-2024, 06:30 PM)VinceLxIs there anything relating to 901D on the list?(10-10-2024, 11:03 AM)maxpayne(05-10-2024, 05:48 PM)VinceLx ..
Out of curiosity I tried to install from the other folders, but no luck
According to this error https://www.hovatek.com/forum/attachment.php?aid=11813
I suspect you didn't follow the instructions in the video. Probably you didn't click Browse my computer for driver software > Let me pick from a list of available drivers on my computer
You are right, I did not click on Let me pick...
So, now when I do that, I go to this place in the folders:
C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers
and I am proposed a lot of different models
But from all this list I don't see any reference to a Diag driver. When I read the procedure, I should have a Qualcomm HS-USB Android DIAG 901D
What to do next?
12-10-2024, 08:50 AM
(11-10-2024, 09:08 PM)justshez(11-10-2024, 06:30 PM)VinceLxIs there anything relating to 901D on the list?(10-10-2024, 11:03 AM)maxpayne(05-10-2024, 05:48 PM)VinceLx ..
Out of curiosity I tried to install from the other folders, but no luck
According to this error https://www.hovatek.com/forum/attachment.php?aid=11813
I suspect you didn't follow the instructions in the video. Probably you didn't click Browse my computer for driver software > Let me pick from a list of available drivers on my computer
You are right, I did not click on Let me pick...
So, now when I do that, I go to this place in the folders:
C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers
and I am proposed a lot of different models
But from all this list I don't see any reference to a Diag driver. When I read the procedure, I should have a Qualcomm HS-USB Android DIAG 901D
What to do next?
No, no reference about 901D, or about Diag.
On the other hand I explored the other folders and I found exactly Qualcomm HS-USB Android DIAG 901D in the following folder:
C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers\qcser.inf_amd64_da2bdde674bc3d1e
Is it ok to use it, although there is a reference to amd64 in the name of the folder? My PC has an Intel one.
12-10-2024, 08:53 AM
(12-10-2024, 08:50 AM)VinceLx(11-10-2024, 09:08 PM)justshez(11-10-2024, 06:30 PM)VinceLxIs there anything relating to 901D on the list?(10-10-2024, 11:03 AM)maxpayne(05-10-2024, 05:48 PM)VinceLx ..
Out of curiosity I tried to install from the other folders, but no luck
According to this error https://www.hovatek.com/forum/attachment.php?aid=11813
I suspect you didn't follow the instructions in the video. Probably you didn't click Browse my computer for driver software > Let me pick from a list of available drivers on my computer
You are right, I did not click on Let me pick...
So, now when I do that, I go to this place in the folders:
C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers
and I am proposed a lot of different models
But from all this list I don't see any reference to a Diag driver. When I read the procedure, I should have a Qualcomm HS-USB Android DIAG 901D
What to do next?
No, no reference about 901D, or about Diag.
On the other hand I explored the other folders and I found exactly Qualcomm HS-USB Android DIAG 901D in the following folder:
C:\Users\Morbac\Desktop\Qualcomm+Diag+Drivers\Qualcomm Diag Drivers\qcser.inf_amd64_da2bdde674bc3d1e
Is it ok to use it, although there is a reference to amd64 in the name of the folder? My PC has an Intel one.
You can use it
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)