Related
ii just got my redmi 3s and i just bricked it. it does not boot up into any splash logo, recovery or download mode, just always stays on black screen until battery dies then it flashes red if i power on. now when i plug it in to the computer the only thing that pops up is Qualcomm HS-USB Diagnostics 900E which i dont need. i need qualcomm hs-usb qdloader 9008 but no tools detect the phone other then QFIL and even when i give it all the files it just says
Code:
Start Download
COM Port number:4
Switch To EDL
Download Fail:Failed to Switch to Emergency Download mode
Download Fail:Switch To EDL FailFireHose Fail
Finish Download
i have tried touching random copper points on the board but nothing reboots the phone into EDL.
Maybe
Found this, not sure if it's what you looking for,
http://en.miui.com/thread-286357-1-1.html
---------- Post added at 08:26 PM ---------- Previous post was at 08:16 PM ----------
Found this, not sure if it's what you looking for,
http://en.miui.com/thread-286357-1-1.html
Better idea is search Ali express for "deep flash cable xiaomi"
jazz452 said:
Found this, not sure if it's what you looking for,
http://en.miui.com/thread-286357-1-1.html
---------- Post added at 08:26 PM ---------- Previous post was at 08:16 PM ----------
Found this, not sure if it's what you looking for,
http://en.miui.com/thread-286357-1-1.html
Better idea is search Ali express for "deep flash cable xiaomi"
Click to expand...
Click to collapse
wow thats very interesting, ill try to buy one.
been reading on it for a bit. think this can really work?
or you can purchase something called a jig i hope i spelled it properly from ebay or amazon it shorts the usb testpoints and puts your phone into edl or fastboot mode
xdarkmario said:
wow thats very interesting, ill try to buy one.
been reading on it for a bit. think this can really work?
Click to expand...
Click to collapse
If the test points work the cable should, maybe the other cable will work, seems strange that they say to use to deep flash cable though, sure these people know about the jig cable so wouldn't chance it.
https://www.youtube.com/watch?v=DJZ6Ka7mrIA
You can buy cable in UK
http://www.fonefunshop.co.uk/cable_picker/99673_Xiaomi_Deep_Flash_Cable.html
Even get a how to on the page.
You can also try this unbrick guide on MIUI forum.
http://en.miui.com/thread-327861-1-1.html
He can't get to recovery.
xdarkmario said:
ii just got my redmi 3s and i just bricked it. it does not boot up into any splash logo, recovery or download mode, just always stays on black screen until battery dies then it flashes red if i power on. now when i plug it in to the computer the only thing that pops up is Qualcomm HS-USB Diagnostics 900E which i dont need. i need qualcomm hs-usb qdloader 9008 but no tools detect the phone other then QFIL and even when i give it all the files it just says
Code:
Start Download
COM Port number:4
Switch To EDL
Download Fail:Failed to Switch to Emergency Download mode
Download Fail:Switch To EDL FailFireHose Fail
Finish Download
i have tried touching random copper points on the board but nothing reboots the phone into EDL.
Click to expand...
Click to collapse
try this
Boot into fastboot mode and connect your phone to pc
open command window and type fastboot oem edl
It worked for me
Kanth's said:
try this
Boot into fastboot mode and connect your phone to pc
open command window and type fastboot oem edl
It worked for me
Click to expand...
Click to collapse
again, still cant do that. I cant do anything. I brought the cable a couple of days ago so when it gets here ill try it, if not then ill send it to warranty repair
xdarkmario said:
again, still cant do that. I cant do anything. I brought the cable a couple of days ago so when it gets here ill try it, if not then ill send it to warranty repair
Click to expand...
Click to collapse
Is it hardbricked?
Kanth's said:
Is it hardbricked?
Click to expand...
Click to collapse
yes i assume hitting power immediately puts it into Qualcomm HS-USB Diagnostics 900E mode, no screens no lights
xdarkmario said:
yes i assume hitting power immediately puts it into Qualcomm HS-USB Diagnostics 900E mode, no screens no lights
Click to expand...
Click to collapse
Take a look at this one - http://xiaomitips.com/guide/how-to-fix-bricked-redmi-3s-on-miui-7-8/
Kanth's said:
Take a look at this one - http://xiaomitips.com/guide/how-to-fix-bricked-redmi-3s-on-miui-7-8/
Click to expand...
Click to collapse
of course i have tried this before.
Please bear in mind that the method of reflashing Android ROM can only works fixing soft-bricked devices and NOT for hard-bricked ones.
Click to expand...
Click to collapse
I softbricked my redmi 3s as well, because I disabled some google apps.
Needless to say, you have to:
1. manually update/install qualcomm driver (when your phone in download mode).
2. download a fastboot rom
3. download miphone miflash tool, enable "flash all" option when you flash the fastboot rom.
there's a thread here on xda as well. search for bricked redmi 3 workaround.
do you want to enter download mode?
pressing vol up + vol down at once (Off position), and put in the USB cable
If the phone is on turn off 1st and imediatelly put in USB cable while, press vol up+ vol down
can you enter to fastboot?
I have same problem on my Redmi 3 Pro. No fastboot, No booting, No blink red light, No Charging, but if my device plug on pc it detected QC bla.. bla.. on port device manager. I don't know what to do anymore. *hopeless* *tearr* :crying:
the only way for hard brick is test points or deep flash cable, end of, I would go with cable less chance of breaking something while taking phone apart. If the phone is detected then it's only semi hard brick and can be fixed with Mi flash tool.
http://en.miui.com/thread-235865-1-1.html
http://en.miui.com/thread-254606-1-1.html
might be better.
but remeber to download the rom for your device.
xdarkmario said:
ii just got my redmi 3s and i just bricked it. it does not boot up into any splash logo, recovery or download mode, just always stays on black screen until battery dies then it flashes red if i power on. now when i plug it in to the computer the only thing that pops up is Qualcomm HS-USB Diagnostics 900E which i dont need. i need qualcomm hs-usb qdloader 9008 but no tools detect the phone other then QFIL and even when i give it all the files it just says
Code:
Start Download
COM Port number:4
Switch To EDL
Download Fail:Failed to Switch to Emergency Download mode
Download Fail:Switch To EDL FailFireHose Fail
Finish Download
i have tried touching random copper points on the board but nothing reboots the phone into EDL.
Click to expand...
Click to collapse
What did you do to brick it? Please tell us so that new users don't face the same problem as you
Ptmaroct said:
What did you do to brick it? Please tell us so that new users don't face the same problem as you
Click to expand...
Click to collapse
That's a good valid point
First of all, i live in Bangladesh. I asked a relative of mine who lives in Sweden to buy me this phone. So, there is no way for me to send this phone back to ZTE.
Now let me explain how i got into this huge mess. I installed twrp successfully using this post - https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
i only followed part A of this post. Then i needed to root. so i tried to flash supersu 2.79 first but failed. Then i tried to flash supersu 2.65 as someone commented that they failed with 2.79 but succeeded with 2.65. However, after flashing supersu 2.65 i soft bricked my phone. i could still access twrp 3.0.2. After a while, i downloaded b08 update.zip and tried to flash it through twrp but failed. then i saw this post - https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
and this post - https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And tried to update twrp to 3.03. which then hard bricked my phone. now i cannot access anything. when i try to start my phone it shows the zte logo for a second and the whole screen goes blank with the red led.
same thing happens with volume up+power and volume down+power. And there is no way to turn the phone off. So, i waited a whole day for the phone to empty it's battery and tried to boot to edl mode using volume up+down but Qualcomm HS-USB QDLoader does not appear. The only thing i can get to connecting to my computer is handset diagnostic interface.
Now only a brilliant dev can help me. So can someone PLEASE Help me.
Also i've found this post is very similar to my problem https://forum.xda-developers.com/axon-7/help/bricked-a2017g-b03-help-please-t3487635
Update: Fixed using this post >> https://forum.xda-developers.com/ax...ory-brick-repair-manual-t3585898#post71764940
& this >> http://4pda.ru/forum/index.php?showtopic=814221&st=0#entry60102671
Why can't you boot into EDL mode?
That's strange to me...
Did you try another computer to see if it pops up there?
Then try to reflash recovery if you can...
Abiram26 said:
Why can't you boot into EDL mode?
That's strange to me...
Did you try another computer to see if it pops up there?
Then try to reflash recovery if you can...
Click to expand...
Click to collapse
yes i have. but in the device manager, instead of Qualcomm HS-USB QDLoader, Handset Diagnostic Interface appears.
Furthermore, computers does not recognize any adb device when i connect my axon 7
what do i do???
Edit: when i uninstall Handset Diagnostic Interface from device manager and then connect my phone with both volume keys pressed, at first qusb_bulk appears but after automatic installation of hardware software it's Handset Diagnostic Interface all over again
Well I did some Google'ing for you and I guess the things in these threads might be your best bet:
http://www.modaco.com/forums/topic/343587-guide-de-bricking-a-zte-blade/ (same thread-ish on XDA: https://forum.xda-developers.com/showthread.php?t=2163493 )
http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
However all these methods are not tested with the Axon 7 and seem pretty risky to me...
If I were you I'd send the phone back to Sweden so the relative can send it back to ZTE.
I'm not sure if this falls under the ZTE warranty stuff so they might charge you a bit; anyhow it's still the better option than throwing this phone away I'd say.
I don't think I can really help you here, sorry :s
PS: If you are going to try these risky methods; don't blame me if it goes wrong...
EDIT: You might also want to try to go to the ZTE website and try to get some support from there (customer support, support from the forum/community ther, etc.)
Perhaps they can give you the right tools to unbrick your Axon7
Abiram26 said:
Well I did some Google'ing for you and I guess the things in these threads might be your best bet:
http://www.modaco.com/forums/topic/343587-guide-de-bricking-a-zte-blade/ (same thread-ish on XDA: https://forum.xda-developers.com/showthread.php?t=2163493 )
http://www.modaco.com/forums/topic/337757-update-save-ur-bricked-v880-and-also-the-imei/
However all these methods are not tested with the Axon 7 and seem pretty risky to me...
If I were you I'd send the phone back to Sweden so the relative can send it back to ZTE.
I'm not sure if this falls under the ZTE warranty stuff so they might charge you a bit; anyhow it's still the better option than throwing this phone away I'd say.
I don't think I can really help you here, sorry :s
PS: If you are going to try these risky methods; don't blame me if it goes wrong...
EDIT: You might also want to try to go to the ZTE website and try to get some support from there (customer support, support from the forum/community ther, etc.)
Perhaps they can give you the right tools to unbrick your Axon7
Click to expand...
Click to collapse
:crying::crying::crying::crying:
if only i could boot into edl mode
I don't think your phone is in such a dire condition. I was contacted by @raystef66 only last night. He made the same mistake as you did, trying to flash SuperSU via TWRP on a locked bootloader phone. However, he didn't take all steps you took.
If I were you, I'd try to somehow prevent the PC from automatically installing the ZTE DFU (Diagnostics) driver. You say the device appears to be in EDL mode when you connect it (QUSB_BULK) and then it installs new drivers. Can you somehow cancel that process?
Here's a microsoft guide on how to prevent your PC from automatically installing drivers. Maybe try that and reconnect your device. It might get recognised as QUSB_BULK and then you can restore your stock recovery via the Axon7tool? If you can do that, it shouldn't be a lost cause?
Send me a PM with your Hangouts, let's see if I can help.
Controllerboy said:
I don't think your phone is in such a dire condition. I was contacted by @raystef66 only last night. He made the same mistake as you did, trying to flash SuperSU via TWRP on a locked bootloader phone. However, he didn't take all steps you took.
If I were you, I'd try to somehow prevent the PC from automatically installing the ZTE DFU (Diagnostics) driver. You say the device appears to be in EDL mode when you connect it (QUSB_BULK) and then it installs new drivers. Can you somehow cancel that process?
Here's a microsoft guide on how to prevent your PC from automatically installing drivers. Maybe try that and reconnect your device. It might get recognised as QUSB_BULK and then you can restore your stock recovery via the Axon7tool? If you can do that, it shouldn't be a lost cause?
Click to expand...
Click to collapse
I have tried this, but axon7tool does not recognize any adb device. When i input adb devices command in cmd there is no device. However, it did get recognized as QUSB_BULK after disabling automatic driver installation through group policy. What do i do??
Edit: after seeing this post - https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
i'm really panicking. "Handset Diagnostic Interface" is DFU mode. "handset diagnostic interface (DFU) (ComX)" i just ignored the DFU part when posting. Does this mean i cannot unbrick my phone???
Please Help
nsabir said:
I have tried this, but axon7tool does not recognize any adb device. When i input adb devices command in cmd there is no device. However, it did get recognized as QUSB_BULK after disabling automatic driver installation through group policy. What do i do??
Edit: after seeing this post - https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
i'm really panicking. "Handset Diagnostic Interface" is DFU mode. "handset diagnostic interface (DFU) (ComX)" i just ignored the DFU part when posting. Does this mean i cannot unbrick my phone???
Please Help
Click to expand...
Click to collapse
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.
Oki said:
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.
Click to expand...
Click to collapse
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??
Oki said:
You can make Windows to use the right driver so you will be able to use axon7tool. So if you have problems connecting to your phone as QUSB_BULK, download Zadig to your computer and replace your drivers with WinUSB ones. Open Zadig tool, go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool and flash TWRP 3.0.2-2 signed again and continue with the unlock procedure.
If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.
All the answers on how to return to a working state or not falling into a soft brick like yours were just in the thread of the guide you didn't complete. Devices with the Qualcomm Snapdragon 820 are unbrickable. So do not panic, and read the whole thread [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM.
Click to expand...
Click to collapse
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??
nsabir said:
My QUSB_BULK is not with a warning sign. And i have already used Zadig.
At first, i couldn't get past DFU mode. But after following @Controllerboy instructions i am able to get QUSB_BULK in my device manager. But it's all the same.
For axon7tool to work the computer has to first recognize my a2017g as a adb device. That's where the problem is. My phone is not being recognized as an adb device. When i use adb devices on cmd there is no listed device. I have already tried this with other computers but the results are the same.
what do i do??
Click to expand...
Click to collapse
EDL mode has nothing to do with adb!!!!! adb only connects to recovery or a booted system. fastboot connects to bootloader, and Axon7tool communicates with the EDL bootstrap. In order to use Axon7tool (to flash or backup boot or recovery partitions) your computer has to detect your device as QUSB_BULK. Obviously in that mode adb or fastboot will not find your device in a compatible state.
What can you do?
1. read the whole thread, not just the opening post. As advised.
2. Use Axon7tool to flash the same TWRP 3.0.2-2 you flashed before. It is signed, so the bootloader detects it as a valid ZTE image even when the bootloader is still locked.
3. Unlock your A2017G phone.
4. enjoy flashing and reflashing all the multiple roms, patches, etc.
Oki said:
EDL mode has nothing to do with adb!!!!! adb only connects to recovery or a booted system. fastboot connects to bootloader, and Axon7tool communicates with the EDL bootstrap. In order to use Axon7tool (to flash or backup boot or recovery partitions) your computer has to detect your device as QUSB_BULK. Obviously in that mode adb or fastboot will not find your device in a compatible state.
What can you do?
1. read the whole thread, not just the opening post. As advised.
2. Use Axon7tool to flash the same TWRP 3.0.2-2 you flashed before. It is signed, so the bootloader detects it as a valid ZTE image even when the bootloader is still locked.
3. Unlock your A2017G phone.
4. enjoy flashing and reflashing all the multiple roms, patches, etc.
Click to expand...
Click to collapse
Sir, i don't u understand my problem properly. Let me give u a thorough description.
When i press and hold the power button the phone vibrates shows ZTE logo for less than a second then the screen turns off and the LED turns red.
When i press volume up+power same thing happens.
When i press volume down+power same thing.
And i cannot power off my phone no matter what i do it always stays at that state until the battery is empty.
Then if i press volume up+down at the same time and insert usb red led turn on.
And when i insert the usb in any of these states only one thing appears on my device manager is "Handset Diagnostic Interface (DFU) (ComX)"
But if i Uninstall Handset Diagnostic Interface (DFU) (ComX) from device manager and disable automatic driver installation through group policy then QUSB_BULK appears with a yellow sign.
If i use Zadig to install winusb driver then the yellow sign disappears.
U r telling me to read the whole thread. I have done so. But in DFU mode adb devices command doesn't list any device. If my computer doesn't see my device as an adb device how can i do anything.
I have also tried to use axon7tool -w recovery command since my device is in qusb_bulk mode. But cmd says no device detected.
2017 DFU mode investigation
Bricked A2017G
These posts have given me a big scare. Since no one has been able to recover from the same condition that i am in right now.
That's why i'm asking the help of experts. Please help me.
I have also came to a conclusion myself that if a tool like this Flashing recovery or this ZTE Open Download Mode or maybe this [TOOL][ALPHA] ZTE Warp 4G Unbrick Tool is not developed then this particular Qualcomm Phone is Brickable.
I am saying this because after a good amount of googling i came to know that when qualcomm phones are bricked it goes into emergency download mode which shows as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB QDLoader 9006" on device manager. And there are a lot of guides to unbrick from that state. But only old ZTE devices go into "Handset Diagnostic Interface (DFU) (ComX)" mode aka DFU mode.
And there are different guides for different models.
This is why i am panicking and asking for the help of experts. If there was a guide to recover from this state this post wouldn't exist. So if u can, please help.
And sorry for my english, i tried my best.
nsabir said:
Sir, i don't u understand my problem properly. Let me give u a thorough description.
When i press and hold the power button the phone vibrates shows ZTE logo for less than a second then the screen turns off and the LED turns red.
When i press volume up+power same thing happens.
When i press volume down+power same thing.
And i cannot power off my phone no matter what i do it always stays at that state until the battery is empty.
Then if i press volume up+down at the same time and insert usb red led turn on.
And when i insert the usb in any of these states only one thing appears on my device manager is "Handset Diagnostic Interface (DFU) (ComX)"
But if i Uninstall Handset Diagnostic Interface (DFU) (ComX) from device manager and disable automatic driver installation through group policy then QUSB_BULK appears with a yellow sign.
If i use Zadig to install winusb driver then the yellow sign disappears.
U r telling me to read the whole thread. I have done so. But in DFU mode adb devices command doesn't list any device. If my computer doesn't see my device as an adb device how can i do anything.
I have also tried to use axon7tool -w recovery command since my device is in qusb_bulk mode. But cmd says no device detected.
2017 DFU mode investigation
Bricked A2017G
These posts have given me a big scare. Since no one has been able to recover from the same condition that i am in right now.
That's why i'm asking the help of experts. Please help me.
I have also came to a conclusion myself that if a tool like this Flashing recovery or this ZTE Open Download Mode or maybe this [TOOL][ALPHA] ZTE Warp 4G Unbrick Tool is not developed then this particular Qualcomm Phone is Brickable.
I am saying this because after a good amount of googling i came to know that when qualcomm phones are bricked it goes into emergency download mode which shows as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB QDLoader 9006" on device manager. And there are a lot of guides to unbrick from that state. But only ZTE devices go into "Handset Diagnostic Interface (DFU) (ComX)" mode aka DFU mode.
And there are different guides for different models.
This is why i am panicking and asking for the help of experts. If there was a guide to recover from this state this post wouldn't exist. So if u can, please help.
And sorry for my english, i tried my best.
Click to expand...
Click to collapse
Can you boot into the bootloader by pressing the button combination?
Oki said:
Can you boot into the bootloader by pressing the button combination?
Click to expand...
Click to collapse
No i cannot. Everything seems to be pointing back to DFU mode.
I need something like Method 5 of this post How to recover a ZTE Blade/Libra/v880 after a bad flash for A2017G
nsabir said:
No i cannot. Everything seems to be pointing back to DFU mode.
I need something like Method 5 of this post How to recover a ZTE Blade/Libra/v880 after a bad flash for A2017G
Click to expand...
Click to collapse
Hi, maybe this can help you, is the chinese forum, i know is a shot in the dark, but your case i think need a special treatment, sorry for my english, the link:
http://www.myzte.cn/forum-1037-1.html
and the tutorials:
http://www.myzte.cn/forum.php?mod=forumdisplay&fid=1037&filter=typeid&typeid=2243
Use Google translator, and good luck, sorry if this is a waste of time for you, i am trying to help
PS: RMA chinese http://rma.zte.com.cn/
Altomugriento said:
Hi, maybe this can help you, is the chinese forum, i know is a shot in the dark, but your case i think need a special treatment, sorry for my english, the link:
http://www.myzte.cn/forum-1037-1.html
and the tutorials:
http://www.myzte.cn/forum.php?mod=forumdisplay&fid=1037&filter=typeid&typeid=2243
Use Google translator, and good luck, sorry if this is a waste of time for you, i am trying to help
PS: RMA chinese http://rma.zte.com.cn/
Click to expand...
Click to collapse
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.
nsabir said:
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.
Click to expand...
Click to collapse
Do you find something useful? I think I find someone in that forum, exactly in your position, all the answers pointing to RMA for the fix, sorry, maybe later can take another look and search for a solution.
Enviado desde mi ZTE A2017U mediante Tapatalk
nsabir said:
please don't embarrass me by saying sorry. I appreciate the fact that u even attempted to help me. thank u.
I am going through the Chinese posts and hoping to find something useful.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3551590
Enviado desde mi ZTE A2017U mediante Tapatalk
Altomugriento said:
https://forum.xda-developers.com/showthread.php?t=3551590
Enviado desde mi ZTE A2017U mediante Tapatalk
Click to expand...
Click to collapse
Thank you for the link. But i tried this miflash tools weeks ago.
Here is the full guide in my opinion for the mi flash tool.
http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
Unfortunately, the A2017G does not have 9008 port. It has ZTE's own Handset Diagnostic Interface (DFU) (ComX) for which i need the latest version of ZTE firmware flasher. At the moment only ZTE have this. So, my bricked phone is a lost cause.
Well, today, I flash a wrong firmware on my RN3 pro RR 5.8.3, unlock unofficially and get brick. No fastboot, No recovery, long press power button only brought splash screen for a second then screen goes black again. When stick to PC only red led blinking, on Device manager show Qualcomm HS-USB Diagnostics 900E so no Miflash.
Okay after a whole morning, I found this method here http://en.miui.com/forum.php?mod=viewthread&tid=266598&highlight=900e.. I tried method 3 from that thread because the other are just unreadable. So here is the step:
1. Plug the phone to PC - Red led blinking
2. Hold both 3 button: Volume up, Volume Down, Power button for around 10s. Phone vibrate and show the Linux Penguin Icon (Qualcom mode)
3. Check in Device manager/Port , it show other (unfortunately not the 9008 as in the thread). I check with Miflash Phone is recognize but i Cant flash any thing
4. SO i tried using this method here (step 4 ) https://forum.xda-developers.com/showpost.php?p=69613342&postcount=3 and get into EDL mode with 9008 port. Voila!
Optional
5. Then I flash this TWRP and unlock officially from here https://forum.xda-developers.com/redmi-note-3/how-to/unlock-unofficially-install-zcx-twrp-t3586778 and the beast is up again ! :highfive:
So i post this here to help anyone stuck in EDL mode and dont have a DFC or dont want to use test point method.
hope this help .
Thanks for sharing.
I already have deep flash cable (btw I made it myself, it is easy) and I have used it some times... But it is good if u don't have the cable!!
Regards!
Thanks a lot for this small post, it saved me from throwing this phone out of the window.
I could update MIUI using fastboot EDL, weirdely enough you cannot update official MIUI without unlocking the bootloader... WTF xiaomi
Saved my ass man thank you i got a real headache from all the failed attempts but u did the job.
my Redmi 4 no response. wat I do now.
when I connect usb cable to phone to pc it's show direct edl mode or Qualcomm Snapdragon 9008 is connected in port .
so what happened it?
wat I do now pls help me.
Hello I have a ZTE smartphone and I rooted it and unlocked the Bootloader.
Then i wanted to update it and locked the bootloader.
Now it shows only the ZTE logo if i turn it on.
And i cant enter EDL mode with the buttons.
What should i do?
sorry for my bad english
Tried wipe?
UltraBackfisch said:
Hello I have a ZTE smartphone and I rooted it and unlocked the Bootloader.
Then i wanted to update it and locked the bootloader.
Now it shows only the ZTE logo if i turn it on.
And i cant enter EDL mode with the buttons.
What should i do?
sorry for my bad english
Click to expand...
Click to collapse
You bricked it. Which guide did you use?? All of them tell you not to do this dumb crap ?
You didn't have to lock in order to update... Just downloading a flashable for your phone model would have been enough
You'll have to enter DFU at least. What happens when you hold both Vol+ and Vol- and insert the cable (other end on the PC of course)? If a red LED turns on, then you are on DFU. Open device manager and tell me what you see under Ports (COM & LPT). If it is DFU then you can use MultiDL to enter EDL, then an EDL package to fix your mess
Choose an username... said:
You bricked it. Which guide did you use?? All of them tell you not to do this dumb crap
You didn't have to lock in order to update... Just downloading a flashable for your phone model would have been enough
You'll have to enter DFU at least. What happens when you hold both Vol+ and Vol- and insert the cable (other end on the PC of course)? If a red LED turns on, then you are on DFU. Open device manager and tell me what you see under Ports (COM & LPT). If it is DFU then you can use MultiDL to enter EDL, then an EDL package to fix your mess
Click to expand...
Click to collapse
I pressed the Vol buttons and insert the cable and the LLD turns on but it dont react and in my device manager there is nothing exept my PC disks
UltraBackfisch said:
I pressed the Vol buttons and insert the cable and the LLD turns on but it dont react and in my device manager there is nothing exept my PC disks
Click to expand...
Click to collapse
your pc disks? Lmao
You have to open the Ports (COM & LPT) tab
The phone won't react at all when it is in DFU, that's fine. Download MultiDL and follow the guide on how to use it. It's in this forum
Choose an username... said:
your pc disks? Lmao
You have to open the Ports (COM & LPT) tab
The phone won't react at all when it is in DFU, that's fine. Download MultiDL and follow the guide on how to use it. It's in this forum
Click to expand...
Click to collapse
Can you send me the link?
@UltraBackfisch: Can you use the forum search function?
AnonVendetta said:
@UltraBackfisch: Can you use the forum search function?
Click to expand...
Click to collapse
Sorry i dont know how.
But i know i want that my ZTE works fine
Choose an username... said:
your pc disks? Lmao
You have to open the Ports (COM & LPT) tab
The phone won't react at all when it is in DFU, that's fine. Download MultiDL and follow the guide on how to use it. It's in this forum
Click to expand...
Click to collapse
Ok i Did what you said but in the Tool i cant see anything.
Connect state: Disconected
@UltraBackfisch: Near the top of almost every page on XDA it says "Search forum" and "Search thread".....use it.....it's kinda like searching Google.
It's normal for the DFU MultiDL tool to say disconnected. Did you read the instructions? The only point of this tool is to get your device into EDL, then you can use MiFlash or Axon 7 EDL Tool to flash.
Hi internet,
I obviously need help. I accidently bricked my 6T again and it seems to be permenant. I tried to used the MSMdownloadtool but the tool can't detect the device. And the device is in a Qualcomm CrashDump Mode. It shows Attempted to kill init! exit code=0x0000000b do_exit. I got to go but is there a way to fix this.
You must post in Q/A not here
Tapatalké depuis mon OnePlus 6T Havoc OS avec FP !
What were u exactly trying to do while this happened ?
Extreme_Ninja2099 said:
Hi internet,
I obviously need help. I accidently bricked my 6T again and it seems to be permenant. I tried to used the MSMdownloadtool but the tool can't detect the device. And the device is in a Qualcomm CrashDump Mode. It shows Attempted to kill init! exit code=0x0000000b do_exit. I got to go but is there a way to fix this.
Click to expand...
Click to collapse
You can restore you device using fastboot rom. Search for oos 6t fastboot rom.. There are guides for installation.
P.S. It will give a whole bunch of error in the cmd during installation but don't interrupt the process as your device will be restored in the end
Use Mnm tool to fix your phone. It can fix hard brick devices and guidance is there how to use .
PS: this is not right place post next time post on Q/A section.
Hold all the buttons down till it shuts off, almost a full minute. Then get it to boot to fastboot, power off. Then start up msm, then while phone is unplugged and off, hold both vol buttons for a 4 count, then plug it in. Msm will day connected, hit start. Let it finish and reboot. that's all
Qualcomm crashdump is not the same as download mode, and will not work with MSM. You still need to put your device manually into download mode.
parker.stephens said:
Qualcomm crashdump is not the same as download mode, and will not work with MSM. You still need to put your device manually into download mode.
Click to expand...
Click to collapse
Hold down every button till it shuts off, then force reboot to bootloader, then select power off to make sure it's off. Then do as I instructed above to fix it. Sometimes u can just run a fastboot rom to fix it, or boot twrp and flash a rom. I do this multiple times a day sometimes.
fullofhell said:
Hold all the buttons down till it shuts off, almost a full minute. Then get it to boot to fastboot, power off. Then start up msm, then while phone is unplugged and off, hold both vol buttons for a 4 count, then plug it in. Msm will day connected, hit start. Let it finish and reboot. that's all
Click to expand...
Click to collapse
Thanks everyone who replied. The whole thing started when I tried to update my TWRP the wrong way and I got nothing better to do. I was on 3.2.3-1 and the newest on the website (TWRP) was 3.2.3-2, but I flashed the image instead, into vendor. This got me into the Qualcomm CrashDump Mode and it kept on rebooting to it as well. There was no way that I was be able to use the MSMDownload tool to recover my 6T as the tool couldn't detect my device as it was connected as Qualcomm HS-USB Diagnostics 900E not Qualcomm HS-USB QDloader 9008.
I pressed all the buttons and got into FASTBOOT mode! Then I booted TWRP, luckily all my stuff isn't corrupted and I did a Nandroid backup beforehand as well. So, I just restored my Nandroid backup and voila I got my 6T back. Thanks again everyone
Extreme_Ninja2099 said:
Thanks everyone who replied. The whole thing started when I tried to update my TWRP the wrong way and I got nothing better to do. I was on 3.2.3-1 and the newest on the website (TWRP) was 3.2.3-2, but I flashed the image instead, into vendor. This got me into the Qualcomm CrashDump Mode and it kept on rebooting to it as well. There was no way that I was be able to use the MSMDownload tool to recover my 6T as the tool couldn't detect my device as it was connected as Qualcomm HS-USB Diagnostics 900E not Qualcomm HS-USB QDloader 9008.
I pressed all the buttons and got into FASTBOOT mode! Then I booted TWRP, luckily all my stuff isn't corrupted and I did a Nandroid backup beforehand as well. So, I just restored my Nandroid backup and voila I got my 6T back. Thanks again everyone
Click to expand...
Click to collapse
Everybody, it's called the MSMDownload Tool. It cannot be used in Fastboot Mode or Qualcomm CrashDump Mode, it can only be used in EDL Mode (Emergency Download Mode).
I have onplus 6t international i reset my device now its stuck on fastboot mode locked i cant enable oem unlocked in devlopers because my 6t is stuck on fastboot what to do please help
CaptionNixx said:
I have onplus 6t international i reset my device now its stuck on fastboot mode locked i cant enable oem unlocked in devlopers because my 6t is stuck on fastboot what to do please help
Click to expand...
Click to collapse
Power off use msm. Done.
fullofhell said:
Power off use msm. Done.
Click to expand...
Click to collapse
I did that but its shows conected when i press start its work for 5s then its shows N/A in connection area
CaptionNixx said:
I did that but its shows conected when i press start its work for 5s then its shows N/A in connection area
Click to expand...
Click to collapse
If your using windows search for device manager to see what your device is being detected as. Try and reboot if your device isn't Qualcomm HS-USB QDloader 9008. Once it shows that try and update the driver, but you'll need to be a admin. Have you installed Oneplus USB Drivers?
Extreme_Ninja2099 said:
If your using windows search for device manager to see what your device is being detected as. Try and reboot if your device isn't Qualcomm HS-USB QDloader 9008. Once it shows that try and update the driver, but you'll need to be a admin. Have you installed Oneplus USB Drivers?
Click to expand...
Click to collapse
Yes i did that and driver is fully installed Qualcomm HS-USB QDloader 9008 and there is No yallow sigh in driver
Try closing the MSMDownload tool and opening it again. This happened to me when I used MSMDownload Tool and restarting made my device connected
Extreme_Ninja2099 said:
Try closing the MSMDownload tool and opening it again. This happened to me when I used MSMDownload Tool and restarting made my device connected
Click to expand...
Click to collapse
Thanks brother its done
Help I can not get in to fastboot mode. Im stuck in Crashdump mode. Even when i power off the phone holding powerbutton down for a while it will powerup again and the unlocked bootloader warning window with "press power key to pause boot" will not react to any presses.
Also booting and holding down power+down will result in the same and go to crashdump mode.
What do I do
Voldemort13 said:
Help I can not get in to fastboot mode. Im stuck in Crashdump mode. Even when i power off the phone holding powerbutton down for a while it will powerup again and the unlocked bootloader warning window with "press power key to pause boot" will not react to any presses.
Also booting and holding down power+down will result in the same and go to crashdump mode.
What do I do
Click to expand...
Click to collapse
did yoy got any solution