Database Users

Bricked A2017G B03 - help please

Hello!
As title says i bricked my Axon :crying:
I followed http://forum.xda-developers.com/showpost.php?p=68738854&postcount=100 (and the german one that linked to this one) but couldnt do the fastboot unlock.
So i couldnt finish this and my phone required a pin number to start android: bootet and started up but wanted a pin code to start/enter system.
Wasnt able to fix that with googling for answers so i went back to edl mode and rewrote my backup boot/recovery images with axon7backup.
Had no errors with that but it wont start now:
After the ZTE Logo the display goes black but it connects as "handset diagnostic interface (DFU) (ComX)" to my computer.
I fiddled around with driver installing etc and forced the HS-USB QDLoader 9008 on it but no luck, axon7backup/root can not connect.
When i did the actual flashing yesterday it never connected with the hold both vol-keys and connect usb way either, always had to reboot into edl via adb.
I cant boot anything else (no twrp/recovery) it just goes to the diagnostic interface mode.
Thanks in advance

you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....

Starvirus said:
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Click to expand...
Click to collapse
Thanks. I tried it but it wont go to FTM. Only goes to diagnostic com port.
It seems i cant even turn it off. The little red light on the front is on the whole time .

sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.

adb don't show your device?

Starvirus said:
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
Click to expand...
Click to collapse
Oh ok. I expected ftm to work from vol-down and power-button till restart.
@adb: sadly no connection possible since it goes straight to Comport Connection.
Edit:
Couldnt make that work. It was off and i connected the usb. So it showed me the loading battery picture where i cant do anything. held the vol-down the whole time. But as soon as it had some battery it went straight to comport-connection again

im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in

