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?
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
Hello guys, I hard brick my nubia z9 mini (chineese version). The phone is not responding to anything (power button press at the same time that volume +, I can't disconnect the battery cause it is screwed inside and I don't have tools to unscrewed it). Pc recognize the phone as Qualcomm HS-USB QDLoader 9008 (COM4) so I think it still as a chance to recovery but I don't know how, I've already try a few stuff:
- QFIL : but it was a problem about Sahara that failed
- ZTEMT ToolStudio(Common) 4.4.58 : but in ComPorts the qualcomm thing is there but not when I go to eMMCDownload, nothing appear
- nubia recovery tool : but recovery work once and then it failed (the phone still not gave any sign of life)
I've installed drivers for qualcomm devices version 2.0.8.7
I'm a little noob in this field so I'm pretty sure you can help me because I don't understand everything in all those stuff, please help me !
Thank you already
Unbrick your Nubia Z9 mini using "Nubia Toolstudio V 4.6.90."
Step 1: Connect your phone with Your Computer PC in "Qualcomm HS-USB QDLoader 9008" mode by pressing volume -,+ and power buttons, press all three buttons Simultaneously for 15 sec. (Note: Driver need for PC for connection, I used Nubia emergency tool 1.0.6 for driver purpose, don't use it for recovery purpose.)
ttps://drive.google.com/open?id=0B8joXHOIogfeOUVJanpnN1I0UjQ (Download All software From this given link, In this link "https"---"h" is missing, add by ur self)
Step 2: Install "Nubia Tool Studio V.4.6.90" in Your PC.
Step 3 : Open Nubia Tool Studio, Select model "NX511J" and "Firehouse Download" in menu list, click referesh button, it will shows connected port.
Step 4: Extract the firmware that you have downloaded, and shows the file path of Firmware folder. (Use any one Firmware file "Z9(Mini)_NX511J_XVV" or "Z9(Mini)_NX511J_XVV2".)
Step 5: Click "Start" button, it will start download to your phone's emmc. After completing download 100%, your phone automatically restart to normal, and you will be happy:laugh:
Hello Everyone !!
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you
reserved
@vasu97
We already have a dedicated thread on the same topic.
what can i edit so it won't relock the bootloader? or does it relock it?
vasu97 said:
Hello Everyone !!
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you
Click to expand...
Click to collapse
Holy crap! I literally spent the last 12 hours trying to get my phone fixed. This was the only solution. Thank you so much!!!
If anyone had problems with the MSM tool "Sahara communication failed," unplug your phone. Turn it off by holding the power button for a while. Hold the power up for 10 seconds, then keep holding the volume up and plug your phone in to the PC. The MSM tool should automatically detect and restore your phone.
vasu97 said:
reserved
Click to expand...
Click to collapse
thank you so much
I've tried all the steps on multiple ports and different computers but I got always the errno 258 while loading the cache.img. Don't know what else to do...
My intention is to backup QCN of my Moto X4 (XT1900-1). Currently I installed Motorola latest USB drivers and installed Qualcomm HS-USB QDLoader.
Device is booted with BP mode and Windows (7) shows three other devices called "moto x4" with a device called "RmNet". I select the first device then right click -> update driver -> let me pick from the list -> Motorola "USB QC diag" and force install it.
However when I launch QPST (2.7.472) at the port's tab COM15 appears however at "phone" column it shows "?(0)". When I try to backup the QCN I'm only getting 4kb of data and QPST shows "memory error"
I tried QFIL also, it's backup/restore buttons are getting disabled when I choose that specific port.
I tried the same sequence in two other Windwos PCs (Win 10) same results.
Did anyone successfully backed up QCN before? can you share the details. Thanks