I made a stupid mistake, i've flash in fastboot mode a Mi5 original ROM. so my Mi5s is bricked now. I tried flash with some tools that i found in internet. Miflashbeta some versions. I've sucess message in the final but phone doesn´t boot, even passed some time.
I have no flash mode available and no image on display.
COM port are in Qualcomm HS-USB QDLoader 9008, so i supposed that is is in EDL mode. After 30 times that i'm trying flashing i'm loosing any hope to fix it. Could anyone help me?
engpika said:
I made a stupid mistake, i've flash in fastboot mode a Mi5 original ROM. so my Mi5s is bricked now. I tried flash with some tools that i found in internet. Miflashbeta some versions. I've sucess message in the final but phone doesn´t boot, even passed some time.
I have no flash mode available and no image on display.
COM port are in Qualcomm HS-USB QDLoader 9008, so i supposed that is is in EDL mode. After 30 times that i'm trying flashing i'm loosing any hope to fix it. Could anyone help me?
Click to expand...
Click to collapse
Does fastboot recognize a device at all?
Yes, you are in EDL mode. When I was in EDL mode, I couldn't flash on my laptop. Switched to my desktop and I was finally able to flash the recovery ROM.
What error message are you getting when using MiFlash tool?
dgrasley said:
Does fastboot recognize a device at all?
Click to expand...
Click to collapse
no...
C:\WINDOWS\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\WINDOWS\system32>
golfinry said:
Yes, you are in EDL mode. When I was in EDL mode, I couldn't flash on my laptop. Switched to my desktop and I was finally able to flash the recovery ROM.
What error message are you getting when using MiFlash tool?
Click to expand...
Click to collapse
I have a success flash message. but device not booting at all.
Few things to try:
Different Cable
Different Computer/Port
Try different drivers
Turn off the phone - Once you turn it on, try to flash again right away.
Is the Miflash tool detecting the phone on COM port?
engpika said:
no...
C:\WINDOWS\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\WINDOWS\system32>
Click to expand...
Click to collapse
Isn't adb for android os? You have a bricked device so you need to try using fastboot to connect to phone, not adb. If you have fastboot and adb, "fastboot devices" will show your device if it is in fastboot mode. You can try to manually wipe then flash the parts of the ROM through fastboot or install twrp and recover nandroid backup.
MiFlash say successful but the phone still doesn't boot? Try to hold all the buttons(vol+,vol-,power) for at least one minute and check if something happens.
When I bricked my MI5 it took +- 5 hours to boot it after flashing a fastboot ROM. Just give it some time.
Sent from my MI 5 using Tapatalk
engpika said:
I made a stupid mistake, i've flash in fastboot mode a Mi5 original ROM. so my Mi5s is bricked now. I tried flash with some tools that i found in internet. Miflashbeta some versions. I've sucess message in the final but phone doesn´t boot, even passed some time.
I have no flash mode available and no image on display.
COM port are in Qualcomm HS-USB QDLoader 9008, so i supposed that is is in EDL mode. After 30 times that i'm trying flashing i'm loosing any hope to fix it. Could anyone help me?
Click to expand...
Click to collapse
Hi,
I know this is old, but I made the exact same mistake last night. Did you manage to fix it? How?
Thank you in advance
Related
Hi,
My girlfriend bricked my phone (i think), Everything i do always saying Fastboot Mode Started but when i try to do some commands, gives-me errors, usb_read() transation failed etc..
On my computer, device detected as CMCC Composite ADB Interface.
Can anyone help me?
Thanks
leonardoc said:
Hi,
My girlfriend bricked my phone (i think), Everything i do always saying Fastboot Mode Started but when i try to do some commands, gives-me errors, usb_read() transation failed etc..
On my computer, device detected as CMCC Composite ADB Interface.
Can anyone help me?
Thanks
Click to expand...
Click to collapse
What was she doing when it bricked
Can you boot into OS normally?
itsbighead said:
What was she doing when it bricked
Can you boot into OS normally?
Click to expand...
Click to collapse
I don't know, i think that was updating and run out off battery..
No, only fastboot, but i think is bricked, because i do "fastboot erase boot" and keep saying "earsing 'boot'" and is stuck :/
Actually i can put phone into qualcomm 9008, but BoardDiag3.99c gives-me error when testing :/
I keep changing roms since long time before on my oneplus devices, i bought asus zenfone 2 and tried to root the phone, it got bricked and i unbricked successfully by using xFSTK tool. device turned on like before but unable to connect to pc, even when MTP is selected it just starts charging when i connect it to pc, even tried with different types of cables still the same issue. tried in recovery and fastboot as well.
at least if it would work in fastboot then i can install twrp and add custom rom. not even able to do that.
P.S - tried even installing adb, intel drivers. problem doesn't seem to be going..
PLEASE HELP.
deejaysandee143 said:
I keep changing roms since long time before on my oneplus devices, i bought asus zenfone 2 and tried to root the phone, it got bricked and i unbricked successfully by using xFSTK tool. device turned on like before but unable to connect to pc, even when MTP is selected it just starts charging when i connect it to pc, even tried with different types of cables still the same issue. tried in recovery and fastboot as well.
at least if it would work in fastboot then i can install twrp and add custom rom. not even able to do that.
P.S - tried even installing adb, intel drivers. problem doesn't seem to be going..
PLEASE HELP.
Click to expand...
Click to collapse
flash latest Raw firmware with asus flash tool. get it from following thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
flash latest Raw firmware with asus flash tool. get it from following thread.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Brother, after completing this process only i am facing this issue..
unable to connect my phone in any mode. not even to other pc.
Fast charging works?
There may be a problem with the flex cable that has the sim + sd slots on it. Costs 3$ on ebay and its very easy to replace.
pecholino said:
Fast charging works?
There may be a problem with the flex cable that has the sim + sd slots on it. Costs 3$ on ebay and its very easy to replace.
Click to expand...
Click to collapse
No, fast charging was not working after the process in xFSTK tool. it would take around 8 hours to get 100 %
deejaysandee143 said:
Brother, after completing this process only i am facing this issue..
unable to connect my phone in any mode. not even to other pc.
Click to expand...
Click to collapse
i said flash raw firmware again.. you will overcome the issue! which version you are currently on?
sukhwant717 said:
i said flash raw firmware again.. you will overcome the issue! which version you are currently on?
Click to expand...
Click to collapse
The phone doesn't boots normally, and neither connects in fastboot nor in recovery. only shows error. its version 5
deejaysandee143 said:
The phone doesn't boots normally, and neither connects in fastboot nor in recovery. only shows error. its version 5
Click to expand...
Click to collapse
then you have to use xfstk again..you can not do anything until you are able to go into fastboot mode. flash xfstk again and again until you enter fastboot mode
sukhwant717 said:
then you have to use xfstk again..you can not do anything until you are able to go into fastboot mode. flash xfstk again and again until you enter fastboot mode
Click to expand...
Click to collapse
I can enter only in fastboot mode but fastboot wont be detected in adb, as i mentioned it's not getting recognized..
Well I am having the same simptoms since the sdcard slot got burned. No fast charging and no pc recognition. I am currently waiting for the flex cable so I can fix it
Hello sirs, I hope you can help me.
I have a mi6 that turned into a brick. Hold the buttons to it to give restart / download mode or put it to load. He does not respond to anything.
However,
By putting it on your computer it recognizes you as Qualcomm QDLoader 9008.
I wonder if I can recover it yet. or unfortunately it turned a paper weight.
DL Xiaomi flash tool and flash fastboot rom. It will be fine.
icrunchbanger said:
DL Xiaomi flash tool and flash fastboot rom. It will be fine.
Click to expand...
Click to collapse
I tried to do this form, downloaded all the miui site drivers, adb fastboot and cualcomm driver.
How to run my flash with a last method with the xiaomi global mi6 I got the following error:
"Cannot receive hello packet Xiaomi Device"
The program tried a few more times and nothing more.
What can I be doing wrong? Do you have another option? because he is in what they call DeadBrick (I discovered this term only now, after searching the forums)
XeeXa said:
I tried to do this form, downloaded all the miui site drivers, adb fastboot and cualcomm driver.
How to run my flash with a last method with the xiaomi global mi6 I got the following error:
"Cannot receive hello packet Xiaomi Device"
The program tried a few more times and nothing more.
What can I be doing wrong? Do you have another option? because he is in what they call DeadBrick (I discovered this term only now, after searching the forums)
Click to expand...
Click to collapse
I know, i was there. Reboot your computer and start again.
I restarted and tried again.
I formatted and installed only the drivers and the error continues.
I tried with miflash 2015 until version miflash2017
I think, you device isn't in EDL mode. You open back cover of device. Make test point for QDL 9008. Then, you flash fastboot rom by Mi flash tool. It's very simply. I made it for unbrick my Mi6 several times.
See video here.
https://youtu.be/vSNRQdUuNYw
bahuy2003 said:
I think, you device isn't in EDL mode. You open back cover of device. Make test point for QDL 9008. Then, you flash fastboot rom by Mi flash tool. It's very simply. I made it for unbrick my Mi6 several times.
See video here.
Click to expand...
Click to collapse
Is this the only way to put the phone in edl mode?
Yes, it's only way for Mi6, which is locked bootloader.
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Solved: Use the first blank flash from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
mookiexl said:
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Click to expand...
Click to collapse
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
mookiexl said:
Solved: Use the first blank flash to from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
Click to expand...
Click to collapse
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Technical said:
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Click to expand...
Click to collapse
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
Before connecting the phone, start the blankflash program. Maybe you have to repeat it a couple of times. Also try different cables, ports and computers.
Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
mookiexl said:
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Click to expand...
Click to collapse
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
LØNEWØLF said:
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
Click to expand...
Click to collapse
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go: https://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0! ???
Dany XP said:
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go:
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0!
Click to expand...
Click to collapse
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
LØNEWØLF said:
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
Click to expand...
Click to collapse
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Dany XP said:
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Click to expand...
Click to collapse
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
LØNEWØLF said:
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
Click to expand...
Click to collapse
Uh...good question
Last time i flashed ThE stock ROM via mi flash tool i lost energy on my pc so prosess ended un error. My phone was in fastboot but i rebooted and never turns on again. I cant get fastboot mide anymore. Adb not recognice it but i can see it on PC in device mánager as "gualcomm HS-USB diagnostics 900E (COM3)
Any help?
MaxxTwo said:
Last time i flashed ThE stock ROM via mi flash tool i lost energy on my pc so prosess ended un error. My phone was in fastboot but i rebooted and never turns on again. I cant get fastboot mide anymore. Adb not recognice it but i can see it on PC in device mánager as "gualcomm HS-USB diagnostics 900E (COM3)
Any help?[/QUOTE
Just go to fastboot mode and type: "fastboot oem edl"
If you can´t enter fastboot, you have to open your phone and connect both testpoints
it's all on xda questions and anwsers mi A2 lite
Click to expand...
Click to collapse
Nxkealen said:
MaxxTwo said:
Last time i flashed ThE stock ROM via mi flash tool i lost energy on my pc so prosess ended un error. My phone was in fastboot but i rebooted and never turns on again. I cant get fastboot mide anymore. Adb not recognice it but i can see it on PC in device mánager as "gualcomm HS-USB diagnostics 900E (COM3)
Any help?[/QUOTE
Just go to fastboot mode and type: "fastboot oem edl"
If you can´t enter fastboot, you have to open your phone and connect both testpoints
it's all on xda questions and anwsers mi A2 lite
Click to expand...
Click to collapse
Thanks! But its in indi, can not undetstand nothing XD
Click to expand...
Click to collapse
https://redirect.viglink.com/?key=e...ter-t3862648/amp/&ref=https://www.google.com/
1- install mi flash tool and Qualcomm driver on your Pc
2- open the phone (just remove the battery connector )
3-plug a USB cable in the device
4- short the jtag pins(you can find their location in this page www mobilerdx com/2018/09/xiaomi-redmi-6-pro-test-point-boot-into-edl-9008-mode.html
7-plug the USB cable in the Pc while shortening the pins
If you do these steps mi flash tool should reconize your device and you will be able to flash it
Thanks man! My phone is working properly again. Let me tell my story in this.
Never opened a device before this. So I decided to take it to the official service. Unfortunately they told me that the mother board was damaged and the cost to REPLACE it is the same as buy a new phone!
So I been forced to try fix it by my self.
A couple of latex gloves XD and don't ask how I did to short the points but it works...
Now I'm using my Daisy again and waiting for official Android Q !!!