Develop Bugs

Mi Max Bricked after installing CM13 Rom

My MI Max (3gb/64gb 2016) completely bricked out after installing a CM13 rom, it was rooted and had TRWP installed (and working). Screen is black, no Led's.
I've tried connecting it to my Windows 10 (64 Bits) PC, turned Driver Signature off. It recognizes something when I connect my MI Max but cannot load the correct USB (Serial) drivers so I cannot use MIFlash to restore the firmware. Who can tell me what drivers I need to install (tried a lot of Qualcomm drivers but non are recognized by windows and therefor not working for MI Flash (Beta)). It is driving me crazy.
The device manager states Unknown USB Device (Device Descriptor Request Failed)
PLEASE HELP

hey buddy just follow this guide exactly and you'll be up and running like nothing happened before.heres the link http://en.miui.com/thread-3282-1-1.html. if the device doesn't get into edl mode with the mentioned button combo (as it happened to me).press the volume up+vol down + power (all 3 buttons simultaneously) and let go once u feel a vibration.once u get into edl mode the screen will be blank,no button or notification lights,just will show up in ur PC device manager after u install the drivers.I personally used this guide and the linked files to upgrade my mi max hydrogen (3gb ram/32gb) from global stable to global developer on win 10 64bit

Any luck?
[deleted]

i wonder why people post questions and disappear.

maybe he solved his problem...

Hello, I have also managed to brick my Mi Max while trying to flash RR ROM with TWRP.
My phone is completely dead, when trying to get into EDL mode the phone doesn't respond as mentioned in this thread.
The PC therefore doesn't recognized phone as HSUSB_BULK only as "unknown..." how to proceed ?

zuk z2 plus China ROM but won't recognize the port 9008

Help! I want to flash my zuk z2 plus China ROM but won't recognize the port 9008.
Been following all the possible solutions here for almost a month even on YouTube but always failed.
Thanks in advance.

shadfreak said:
Help! I want to flash my zuk z2 plus China ROM but won't recognize the port 9008.
Been following all the possible solutions here for almost a month even on YouTube but always failed.
Thanks in advance.
Click to expand...
Click to collapse
Try this by following carefully. It worked for me. Hope it works for you too...
https://youtu.be/DexLELi04XY

No luck men. Still doesn't recognize the port 9008.
Here's the things I've done so far.
1. Install Zuk latest driver
2. QFIL /Miflash (reconfigure settings based on comment on links)
3. Qualcomm driver
4. Zuk latest ROM (followed all the procedures from the link (xda and zukfans).
5. Use different cables
5. Insert to different port (update driver port)
6. Use different PC's (Windows 7, 8.1 and 10. Restart, ON and OFF after every attempt.
7. On developer mode
8. Use cp fastboot mode
9. ADL devices detected / ADL reboot. OKAY!
10. AND the final step (QFIL download or Miflash refresh) still no port 9008 at all.
11. Tried the Youtube cable jumper with foil(?) still no port 9008.

Question black screen poco f3

Hello, I broke my poco f3. I uploaded the port from pixel 5 and updated the phone. The phone does not light up anymore. The computer detects it as: qualcomm hs-usb qdloader 9008. I tried to bypass flash login somehow, but it failed. Can this phone be saved?

Bricked, black Screen, Qualcomm HS-USB QDLoader 9008
Hello, I Have me News Mi Mix 2 Bricked by Flash, in me PC is the Phone: Qualcomm HS-USB QDLoader 9008 Can i Flash the Firmware from China Rom without Bootloader/Recovery (Only Black Screen on Mobile Phone)
forum.xda-developers.com
U can try this

can someone explain what to do in 4 points I don't understand exactly what needs to be done there

Search for someone who has an xiaomi authorised account to flash EDL mode.is the only way to fix.You need to pay for that.

I've heard it too. There is no other way out. Thanks for the help

What rom did you flashed that bricked your phone? HentaiOS?

unfortunately, but I don't remember. I know it was the pixel 5 port of adndroid 12 beta 4/5. I also read about a way to recharge the phone by blocking the power button, it may help, but it will discharge from Wednesday: D

Hi . did you found a solution ??

Question [SOLVED] Bricked OP9Pro, can't get to fastboot, sahara communication failed

Seems like I succesfully bricked my OP9Pro. Tried to restore in MSMDownloadTool v4.0. Oneplus 9 Pro LE2123.
Phone is detected correctly in Windows device manager(QDLoader 9008, I get to EDL by holding Vol+ and Vol- buttons and connecting the cable). When I try to flash, MSM breaks on Sahara communication failed(FH: 258).
Qualcomm drivers are from Windows Update Center(I connect my phone in EDL mode, click Update and in optional updates section there is the needed driver - Qualcomm Incorporated - Ports).
What should I do?
I saw a python EDL workaround script, but I'm not sure if helps me or if it even works (saw it somewhere on xda, the only thing I remember that it was in some of oneplus's devices thread and the sript name was edl.py, sorry
Tried on one laptop(Acer Nitro< none of the ports gave a succesful result). Gonna try on my second(Asus ROG GL702VMK, it seems to have better ports connection). Gonna write an update message.
I can't get to fastboot, recovery, etc. Phone seems to give no signs of life, there is even no charging notification when the cable is connected(but maybe phone isn't turned off actually, not sure)

You need to click the box to "use lite firehose" beforehand running your msm. And change target to OS or EU depending on which one ur using

Shooter7889 said:
You need to click the box to "use lite firehose" beforehand running your msm. And change target to OS or EU depending on which one ur using
Click to expand...
Click to collapse
Thanks for advice, I got further but now it stopped on Param Preload with "Device not match image"
I use MSMDownloadtool for EU and my phone is EU version(LE2123)

So, I am kinda happy cuz I booted to system.
I used this guide(https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/). Used MSM Download tool with Indian f/w.
Then I tried to return to EU version, but I got the same param preload error. I used this version of MSM and it flashed successfully.
So now I guess the issue is solved. Thanks @Shooter7889 for ur advice with lite firehose

Uncheck "check sha256" for mismatch device issue. Or find correct msm. You're welcome. I had same issue after bricking my 9pro and not being able to run msm successfully.

[QUESTION] Device auto exits EDL Mode after 5 seconds [Solved]

UPDATE: The issue stands solved [see post 5].
........................................................................................................................................................................
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode as Qualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.

My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me

ohwarumbloss said:
My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me
Click to expand...
Click to collapse
I face the same issue on my OnePlus 9 and this help me. Thank you so much.

binary**# said:
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode asQualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.
Click to expand...
Click to collapse
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.

raoakashyadav said:
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.
Click to expand...
Click to collapse
Sorry for the delay in reply. Yup, I fixed this issue via the Disable Driver Signature Verification tweak as shown in this video. In short -->
Install Qualcomm USB Driver and download MSM Tool.
Boot your device to EDL Mode and connect it to your PC.
Then DO NOT disable Driver Signature Verification on your PC.
So as of now, your device will be listed as Qualcomm HS USB QDLoader under Device Manager but will have a yellow exclamation mark [because Drive Signature is enabled]. But at the same time, Windows will hold your device in this ELD Mode and wouldn't let it boot to the OS [which is what we wanted].
So while having your device connected to your PC in EDL Mode, now disable Driver Signature Verification. With this, your device should now stay in EDL Mode and will be listed without any yellow warning sign under Device Manager. You could now proceed ahead with the flashing via MSM Tool without any issues.