Related
Dear Friends today I flashed my redmi note 3 using EDL flash and it went success but after that my device is not turning on and its always on EDL mode only. please help me.
Try to press power button at least 30 to 40 sec...or till u see mi logo
It's hard bricked I think
Sent from my LS-5010 using XDA-Developers mobile app
How can hard brick happen with miflash edl?
bhanuchowdary said:
Dear Friends today I flashed my redmi note 3 using EDL flash and it went success but after that my device is not turning on and its always on EDL mode only. please help me.
Click to expand...
Click to collapse
Connect to pc with usb cable and wait until battery fully discharged. And recharge it for 3 hours. and press power buton for 20-25 second it will open.
What does the windows device manager say when your phone is connected to the pc? If it has something like "900E" mode you need this http://forum.xda-developers.com/redmi-note-3/how-to/unbrick-rn3-hs-usb-900e-edl-cable-100-t3447928 . This helped me out as my phone was dead. It only works when your battery is not completely discharged.
If you have "9008" mode in device manager, you are really in the EDL mode. So it is no problem to flash an appropriate fastboot rom with mi flash tool. Maybe you need the latest beta from mi flash tool though.
---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------
redminote3 said:
How can hard brick happen with miflash edl?
Click to expand...
Click to collapse
happend to me after i tried to unlock my bootloader. I put a modified bootloader to the rom that i wanted to flash. After that my phone was dead, had only HS USB 900E in device manager
Yeah i know that can happen on locked BL, but I thought on unlocked
So i made this DIY Deep Flash Cable using the copper wire method . First it connects. Once it connected as 8000 now its 900E .
When i install drivers it basically gives me error 10 Device Cannot Start.
BTW i have the blinking red light of death.
Any help?
Name your phone??!!
---------- Post added at 12:33 PM ---------- Previous post was at 12:24 PM ----------
Its not blinking red light of death. Its edl mode.
Just download the latest fastboot rom of latest miui version of you are using redmi note 3 from any site and make sure it is of .tgz extension and extract the file.
Disable device signature enforcement in your computer and connect the phone with your computer.
Open device manager on your computer and under ports section check if your phone is getting detected as 900E or something like that.
Download and install mi flash app from any site.
Now run the mi flash application and now connect your phone to the computer. After 10 seconds press the refresh button. Your phone would be seen as written 'comp' or 'com' on the mi flash app. Now from there browse to the folder where you extracted the fastboot rom and in the extracted files there would be a folder named image, just select that folder and press ok. Now click on flash.
Voila!! Your phone is now back.
Varun Sharda said:
Name your phone??!!
---------- Post added at 12:33 PM ---------- Previous post was at 12:24 PM ----------
Its not blinking red light of death. Its edl mode.
Just download the latest fastboot rom of latest miui version of you are using redmi note 3 from any site and make sure it is of .tgz extension and extract the file.
Disable device signature enforcement in your computer and connect the phone with your computer.
Open device manager on your computer and under ports section check if your phone is getting detected as 900E or something like that.
Download and install mi flash app from any site.
Now run the mi flash application and now connect your phone to the computer. After 10 seconds press the refresh button. Your phone would be seen as written 'comp' or 'com' on the mi flash app. Now from there browse to the folder where you extracted the fastboot rom and in the extracted files there would be a folder named image, just select that folder and press ok. Now click on flash.
Voila!! Your phone is now back.
Click to expand...
Click to collapse
Il try will update!
Nope , should i try testpoint?
your phone is redmi note 3 right? then try to reboot your phone in fastboot mode by holding volume down + power key untill it gives you the image of the mi bunny screwing with android bot. if this mode is opening then ur phone can be revive again dead sure. but if its blinking you have to make sure its in edl mode. just download adb driver from google search for your phone install it install your phones driver and connect it to the pc. if there is a device showing qloader 9008 something in device manager then your phone is alive and you can recover it by flashing the latest miui rom either global or developer via mi flash tool. your phone will be as good as new. just check it and msg if your phone is showing such indication i will help you to revive it.
No fastboot mode , no recovery , no MI logo
Does my flash detect ur device?
@Wardoge You can use deep flash method. You need special usb cable.
deep flash https://www.youtube.com/watch?v=uXai6PMmM7s
how to make deep flash cable https://www.youtube.com/watch?v=hmdrj4uX7gY
Wardoge said:
So i made this DIY Deep Flash Cable using the copper wire method . First it connects. Once it connected as 8000 now its 900E .
When i install drivers it basically gives me error 10 Device Cannot Start.
BTW i have the blinking red light of death.
Any help?
Click to expand...
Click to collapse
If you have the blinking led of death then you can maybe just flash the ROM ?. Try it.
kounir said:
@Wardoge You can use deep flash method. You need special usb cable.
deep flash https://www.youtube.com/watch?v=uXai6PMmM7s
how to make deep flash cable https://www.youtube.com/watch?v=hmdrj4uX7gY
Click to expand...
Click to collapse
I will but later
Adarsh2000 said:
If you have the blinking led of death then you can maybe just flash the ROM ?. Try it.
Click to expand...
Click to collapse
I am not an edl mode also i don't have fastboot , nor recovery
I accidentally flashed Redmi note 3 firmware into Redmi note 4. Now only red light is blinking. No fastboot also. Computer showing in ports Qualcomm hs usb qdloader 9008 (com3). Please help me flash full fastboot rom
if your computer detects your device as qdloader , that means it is in EDL mode, in this mode , you should be able to flash fastboot roms using miflash , you should read this thread first, http://en.miui.com/thread-565784-1-1.html . although the thread writes about flashing in fastboot mode, but it shouldn't differ alot from flashing in EDL mode, just follow the B part of the guide in the link, MIFlash should be able to detect your device and list it down as COM(number) .
As for the driver part, you shouldn't need to update anything if MIFlash can detect your device , as your computer already correctly detects it as QDLoader
chun_9876 said:
if your computer detects your device as qdloader , that means it is in EDL mode, in this mode , you should be able to flash fastboot roms using miflash , you should read this thread first, http://en.miui.com/thread-565784-1-1.html . although the thread writes about flashing in fastboot mode, but it shouldn't differ alot from flashing in EDL mode, just follow the B part of the guide in the link, MIFlash should be able to detect your device and list it down as COM(number) .
As for the driver part, you shouldn't need to update anything if MIFlash can detect your device , as your computer already correctly detects it as QDLoader
Click to expand...
Click to collapse
Thankyou for your valuable reply. Miflash detecting device. But error in flash. Then removed back cover and removed battery connection also. Then Miflash flashed the rom successfully
Does somebody have any information or encounter about this? The device is a Blu Energy X Plus 2, a back up phone I wanted to experiment with.
-After unlocking bootloader using ADB, phone got stuck at boot logo.
-I forgot to wipe.
-Device is not yet rooted
-After waiting for minutes I have forced the phone to shut down.
-Volume+Power combo, battery is non removable
-Now it wont turn on and respond to any button.
-It charges, as proven by the red light.
-It is somehow detected by the PC using the VCOM drivers. PC makes a sound and MT65xx PreLoader VCOM appears in the Device Manager.
-SP Flash Tool will not start download. Even tried download before plugging in usb, nothing happens.
-Tried many different flash tools versions. 1628, v5, v3, Nothing works. No error message but an error appears when I plug out the USB cord
-BROM Error: S_BROM_CMD_STARTCMD_FAIL(0x7D5)
Cannot pass bootroom start command! Possibly target power up too early.
Hi , maybe your SP Flash tool is not compatible for your chip , so try this one :
https://spflashtool.com/download/SP_Flash_Tool_v5.1628_Win.zip
Search firmware exactly for your device model .
You can use IDM -Internet Dowwnload Manager for fast downloading...
Teddy Lo said:
Hi , maybe your SP Flash tool is not compatible for your chip , so try this one :
https://spflashtool.com/download/SP_Flash_Tool_v5.1628_Win.zip
Search firmware exactly for your device model .
You can use IDM -Internet Dowwnload Manager for fast downloading...
Click to expand...
Click to collapse
I have already tried the 5.1628 version, it is also not working.
The latest version has a bug I think which causes it to have a RUntime error when picking a scatter file.
The old v3 will not accept any scatter file anymore.
Also I have downloaded two versions of stock rom already. First one is 800 mb and the second one is 2GB. Both do not work, but I suspect the first one to completely fail since it had an unmatching scatter file within.
Try this.Hold power button for 2 min if your phone boots up Good News It's usable.If not then It's only crap now.Mediatek devices are not supposed to be rooted and if somehow you managed to do that they will make sure you pay for it.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Try this.Hold power button for 2 min if your phone boots up Good News It's usable.If not then It's only crap now.Mediatek devices are not supposed to be rooted and if somehow you managed to do that they will make sure you pay for it.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I tried it but the device doesnt seem to respond to any button whatsoever. The device is not rooted though, I wanted to flash magisk but it all happened after unlocking the bootloader. But I have hope since the preloader is indeed detected in the PC.
Try to relock bootloader with adb if your device is recognised by ADB ...
Teddy Lo said:
Try to relock bootloader with adb if your device is recognised by ADB ...
Click to expand...
Click to collapse
device is no longer recognized by adb, it wont turn on anymore. Only as MT65xx preloader as it shows in the device manager
helpplease123 said:
device is no longer recognized by adb, it wont turn on anymore. Only as MT65xx preloader as it shows in the device manager
Click to expand...
Click to collapse
Follow this thread maybe is driver issue so read carefully ...
https://forum.xda-developers.com/showthread.php?t=2180436
Good luck
What's up with VCOM?
Well I don't think your PC would be able to detect your device because you haven't got the VCOM drivers yet. Get any VCOM driver for Mediatek, and then disable driver signature enforcing on Windows. Now fire up SPFT and select the scatter use v5.1628 as the newer ones seem to be unstable (also verified by OP). Now choose the Preloader for your device and then enter download mode. Turn off the phone (if you can't, just let it die until the battery is over). And then connect it using an USB cable, while SPFT is in download mode. You should be able to unbrick your device.
And as you said S_BROM_CMD_STARTCMD_FAIL(0x7D5), that is when the device powers up too early before the flash could begin. The 8 byte token is not received by the preloader and hence it ain't working. This is why you have to switch your phone off completely, and also try using a different USB cable
Note:
The preloader parition has an emergency download mode which is used to enable the download to take place. Now, if you flash the wrong preloader, then your device won't even be detected in SPFT or anywhere else. So yeah, in MTK preloader is the life of your phone. Please verify that you are flashing the correct preloader
BusinessKid said:
Well I don't think your PC would be able to detect your device because you haven't got the VCOM drivers yet. Get any VCOM driver for Mediatek, and then disable driver signature enforcing on Windows. Now fire up SPFT and select the scatter use v5.1628 as the newer ones seem to be unstable (also verified by OP). Now choose the Preloader for your device and then enter download mode. Turn off the phone (if you can't, just let it die until the battery is over). And then connect it using an USB cable, while SPFT is in download mode. You should be able to unbrick your device.
And as you said S_BROM_CMD_STARTCMD_FAIL(0x7D5), that is when the device powers up too early before the flash could begin. The 8 byte token is not received by the preloader and hence it ain't working. This is why you have to switch your phone off completely, and also try using a different USB cable
Note:
The preloader parition has an emergency download mode which is used to enable the download to take place. Now, if you flash the wrong preloader, then your device won't even be detected in SPFT or anywhere else. So yeah, in MTK preloader is the life of your phone. Please verify that you are flashing the correct preloader
Click to expand...
Click to collapse
Tried everything here, and I even used a windows 7 pc but it is still not working. The VCOM was already installed, in fact when I plug in the phone windows automatically detects it as the MTK Preloader VCOM USB port(COM13) in the device manager. The VCOM driver that is supposed to be installed leaves an error in the device manager (COM12). SP Flash tool still will not start flashing. No error messages, until I plug out the usb cord.
helpplease123 said:
Tried everything here, and I even used a windows 7 pc but it is still not working. The VCOM was already installed, in fact when I plug in the phone windows automatically detects it as the MTK Preloader VCOM USB port(COM13) in the device manager. The VCOM driver that is supposed to be installed leaves an error in the device manager (COM12). SP Flash tool still will not start flashing. No error messages, until I plug out the usb cord.
Click to expand...
Click to collapse
You do see that exclamation right - this means it isn't properly configured
---------- Post added at 01:37 PM ---------- Previous post was at 01:35 PM ----------
helpplease123 said:
Tried everything here, and I even used a windows 7 pc but it is still not working. The VCOM was already installed, in fact when I plug in the phone windows automatically detects it as the MTK Preloader VCOM USB port(COM13) in the device manager. The VCOM driver that is supposed to be installed leaves an error in the device manager (COM12). SP Flash tool still will not start flashing. No error messages, until I plug out the usb cord.
Click to expand...
Click to collapse
Looks like it's more of a Windows issue than your phone. If your preloader's good - you're safe. I think it's a COM bridge issue. Just stay on the wait and I'll get back to you in a minute or two
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
I'm working on a batch script for you to fix the COM issue. Would you mind sharing your Windows Version and Architecture?
I'm building it for Windows 7 x64 - if that's your PC?
BusinessKid said:
You do see that exclamation right - this means it isn't properly configured
Click to expand...
Click to collapse
---------- Post added at 01:37 PM ---------- Previous post was at 01:35 PM ----------
I mean the COM13 is fairly OK for the part, its the VCOM that comes from installing the phone. However the COM12 that came from the manual installer had the exclamation point.
Looks like it's more of a Windows issue than your phone. If your preloader's good - you're safe. I think it's a COM bridge issue. Just stay on the wait and I'll get back to you in a minute or two
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
Click to expand...
Click to collapse
Its already a great thanks from me for you to even post more than once. thank you so much!
[/COLOR]I'm working on a batch script for you to fix the COM issue. Would you mind sharing your Windows Version and Architecture?
I'm building it for Windows 7 x64 - if that's your PC?
Click to expand...
Click to collapse
Yes, in fact I have first tried it in Windows 10 x64 before switching back to this W7 x64 laptop. Same problem same outcome though
So let us go 101
Okay - the first thing that we'd do now is blow off those crappy drivers - uninstall them! Now get on your Windows 10 x64 PC. Install the VCOM drivers from this XDA thread. It's for elephone, however I've used it myself and it works really well on almost any device. Now power off your phone completely (no bootlooop, completely dark screen). Launch SPFT, select scatter, select the correct preloader and then hit on download. Do not connect your phone now! Now wait for 10 seconds. Now connect your phone. And let the download begin. If it works - fantastic, if it doesn't ping me back and I'll be waiting for replying to you. The batch script is almost done (I was doing some kernel work), I'll upload it once I'll be back home (on the way back now).
Fingers crossed :fingers-crossed:
BusinessKid said:
Okay - the first thing that we'd do now is blow off those crappy drivers - uninstall them! Now get on your Windows 10 x64 PC. Install the VCOM drivers from this XDA thread. It's for elephone, however I've used it myself and it works really well on almost any device. Now power off your phone completely (no bootlooop, completely dark screen). Launch SPFT, select scatter, select the correct preloader and then hit on download. Do not connect your phone now! Now wait for 10 seconds. Now connect your phone. And let the download begin. If it works - fantastic, if it doesn't ping me back and I'll be waiting for replying to you. The batch script is almost done (I was doing some kernel work), I'll upload it once I'll be back home (on the way back now).
Fingers crossed :fingers-crossed:
Click to expand...
Click to collapse
Dude holy ****, I cannot believe that it worked! I swear I was very confident that the problem was not in the drivers, but out of luck I started to follow that guide again from start to finish and selected the "MTK USB Port" in the device manager section. Then I plugged in and SP flash tool finally started! You rock!
Your welcome! I'm glad that worked!
Hello,
I have my Pocophone for 2 months now. I installed Lineage OS 16.0 succesfully and everything was working perfect. Out of nothing I got a blue screen and now my phone won't turn on anymore. When I connect it to my laptop , the device is seen as Qualcomm HS-USB QDLoader 9008. Looks like it's bricked...
Can someone help me to unbrick it?
Thanks in advance.
Greetings,
Bjarnie
have you tried ADB??
santiagoruel13 said:
have you tried ADB??
Click to expand...
Click to collapse
Not yet.. but can’t get in fastboot mode, so that’s not possible I think
You mean , your phone cant boot to fastboot mode??
---------- Post added at 03:27 PM ---------- Previous post was at 03:26 PM ----------
Fastboot reboot bootloader..
Have you tried that???
santiagoruel13 said:
You mean , your phone cant boot to fastboot mode??
---------- Post added at 03:27 PM ---------- Previous post was at 03:26 PM ----------
Fastboot reboot bootloader..
Have you tried that???
Click to expand...
Click to collapse
Yes, the phone won’t boot to fastboot mode with arrow up and power button. Will try it with laptop later today..
Fastboot mode is volume down button + power button.
Just connect the phone to pc. .then hit adb.
Then run the command
Adb reboot bootloader..
KabalLV said:
Fastboot mode is volume down button + power button.
Click to expand...
Click to collapse
Both not working, - and +.
santiagoruel13 said:
Just connect the phone to pc. .then hit adb.
Then run the command
Adb reboot bootloader..
Click to expand...
Click to collapse
Not working.. device isn’t recognized in cmd
Bjarnie said:
Hello,
I have my Pocophone for 2 months now. I installed Lineage OS 16.0 succesfully and everything was working perfect. Out of nothing I got a blue screen and now my phone won't turn on anymore. When I connect it to my laptop , the device is seen as Qualcomm HS-USB QDLoader 9008. Looks like it's bricked...
Can someone help me to unbrick it?
Thanks in advance.
Greetings,
Bjarnie
Click to expand...
Click to collapse
Go to
https://miui.blog/any-devices/qualcomm-qpst-tool/
As per my guess, your device is in EDL mode. I think you could directly flash fastboot rom to it in MiFlash tool, while it is seen as Qualcomm HS-USB QDLoader 9008.
ayush2901 said:
As per my guess, your device is in EDL mode. I think you could directly flash fastboot rom to it in MiFlash tool, while it is seen as Qualcomm HS-USB QDLoader 9008.
Click to expand...
Click to collapse
See the results.. unf not working.
Sydtek said:
Go to
https://miui.blog/any-devices/qualcomm-qpst-tool/
Click to expand...
Click to collapse
Thanks! I tried it without any result yet. Tried different roms/configs but everytime it ends with an error
Try to google the error's and see what you can find out about them.
Bjarnie said:
Thanks! I tried it without any result yet. Tried different roms/configs but everytime it ends with an error
Click to expand...
Click to collapse
Did you solved this? i have the same problem
alanleonardi said:
Did you solved this? i have the same problem
Click to expand...
Click to collapse
Are you using Intel or AMD Ryzen PC? Use Intel PC and use Miflash to flash the stock ROM.
hi
did you solve your problem? i have the same issue and no one can fix it
i have exactly the same problem with poco f1 and unfortunately no one knows what is these errors
some says it is because authorized account but when authorizes account be needed its error appear wile flashing not error of cannot receive hello pocket or can not read com port
I think it happpened because of wrong firmware? I already experienced this to my son's bricked tablet. which is LG Gpad v400 i flashed the wrong firmware which firmware of Gpad V410 and end up to bricked tablet. I think the only solution for that is jtag. Try to Search for pocophone jtag.
HELLO PACKETS ERROR
happened to me with Redmi3s
i tried possibly everything related to DRIVERS, ROMS, MIFLASHER VERSIONS, FASTBOOT ROM VERSION , STORED THEM IN SAPERATE LOCATION WITH SMALLER NAMES, TRIED ON TWO DIFFERENT PC (WIN10 / WIN7,) USED DIFFERENT CABLES, TRIED QUALCOME QLOADER METHOD
USING BLADE, I CUT THE GLUE AND OPENED THE PANEL BEHIND, used TEST POINT SHORT CIRCUIT METHOD , REMOVED BATTERY AND CHARGED OVERNIGHT
BUT
redmi3s NEVER resuscitated ...