Database Users

Bricked Oneplus 2 not getting detected on pc

Can anyone tell me a way so that the pc detects my bricked OPT? I have tried all combinations but its not getting detected at all

phorcus said:
Can anyone tell me a way so that the pc detects my bricked OPT? I have tried all combinations but its not getting detected at all
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Rebel7022 said:
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
finally it got detected but when i run MSM8994DownloadTool.exe as administrator and click on start nothing happens

https://1.bp.blogspot.com/-ZZ-sHUBv...ExaIdiLCYRNQCLcB/s1600/Screenshot+%284%29.png
this is where i am stuck please help guys i am in a fix :'(

Are you sure you disabled driver signature enforcing in Windows? You can't install the qualcomm 9008 serial interface driver without doing this, as this driver is not signed by Microsoft.

pitrus- said:
Are you sure you disabled driver signature enforcing in Windows? You can't install the qualcomm 9008 serial interface driver without doing this, as this driver is not signed by Microsoft.
Click to expand...
Click to collapse
yes i did still it doesn't work, any help would be appreciated

If you power up your phone using volume up in fastboot/bootloader mode and then run fastboot devices, does it list your phone? Just making sure the cable connection works.
If yes, then power down your phone by holding power button until screen goes black (making sure you disconnected usb cable first). Then hold volume up while connecting usb cable (don't touch power button), you should hear Windows detecting a new device, check device manager to see that the qualcomm 9008 usb serial port has been successfully installed and with no warning exclamation mark on it. If all is good, you should now be able the launch the download tool and push the download button to start downloading the file partitions to the phone.

pitrus- said:
If you power up your phone using volume up in fastboot/bootloader mode and then run fastboot devices, does it list your phone? Just making sure the cable connection works.
If yes, then power down your phone by holding power button until screen goes black (making sure you disconnected usb cable first). Then hold volume up while connecting usb cable (don't touch power button), you should hear Windows detecting a new device, check device manager to see that the qualcomm 9008 usb serial port has been successfully installed and with no warning exclamation mark on it. If all is good, you should now be able the launch the download tool and push the download button to start downloading the file partitions to the phone.
Click to expand...
Click to collapse
Thanks a lot for writing out to me, but the thing is that my phone is already dead and i had given up all the hope that i had but luckily it got detected and i cannot boot into fastboot mode or bootloader mode the screen is already black, do you think i still have hope? the phone has been detected as qualcomm 9008 in ports in device manager

phorcus said:
Thanks a lot for writing out to me, but the thing is that my phone is already dead and i had given up all the hope that i had but luckily it got detected and i cannot boot into fastboot mode or bootloader mode the screen is already black, do you think i still have hope? the phone has been detected as qualcomm 9008 in ports in device manager
Click to expand...
Click to collapse
Could it be that the actual screen is dead on your phone? But still, since the PC detects the debug port, it should start restoring the phones partitions when you start downloader tool and press the download button up to the left.

Bricked phone but can still get into EDL mode

Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.

daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.

Choose an username... said:
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Click to expand...
Click to collapse
I'm on win10 64bit

daevion0 said:
I'm on win10 64bit
Click to expand...
Click to collapse
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason

Choose an username... said:
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Click to expand...
Click to collapse
Is there no other option? is there no other way to at least get fast boot mode back on my phone?

daevion0 said:
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
Click to expand...
Click to collapse
Lol nope, not if EDL is not working for you. You still didn't tell me whether you have a DFU brick or not. If you do have a DFU brick the only surefire way is to disassemble your phone and short a testpad, so don't complain.
Try what I told you above. It may be that it's set at 9600 baud

daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
1. You must use "Qualcomm HS-USB QDLoader 9008" driver (there is another one call zidag but it's not work here)
2. As soos as you enter EDL mode, you must press "Flash" as quick as possible

i'm in a similar situation... i did "fastboot oem lock" and now i'm in a loop trying to boot the phone, after the 3time it enters edl (i see the red light).
My model is de G model (2017G) can i use miFlash just to restore the recovery and fastboot?
i had installed lineageOS, when connecting my phone it says that is the U model (2017U) but i think is only a label tag from the rom...
Thansks for the help!!

A 64 bit computer is not really necessary, however it is adviced.
I used a 32bit laptop running Win 10 to rescue mine.
Drivers seem to be a major problem, having the correct up to date drivers is a must.
Also try using Edl Tool and the Axon7 tool kit to access flashing.
Zadig drivers can help in some instances.
With the error you are receiving, have you tried another Edl package?
I was using an Edl package that would not finish flashing either, try a different package and make sure its correct for your phone.
I hope you get it sorted

The hello read package does occur when the phone is not really EDL mode anymore. You always have to restart the phone and boot manually into EDL mode with + - Power and you have to reboot everytime you did or if the hello error happens.
Look under device manager if it says Qualcomm instead of ZTE Device Handset. If that is the case you can build your own EDL cable.
"First I opened the cable and cut the Black and green open, then I connected all the black and green one together and pressed the power button until the red led was gone and 2 additional seconds.
After that I disconnected the modded cable and connected the Phone to the PC with the orginal cable and it showed up as Qualcomm HS-USB QDLoader 9008. "
You can install the qualcomm drivers under the MiFlash tab in the latest version.

i finally solve my issue following the guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 there is also a resume on https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152

Enabling Diagnostic Mode

I wanna enable the diagnostic mode and try to see if i can add more LTE bands through QPST. I tried the generic command through adb shell and its not working Any suggestions are welcome.

Go to Emergency Mode
Type- *#3424#
This will enable diag mode.

Try thr Hardware test Mode
There is a way to enable the harware test mode on Asus zenfome Max pro M!.
youtu.be??toXVB0e9Afo
remove ?? with /
IT should have an option to test the LTE band

ankitpatil2109 said:
Go to Emergency Mode
Type- *#3424#
This will enable diag mode.
Click to expand...
Click to collapse
Thanks but this did nothing for me. The phone has no SIM and the phone says emergency calls only. In the dialer though this code had no effect. the dialer just displayed it and sat there.
What am I missing? Thanks
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
InverselyCrazy said:
There is a way to enable the harware test mode on Asus zenfome Max pro M!.
youtu.be??toXVB0e9Afo
remove ?? with /
IT should have an option to test the LTE band
Click to expand...
Click to collapse
Thanks for this. I looked at all the tests - which are cool. But I did not find any way to enter diag mode so I can try to use Qualcomm tools to unlock some more LTE bands. Am I missing something? Thanks

Iirc, a powered down (switched off) phone can be connected to PC with volume + and volume - buttons pressed simultaneously when connecting via USB to PC. Then PC device manager shows android device connected in diag mode (needs latest qualcomm drivers 2b installed in PC). I am not so sure whether windows need to be in test mode for this or not.

Cookie Ninja said:
Iirc, a powered down (switched off) phone can be connected to PC with volume + and volume - buttons pressed simultaneously when connecting via USB to PC. Then PC device manager shows android device connected in diag mode (needs latest qualcomm drivers 2b installed in PC). I am not so sure whether windows need to be in test mode for this or not.
Click to expand...
Click to collapse
Thanks for this. I tried using both vol+ and vol- with power button. I get a completely black screen. But I do see some 9008 drivers get loaded in Device Manager. When I open QPST a com port is automatically found and it says that the device is in download mode. I cannot really do anything at this point. I want to start service programming so I can edit the NV using QXDM so I can add an LTE band. But this attempt fails due to download mode. I don't know if this is akin to the download mode I have seen in my Samsung phones when I use ODIN to flash firmware. The only way I have found out of the black screen is to press vol+ and power which eventually takes me to fastboot mode on the device and from here I can press/hold power to reboot to the Android system.
I am not sure I have the latest drivers. Now that I have the device rooted, I was able to issue "setprop sys.usb.config diag,adb" and actually see my Windows 10 computer show a diagnostics 9091 com12 port and a modem 9091 on com11. The driver info shown for this in Device Manager is 2.1.1.2 dated 3/19/2014. With this I can actually use QPST to read something from the device. But when I try to use QXDM to read item 06828 (LTE bands) I get "NV Status Error Received: Item Inactive". No idea what that means or what is wrong. Working on my old Samsung Note3 was pretty simple compared to this.

with root
enable diag port :
adb devices
adb shell
su
setprop sys.usb.config rndis,diag,adb

anvesh583 said:
I wanna enable the diagnostic mode and try to see if i can add more LTE bands through QPST. I tried the generic command through adb shell and its not working Any suggestions are welcome.
Click to expand...
Click to collapse
Hey Bro Don;t Dont Worry I also have zenfone max pro m2 and i dont have root even Try This
1.Open CMD.
2.Connect Your DEVICE with USB DEBUGGING.
3.Type "adb devices".
4.In the phone pops up press "ALLOW".
5.Type"adb shell".
6.Type"setprop sys.usb.config ,diag,adb
7.Voila!! Connected
8.Please Check "DEVICE MANAGER"
9.Now Please "QFIL to SELECT YOUR DIAG PORT".

kamo84 said:
setprop sys.usb.config rndis,diag,adb
Click to expand...
Click to collapse
Ajay_Boss said:
Hey Bro Don;t Dont Worry I also have zenfone max pro m2 and i dont have root even Try This
1.Open CMD.
2.Connect Your DEVICE with USB DEBUGGING.
3.Type "adb devices".
4.In the phone pops up press "ALLOW".
5.Type"adb shell".
6.Type"setprop sys.usb.config ,diag,adb
7.Voila!! Connected
8.Please Check "DEVICE MANAGER"
9.Now Please "QFIL to SELECT YOUR DIAG PORT".
Click to expand...
Click to collapse
Guys, Any idea how to make these commands work on Android 11 ?
Both the codes do not trigger anything and does not show any new devices in device manager.

Axon 7 EDL Mode Not Working/ can't boot to EDL

My Axon 7 is the A2017U, i had the B32 Nougat running on it and wanted to try the new lineageos 15.1, but had to unlock my bootloader first i used the toolkit like I've done in the past and was able to unlock it and flash twrp, when i try to boot it back on it goes to factory testing mode, i was able to get into twrp and i wiped everything and it stopped the problem of booting directly to FTM but after that i tried to go into EDL mode and it seemed to try to enter the mode but the red led indicator light stays on rather than doing a quick blink. its no longer picked up as a COM port, when i enter fastboot mode adb doesn't seem to work and I'm unsure what to do or if I'm out of luck. Thank you for your time and the advice and help you guys are able to provide.

use ADB
Enable ADB in developer options
use command "adb reboot edl"

Used Twrp to flash Custom ROM, EDL still not fixed
sauerkraut17 said:
use ADB
Enable ADB in developer options
use command "adb reboot edl"
Click to expand...
Click to collapse
I had no OS installed, only twrp recovery and I was able to unlock my boot loader. I tried to flash Lineage-OS ROM in twrp and didn't have much luck because i would get an error code saying it wasn't compatible with my phone and had to go into the ROM files and edit the updater-script file to remove the compatibility check.
In the end I have a working phone with a custom ROM but EDL mode is still not responsive and seems to freeze my phone as soon as I press the 3 buttons to get into EDL. the notification light blink remains on so ill take it as an indicator that something is wrong with the firmware that it uses. i still want to fix it so EDL can be used but unsure how to fix it. I did some researching and was wondering if using a deep flash Engineering cable would work to fix the EDL mode and any other problems that could be there.

levittc5280 said:
I had no OS installed, only twrp recovery and I was able to unlock my boot loader. I tried to flash Lineage-OS ROM in twrp and didn't have much luck because i would get an error code saying it wasn't compatible with my phone and had to go into the ROM files and edit the updater-script file to remove the compatibility check.
In the end I have a working phone with a custom ROM but EDL mode is still not responsive and seems to freeze my phone as soon as I press the 3 buttons to get into EDL. the notification light blink remains on so ill take it as an indicator that something is wrong with the firmware that it uses. i still want to fix it so EDL can be used but unsure how to fix it. I did some researching and was wondering if using a deep flash Engineering cable would work to fix the EDL mode and any other problems that could be there.
Click to expand...
Click to collapse
EDL using the volume/power button has issues with the newer bootstack (which it sounds like you're on). However, since you have an OS now do as I recommended. It will 'reset' the EDL and once done via ADB command it will work with the volume/power buttons like it did before moving forward.

sauerkraut17 said:
EDL using the volume/power button has issues with the newer bootstack (which it sounds like you're on). However, since you have an OS now do as I recommended. It will 'reset' the EDL and once done via ADB command it will work with the volume/power buttons like it did before moving forward.
Click to expand...
Click to collapse
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?

levittc5280 said:
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
Click to expand...
Click to collapse
Have the same issue as you do after installing the bootstack. but even with the adb reboot edl command my phone just restarts normally.. But my OS is working fine, is there any way?

Try to use volume up and volume down only and plugging in USB cable........

stinka318 said:
Try to use volume up and volume down only and plugging in USB cable........
Click to expand...
Click to collapse
Tried everything already. Can only get to DFU mode..

So, I have a similar problem: after flashing a new version of TWRP, now Recovery doesn't start. The problem is that I haven't any OS installed and the last chance to save the phone should be reflash stock by EDL... BUT EDL mode doesn't start if I press vol UP + vol DOWN during power on... (it became black with a red light, but if I digit "ADB devices" on ADB, no devices seems connected, and in the same way it's impossible to use Axon7Toolkit). So: no Recovery, no EDL mode, no OS installed, my phone is a paperweight.
Is there a method to save my Axon 7?

Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps

levittc5280 said:
My Axon 7 is the A2017U, i had the B32 Nougat running on it and wanted to try the new lineageos 15.1, but had to unlock my bootloader first i used the toolkit like I've done in the past and was able to unlock it and flash twrp, when i try to boot it back on it goes to factory testing mode, i was able to get into twrp and i wiped everything and it stopped the problem of booting directly to FTM but after that i tried to go into EDL mode and it seemed to try to enter the mode but the red led indicator light stays on rather than doing a quick blink. its no longer picked up as a COM port, when i enter fastboot mode adb doesn't seem to work and I'm unsure what to do or if I'm out of luck. Thank you for your time and the advice and help you guys are able to provide.
Click to expand...
Click to collapse
I had the same problem a few days ago. When I booted to EDL Mode the red led was instantly on but the PC recognized it somthing like ZTE Handset Device Mode.
1. You can download TWRP Treble by NFound and flash it via your TWRP. Then reboot to recovery again and under the reboot tab its possible to boot to EDL/9008 Mode.
2. You build a EDL Cable to get the device from the red light to EDL mode. Just open some usb cable and connect the green and black (all four) together, plug it in the device and press the power button
until the red light is gone and hold on two additional seconds. Then remove the cable and plug another working cable in and the PC recognize it as Qualcomm in EDL mode.
This is literally how I unbricked my device.

Syberclone said:
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
Click to expand...
Click to collapse
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.

Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Click to expand...
Click to collapse
Did you resolve problem?

spasacamen said:
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Click to expand...
Click to collapse
No need to order that cable... If you still can cancel it i'd tell you to do that. You made a mistake by changing the drivers, you had the "ZTE Handset Diagnostic Interface (DFU)" driver, and replaced it with the EDL driver.
This of course does not work because your phone is in DFU MODE instead of EDL. What you have to do is uninstall the device via device manager and also tick "Uninstall driver software for this device", then turn the phone off and enter DFU again, and then use MultiDL from this forum to enter EDL. After that, use MiFlash or EDL Tool, and try flashing a FULL EDL file
By the way ADB will only work on FTM mode or the recovery or on a working system. You won't get ADB on edl mode or dfu mode because they simply don't have adb working, it's normal

i never use xda but this quote thing is what i have aswell
levittc5280 said:
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
Click to expand...
Click to collapse
all i see is the red light in edl, whatever i try it Always just goes to a red light and a black screen. this happened after trying to unlock the bootloader. i was in android 8 and tried to lock it, it messed it up as my Phone could not boot anymore, i flashed the stock android 6.0 or something that came with the axon 7 toolkit and it did work but when trying to unlock the bootloader as the device state suddenly was locked it broke the whole thing and i oped edl could save me but even that is broken just like what the person in the quote has

Well the only fix to get EDL mode is through test point, there's a thread of unbricking Axon 7 using test point, find it, you'll need to open your back cover to do this
This in case nothing works to get into EDL mode.

Brick Saved!! OnePlus 8 Pro Oxygen OS 12 to Android 11 downgrade brick saved. Methods I used and pitfalls.

Background:​
OnePlus 8 Pro IN2020
Original OS version is OxygenOS 12 Android 12
How my phone turned into brick:​
Try flashboot unsupported TWRP and other third party recoveries.
After a few tries, eventually causing my phone turning into a brick
What my error looks like:​
Not able to boot into system
Showing "the current image(boot/recovery) have been destroyed"
Can access fastboot and detect by system
​Method:​
Follow the steps in How to UNBRICK OnePlus 8 or 8 Pro! by Max Lee (Thank you my man, Max, for this video)
​Pitfalls in 2022 (IMPORTANT before UNBRICK!):​A USB 2.0 and Third-party USB cable are highly recommended​I was unable to boot into Quadcomm EDL mode while using the stock cable and USB 3.0 connector. Pressing the correct Volumn Up & Volumn Down and Power Button will boot the phone to fastboot in no time.
I successfully got into the EDL mode and finished flashing the phone using my iPad Pro Type-C charging cable which is an USB 2.0 one.
Use a newer version of the Qualcomm driver if you find the device not correctly detected​Use Qualcomm HS-USB QDLoader 9008 driver.
A new Quadcomm driver will help you flash your device correctly the first time!!!
Windows 11 won't let you install unsigned driver by default, but there's a way round​
Press Shift key while click Reboot in start menu to enter Advanced Options
Click Trouble shoot in Advanced Options
Click Advanced options, click Startup Settings then click Restart
After restart press 7 when required
If your computer won't restart, just unplug your phone temporarily
after this your device will detect by your computer correctly.
Pressing buttons requires special timing and preconditions and a few more tries​
To fully power off your phone, press Volume up and Power button for 10 seconds. Release immediately after the screen turns black.
Your phone is in the state of powered off even your screen displaying error message or charging animation, just make sure it's not in fastboot, recovery or booting animations.
Connect your phone to your computer before press Volume up and down and Power Button all at the same time to enter EDL mode.
Prepare yourself with Device Manager and MSM tool open and configured correctly before your phone enter EDL mode. There's a about 10 second window for you to start flashing.
Fail amid your MSM flash process:​Don't panic if you see error message saying you didn't finish flashing​
You can flash it anytime just make sure checking all the things above and enter EDL mode
Check these things：​
Check your Windows can install the unsigned driver correctly
Check Device Manger in Control Panel if your device is correctly detected as a COM device as Qualcomm HS-USB QDLoader 9008 or something like this
Use administrator privilege to open the MSM software
Check your cable connection is stable or not.
Finally, thanks Dr.E (Max Lee) for your help. Without your video instructions, I won't revive my phone. It spares my pain to ask my dad for money for a new phone I don't actually need.
Hope everyone could find some helpful information in this post and flash your phone like a champ.

A even better way to enter EDL mode is power off and unplug your device, and after hold volume up and down at the same time, plug in the USB 2.0 cable to the computer. It works every time!!

i cant join rdl mode always restarting fastboot mode