Cannot connect in Diag mode on Aquaris X2
Cannot connect in Diag mode on Aquaris X2
01-10-2024, 04:42 PM
Yes, this I can read
Nevertheless it is indeed a BQ Aquaris X2. Maybe it is because of the emergency package I flashed in EDL mode? I followed the full process though.
I tried with BQ Firmware flash tool 5.0, it does not work either.
So now I am stuck:
- I cannot flash the original firmware;
- I cannot enter Diag mode.
What do you suggest now?
02-10-2024, 02:51 PM
(01-10-2024, 04:42 PM)VinceLx Yes, this I can read
Nevertheless it is indeed a BQ Aquaris X2. Maybe it is because of the emergency package I flashed in EDL mode? I followed the full process though.
I tried with BQ Firmware flash tool 5.0, it does not work either.
So now I am stuck:
- I cannot flash the original firmware;
- I cannot enter Diag mode.
What do you suggest now?
Refer to https://www.needrom.com/download/bq-aqua...e-edlqfil/
everything you need to fix the baseband issue is there
02-10-2024, 06:06 PM
So, during this procedure, there is a need to enter in Diag mode. Which I cannot. See above.
This is why I asked for support here. How can I enter Diag mode? I followed all the steps of the procedure, everything went fine, until the Diag mode, which I am blocked now.
03-10-2024, 11:57 AM
(26-09-2024, 03:18 PM)VinceLx ..
When I run adb shell, then su: no changes
..
This is likely the problem. The phone needs to be rooted and give you su privilege in command prompt / terminal
Share a screenshot of command prompt / terminal after you enter:
Code:
adb devices
adb shell
suI expect you to get a prompt in Magisk manager if not check magisk manager and give adb shell root privilege
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.
03-10-2024, 12:13 PM
(25-09-2024, 08:43 PM)VinceLx Active 1
Assuming the diag commands runs successfully with root access and it still gets detected as this then you could manually update this using Qualcomm Diag driver like https://mega.nz/file/Z5IFDbTD#BF0qfxkPYa...5hjrORpR3E
and this technique
This post was last modified: 03-10-2024, 12:15 PM by maxpayne.
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.
04-10-2024, 08:11 PM
(03-10-2024, 11:57 AM)maxpayne(26-09-2024, 03:18 PM)VinceLx ..
When I run adb shell, then su: no changes
..
This is likely the problem. The phone needs to be rooted and give you su privilege in command prompt / terminal
Share a screenshot of command prompt / terminal after you enter:
Code:adb devices adb shell su
I expect you to get a prompt in Magisk manager if not check magisk manager and give adb shell root privilege
04-10-2024, 08:15 PM
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.
This post was last modified: 04-10-2024, 08:16 PM by VinceLx.
Attached Files
04-10-2024, 08:27 PM
(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.
04-10-2024, 08:52 PM
(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
04-10-2024, 09:02 PM
(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.
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)