I watched some tutorials for Qualcomm phones on how to get them into diagnostic mode. In Device Manager you should get a Qualcomm device with a certain COM port.
I was never able to get a Huawei Y7 Prime 2017 into diagnostic mode. The phone is rooted and ADB has SU access. I tried:
- Rebooting into EDL mode with adb reboot edl : normal reboot
- sys.usb.config diag,adb: did nothing
- *#*#2846579#*#* and then manufacture mode: nothing
What I want is to get the diagnostic port, if/when I manage to put it into diagnostic mode. Any ideas would be very welcome!
Related
G'day,
Does anyone know how to revive a Lenovo Yoga Tab 3 Plus that no longer bootable?
Situation is this:
* Tablet crashed when bootloader was locked prior to having re-flashed OEM bootloader.
* Tablet no longer boots up / powers on via power button (no led).
* No longer have access to tablet via USB ADB or fastboot.
* Tablet is only accessible via Qualcomm HS-USB QDLoader 9008 diagnostic port.
* I have tried to flash stock ROM using QFIL, but keep getting Sahara failed downloading flash programmer.
* I have disabled Windows driver verification.
I think if I could unlock the bootloader via the Qualcomm USB port I would then be able to revive the tablet by re-flashing all the partitions.
Thanks in advance
Cheers J
you have to to the jtag
i used to had the same problem after i flashed the L firmware to the F one , but i send it back to the merchant and got new one .
jrf888 said:
G'day,
Does anyone know how to revive a Lenovo Yoga Tab 3 Plus that no longer bootable?
Situation is this:
* Tablet crashed when bootloader was locked prior to having re-flashed OEM bootloader.
* Tablet no longer boots up / powers on via power button (no led).
* No longer have access to tablet via USB ADB or fastboot.
* Tablet is only accessible via Qualcomm HS-USB QDLoader 9008 diagnostic port.
* I have tried to flash stock ROM using QFIL, but keep getting Sahara failed downloading flash programmer.
* I have disabled Windows driver verification.
I think if I could unlock the bootloader via the Qualcomm USB port I would then be able to revive the tablet by re-flashing all the partitions.
Thanks in advance
Cheers J
Click to expand...
Click to collapse
Hello friend. Did you try the Lenovo rescue and smart assistant.?
Model no: Lenovo TB3-850F MT:ZA17
MFG date: 2016-07-14
Serial no: HGAC0PMC(80)
I followed the guide to root my Lenovo Tab3 8
https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786
And after installing TWRP to the recovery partition the device is stuck in a boot loop with just the lenovo logo showing on boot and progressing no further. In addition the reset key combination doesnt work it only reboots the device and does not show any menu allowing for recovery boot or reset. So essentially there seems to be nothing to do which can allow a boot of the device.
When I connect the device via USB it is recognised by windows as MT65xx Android Phone but does not show up in adb devices or in ADB Driver Installer 2.0
I tried following the guide http://trendblog.net/fix-soft-bricked-android-device-first-aid-guide/ but it just tells me my phone is soft-bricked and to consult xda developer forums.
Can anyone help me? Thanks
xavier234 said:
Model no: Lenovo TB3-850F MT:ZA17
MFG date: 2016-07-14
Serial no: HGAC0PMC(80)
I followed the guide to root my Lenovo Tab3 8
https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786
And after installing TWRP to the recovery partition the device is stuck in a boot loop with just the lenovo logo showing on boot and progressing no further. In addition the reset key combination doesnt work it only reboots the device and does not show any menu allowing for recovery boot or reset. So essentially there seems to be nothing to do which can allow a boot of the device.
When I connect the device via USB it is recognised by windows as MT65xx Android Phone but does not show up in adb devices or in ADB Driver Installer 2.0
I tried following the guide http://trendblog.net/fix-soft-bricked-android-device-first-aid-guide/ but it just tells me my phone is soft-bricked and to consult xda developer forums.
Can anyone help me? Thanks
Click to expand...
Click to collapse
Solved by pressing volume down with SP tool.
I was trying to update my Axon 7 Mini with an update zip from here https://www.ztedevices.com/en/support/detail?id=03743F4E761C475F838D444384791D36
Extracted the update.zip from the download. put the update.zip in the root of my sd card. Applied through recovery using sd card update. The phone accepted the file. Said it was successful. I wiped the cache partition and selected reboot system. The phone never turned on again. No signs of life whatsoever. Plugged into my desktop PC. Windows detects it but doesn't recognize it. I need some MAJOR help please.
Can you enter the recovery again by pressing volume up and power simultaneously? If not, then you will probably need to enter emergency download "EDL" mode and flash firmware using EDL Tool. Do you have an european version of phone? On my Axon 7 Mini I just upgraded directly from Marshmallow to Nougat without any problems.
So, how to enter the EDL mode, please look here:
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
Maybe you will need the EDL cable or you can try this "DIY hack video". - I had also bricked phone and this video helped me a lot!
When the phone is in EDL mode then you will need the firmware and EDL Tool for flashing.
Good Luck!
Machi007 said:
Can you enter the recovery again by pressing volume up and power simultaneously? If not, then you will probably need to enter emergency download "EDL" mode and flash firmware using EDL Tool. Do you have an european version of phone? On my Axon 7 Mini I just upgraded directly from Marshmallow to Nougat without any problems.
So, how to enter the EDL mode, please look here:
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
Maybe you will need the EDL cable or you can try this "DIY hack video". - I had also bricked phone and this video helped me a lot!
When the phone is in EDL mode then you will need the firmware and EDL Tool for flashing.
Good Luck!
Click to expand...
Click to collapse
Windows doesn't recognize it in through the usb drivers in EDL mode so idk if it can go into that mode manually. Definitely not by command prompt.
Hi all.
I´m still searching some way to solve my problem.
What´s happaned:
was on AEX OREO, make downgrade to SLIM stock 7.1 from raystef66 = all ok. But after a couple days made magisk upgrade to 17 via twrp and after that is "death"...when I try to start my phone I can see first ZTE logo, than 3x red led, that´s all, I think after flash stockrom I lost customrecovery......?.....t I can not start to TWRP, FASTBOOD...maybe EDL working but:
When I try combo+pwr I see DFU/com4 port. So I tried guidef from raystef66 with ZTE DFU_MultiDL_A2017X_Tool = apk see my phone but still in disconect mode(conect stat) but WIN see my phone as HS USB QDlouder 9008 com 8, now I run edl tool from djkuz.
Tool see my phone, name QUALCOM HS=USB QDlouader 9008 and I tried flash edl or recovery with error = from log:
Did not receive Sahara hello packet from device miflash says can not recivie hallo pocaked.
Any new idea how to fix...?
Thx!!
trying on WIN7 pro
kraljan66 said:
Hi all.
I´m still searching some way to solve my problem.
What´s happaned:
was on AEX OREO, make downgrade to SLIM stock 7.1 from raystef66 = all ok. But after a couple days made magisk upgrade to 17 via twrp and after that is "death"...when I try to start my phone I can see first ZTE logo, than 3x red led, that´s all, I think after flash stockrom I lost customrecovery......?.....t I can not start to TWRP, FASTBOOD...maybe EDL working but:
When I try combo+pwr I see DFU/com4 port. So I tried guidef from raystef66 with ZTE DFU_MultiDL_A2017X_Tool = apk see my phone but still in disconect mode(conect stat) but WIN see my phone as HS USB QDlouder 9008 com 8, now I run edl tool from djkuz.
Tool see my phone, name QUALCOM HS=USB QDlouader 9008 and I tried flash edl or recovery with error = from log:
Did not receive Sahara hello packet from device miflash says can not recivie hallo pocaked.
Any new idea how to fix...?
Thx!!
trying on WIN7 pro
Click to expand...
Click to collapse
First: did the DFU see a com port in the config?
You do have to select the com port manually.
Second: can you boot to FTM?
Third: try another Edl package, some Edl have to be installed as a backup restore not via a straight flashing.
thx for quick answer!
1 see pic pls, in DFU com4
2 no can not get to FTM
3 tried 3x another packages...see log/pic from ZTE EDL tool...
kraljan66 said:
thx for quick answer!
1 see pic pls, in DFU com4
2 no can not get to FTM
3 tried 3x another packages...see log/pic from ZTE EDL tool...
Click to expand...
Click to collapse
Use the latest MiFlash. I've been having trouble with EDL Tool lately. Maybe it'll work. z
I'm guessing the red LED turns off as soon as you connect MultiDL correctly?
Make sure Edl tool is in the root directory of you PC or laptop drive.
EG: C:\ or D:\ as per the instructions.
Make sure you run it as admin too.
If I remember correctly the full Edl package had to be placed into the appropriate folder as per instruction (via the tool) and on the post.
@Syberclone:
I have all as you write...in root, edl package is correct/about edl package edl tool says "success = tried 4different edl package for my phone"/
I´m convinced about a port problem, log from edl tool is:
15:47:25: INFO: User wants to talk to port '\\.\COM8'
ERROR
15:47:25: {ERROR: OpenPort:5198 Failed to open com port '\\.\COM8'
I´ll try another miflash but dont believe ...:-/
just used another PC with WIN7 and now.....CHEEEEERS!!!!!!
Thx to all!
Hello,
Recently purchased a non functional SM-T720 and discovered it is stuck in the Qualcomm Emergency Download (EDL) mode.
Where can I locate the "firehose" files to use with the Qualcomm Product Support Tool (QPST)?
Thanks!