i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(

nsabir said:
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
Click to expand...
Click to collapse
Hi,
couldnt fix it myself so i had to send it in.
Unless some tool/rom was released in the last few months to fix it yourself i would guess your device is bricked.

Hi I have almost the same problem, I tried to unlock bootloader and now I don't have the recovery, I can boot and use my mobile but I can't restore it or update it because I don't have the recovery
I try whit axon7tool to restore the recovery but I got a error.

MaxRink said:
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
Click to expand...
Click to collapse
Hi, do you have any idea, if there will be such a flashtool to work with DFU mode? I'm thinking that there are a lot of guys have bricked their devices (including me).
((

A2017G Bricked D: DFU ONLY

Hi! I have flashed A2017_B13_FULL_EDL with MIFlash and now my A2017 only enter to DFU ZTE Handset Diagnostic Interface(DFU) Can you help me please? D:

Sagformas said:
Hi! I have flashed A2017_B13_FULL_EDL with MIFlash and now my A2017 only enter to DFU ZTE Handset Diagnostic Interface(DFU) Can you help me please? D:
Click to expand...
Click to collapse
Please Help

You say A2017G in the title, but A2017 in your post..
Did you flashed the A2017 B13 file to your A2017G phone?

Keiler90 said:
You say A2017G in the title, but A2017 in your post..
Did you flashed the A2017 B13 file to your A2017G phone?
Click to expand...
Click to collapse
Yes, and the phone the last time boots, but when i have flashed the fastboot unlock...my phone has died

In dfu mode you still can access the EDL mode.
Just type
adb reboot edl

SilentEYE said:
In dfu mode you still can access the EDL mode.
Just type
adb reboot edl
Click to expand...
Click to collapse
My Axon 7 only has a red led and anything more :S if i type adb devices my cmd anwser that i havent a phone connected , the screen neither work, only a red led

ZTE Handset Diagnostic Interface (DFU)

Can u try this
Turn off device
Power in with volume down and power button hold
Release power button after 3 secs
On the A2017G you should see a white box on the screen then. ADB should work

SilentEYE said:
Can u try this
Turn off device
Power in with volume down and power button hold
Release power button after 3 secs
On the A2017G you should see a white box on the screen then. ADB should work
Click to expand...
Click to collapse
I have tried it but it neither work (, only red led and DFU :'(

I have tried the nandL_firefox and i cant flash because i havent a partition file :S and dfu.exe.. neither

ZTE Axon 7 (A2017G) Stucks on ZTE logo

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.

[SOLVED!] Hard Bricked 6T Help Pls

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

Phone stuck on EDL mode and Error firehosecheckrsp failed errno 258

hi, everyone , i m tring to revive my hard bricked oneplus 8 pro but without any luck i m getting "firehosecheckrsp failed errno 258" error , i tried every possible solution a did find (Drivers, Cable, USB 2 , other pc) , i m convinsed tha i shoud start search for a motherboard replacements (even that i coudnt find on the internet)
so please if anyone could help me (Phone stuck on EDL mode - recognised by pc but buttons combination doesn't work )

If you're in edl mode, have you attempted to MSM back to stock?
That's about as low level as you can get, so from a recovery perspective if that doesn't work then nothing will.
Also have you tried holding all the buttons for a long time? Say 30 seconds?
Bare in mind that EDL mode will not remain on for very long, you have to have the MSM tool open and ready for the connection, then with the phone off. Connect it to pc and hold volume up and down, you'll hear the windows ding and it'll say connected on the MSM tool, then and only then click start, flashing should commence and it'll remain locked in EDL until complete.
Lastly you're in warranty so you shouldn't need to buy or replace anything.

dladz said:
If you're in edl mode, have you attempted to MSM back to stock?
That's about as low level as you can get, so from a recovery perspective if that doesn't work then nothing will.
Also have you tried holding all the buttons for a long time? Say 30 seconds?
Bare in mind that EDL mode will not remain on for very long, you have to have the MSM tool open and ready for the connection, then with the phone off. Connect it to pc and hold volume up and down, you'll hear the windows ding and it'll say connected on the MSM tool, then and only then click start, flashing should commence and it'll remain locked in EDL until complete.
Lastly you're in warranty so you shouldn't need to buy or replace anything.
Click to expand...
Click to collapse
Thanks for you're replay , but the phone is always on EDL mode even if i unplug the battery (open phone) when i plug again the phone goes automatically to EDL mode and MSM tool show the phone as connected , but when i try to pass the flash, i got the 258 error

ahmadOnePlus said:
Thanks for you're replay , but the phone is always on EDL mode even if i unplug the battery (open phone) when i plug again the phone goes automatically to EDL mode and MSM tool show the phone as connected , but when i try to pass the flash, i got the 258 error
Click to expand...
Click to collapse
Did you make sure you changed the target device?
Also, what model 8 pro? Are you using correct msm for that model? And it almost sounds like you aren't using correct drivers. Qualcomm USB drivers are needed

jamescable said:
Did you make sure you changed the target device?
Also, what model 8 pro? Are you using correct msm for that model? And it almost sounds like you aren't using correct drivers. Qualcomm USB drivers are needed
Click to expand...
Click to collapse
+1 to this

You need these so the phone is detected correctly in windows. Here is a link.
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com

I have the same problem. I have a 7T but stuck with the same error firehose check rsp failed, errno:258

gcf81 said:
I have the same problem. I have a 7T but stuck with the same error firehose check rsp failed, errno:258
Click to expand...
Click to collapse
Hey, I think you reached out to me on YouTube. Do you know for sure which model of OnePlus 7T you have? There are two common versions in North America HD1907 (T-Mobile) and HD1905 (international unlocked)

Nick-Henkey said:
Hey, I think you reached out to me on YouTube. Do you know for sure which model of OnePlus 7T you have? There are two common versions in North America HD1907 (T-Mobile) and HD1905 (international unlocked)
Click to expand...
Click to collapse
Hey Nick, thanks for responding. It was bought unlocked North America version but then ATT customer support went into the phone while trying to fix something and I think they locked it right before it crashed.

gcf81 said:
Hey Nick, thanks for responding. It was bought unlocked North America version but then ATT customer support went into the phone while trying to fix something and I think they locked it right before it crashed.
Click to expand...
Click to collapse
Looking around, the North America version should be running international firmware (HD1905):
OnePlus 7T hardware variants
I was curious about the different hardware variants of the 7T and decided to ask support once EU launch went over and they kindly answered. HD1900: China HD1901: India HD1903: Europe HD1905: North America HD1907: T-Mobile USA
forum.xda-developers.com
I presume that you're using this MSM tool - https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/
Did you try all of the steps suggested by OP, yet?
Install drivers
Change to factory cable
Different USB port
Different Windows computer?
The only thread I could find where this problem was solved was on the OnePlus forum. The user completely removed and reinstalled the Qualcomm drivers (a different PC should handle that) - https://forums.oneplus.com/threads/solved-closed-trying-to-unbrick-op5t.956810/