Database Users

Semi Brick

I tried to go from 7.0 to 7.1.1. I had root, unlocked bootloader and twrp. I somehow managed to hose everything and now when I try to turn on the phone I get the AXON screen and it stays there.
If I try to "power and up" it blanks out and at least shows up as com 5 in the com list.
Tenfar's tool goes through the motions but no change, Tenear's tool doesnt see the device.
Am I hosed or is there someway I can unscrew this up.

I'm right there with you. Literally did the exact same thing. I'm stuck in DFU mode on my 2017U.

UnsecWifi said:
I tried to go from 7.0 to 7.1.1. I had root, unlocked bootloader and twrp. I somehow managed to hose everything and now when I try to turn on the phone I get the AXON screen and it stays there.
If I try to "power and up" it blanks out and at least shows up as com 5 in the com list.
Tenfar's tool goes through the motions but no change, Tenear's tool doesnt see the device.
Am I hosed or is there someway I can unscrew this up.
Click to expand...
Click to collapse
Use this thead https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
And remember NOT USE ZADIG DRIVER FOR MIFLASH, use the driver from the thead.
Tell me if it work

"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.

UnsecWifi said:
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
Click to expand...
Click to collapse
use another computer have windows 7 32 bit(try use windows 10 32 bit)

UnsecWifi said:
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
Click to expand...
Click to collapse
If it sees it you should be alright, just close the MiFlash, or even better reboot your computer. Then try to reset ur axon by holding power button and then when it fails enter EDL again using the combo.
The MiFlash works best on a freshly booted EDL where u did not attempt and fail to flash stuff before. So always reboot the EDL fresh before using the tool.

I went back and forth between my laptop(win10) and my desktop(win7) and never could get anything to work through MiFlash. Then all of a sudden it worked (I have no idea why). I wound up flashing the B15 new_full.
After it finished it did nothing. No splash screen nothing. Only flashing led. I plugged it back in and the battery was dead. I charged it up and it worked!!!!:victory::laugh::victory: Awesome. Thanks to everyone.

UnsecWifi said:
I went back and forth between my laptop(win10) and my desktop(win7) and never could get anything to work through MiFlash. Then all of a sudden it worked (I have no idea why). I wound up flashing the B15 new_full.
After it finished it did nothing. No splash screen nothing. Only flashing led. I plugged it back in and the battery was dead. I charged it up and it worked!!!!:victory:[emoji23]:victory: Awesome. Thanks to everyone.
Click to expand...
Click to collapse
Did it work on win 10 or 7?
Also what drivers did you have installed? I'm afraid mine is a lost cause

Did it on my desktop with Win7. Used qualcom bulk drivers. And the only file to work for me was B15-NEW_FULL (Nougat). Unpack it and select the A2017U_B15-New_twrp_edl folder, refresh so you see your COM port and flash it.
If it doesnt work try going back into EDL mode, closing and reopening the MiFlash utility, switch USB ports etc. And use the cable that came with your phone. Make sure to charge it first with the original charger.

A2017G Hard Brick - no recovery, only DFU

I think I fucced up pretty badly this time...
I was on LOS, wanted to get back to stock, for some reason wiped and rebooted...
Infamous DFU mode. I can't get to FTM (tried power + vol down and it only turns on, scrolls a little and turns off), and I wasn't able to use axon7tool using zadig. No recovery at all, no fastboot, nothing...
I've installed QDLoader 9008 drivers and MiFlash actually recognizes the... thing. Can anyone tell me if this is worth trying/what I have to do? Thanks
P.S I have no way of returning it to ZTE
Edit: The miflash thing didn't work as expected, can't find programmer file

Look like you kill yourseft this time.
You have to enter EDL with any cost, or at less FTM - let batttery drain up and try again.
Otherwise, people say somethings about a DIY EDL cable, but I not really sure

tamahouse02 said:
Look like you kill yourseft this time.
You have to enter EDL with any cost, or at less FTM - let batttery drain up and try again.
Otherwise, people say somethings about a DIY EDL cable, but I not really sure
Click to expand...
Click to collapse
I've found this QPST thing from Qualcomm, also heard that the only thing missing is the programmer which is not released. It detects my device, reports it is a Sahara Memory Dump, and that's pretty much that. I hope that people is actually looking into this
Also I noticd that in the first seconds when it is seemingly installing, it says it is a Sahara Download. Does that help?

I also wanted to know, is there a main thread for this sort of thing? I've seen @tenfar 's thread but there is nothing to do on A2017G's

https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
I know you're already active in this thread, but I don't know if you understand it in depth. You must open your device to enter into edl mode. In edl you can flash twrp and are back in business. So your only way to enter edl is to open your brick as described.

Thank you, however i wanna be extra cautious here. When I have to connect the test point to ground, do I connect it with the SIM slot? What is valid as ground?

If MiFlash recognizes it you should be able to flash a stock Rom. The I have the A2017U so I could be wrong

supergear said:
If MiFlash recognizes it you should be able to flash a stock Rom. The I have the A2017U so I could be wrong
Click to expand...
Click to collapse
It's all done, thank you though. I disassembled the whole thing and did the short to ground thing, and after literally 30 tries it flashed the damn thing

[SOLVED] A2017G Hard brick, Unauthroized ADB and DFU Only.

Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.

Ouh....DFU? I think this thing is totally bricked.

I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?

Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !

raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.

Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.

stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!

Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....

stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!

Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable

Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!

Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...

twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.

Phone Completely Dead Black Screen

I don't know what has happened... I took the phone off my charger at about 80%, was playing on it for a little bit and then restarted the phone.... the next moment I look at it, it is just a black screen. It is completely dead, pushing or holding power button does nothing (held for minutes multiple times), holding volume buttons & power button does nothing, plugging in to charger does nothing. It seems to be completely dead.
I have no idea why, it was working fine until I selected restart and was dead a few minutes later. Completely normal usage prior to that.
Anyone have any suggestions for what I can do to get this phone turned back on at all??
Nubia Z17 NX563J
Kind of a pain that these are completely sealed units...

I've just seen some posts about the Nubia Emergency Tool. If I plug my phone into the PC it does show up as "Qualcomm HS-USB QDLoader 9008" device so it looks like the emergency tool might work with it.
But does that mean it will flash my phone and I will lose all data on it?
There was nothing wrong with it just before, is there no other way to recover the data?

bunta126 said:
I've just seen some posts about the Nubia Emergency Tool. If I plug my phone into the PC it does show up as "Qualcomm HS-USB QDLoader 9008" device so it looks like the emergency tool might work with it.
But does that mean it will flash my phone and I will lose all data on it?
There was nothing wrong with it just before, is there no other way to recover the data?
Click to expand...
Click to collapse
How long have you used your phone? Better to replace the battery as one of my phones behaves the same way. Just replace the battery and that's it.

Tims Fong said:
How long have you used your phone? Better to replace the battery as one of my phones behaves the same way. Just replace the battery and that's it.
Click to expand...
Click to collapse
But the battery is not replaceable...?

bunta126 said:
But the battery is not replaceable...?
Click to expand...
Click to collapse
[NX563J][Project Treble][Android 10-11-12-13][GSI][AB]
Whats about magisk it Boot no more gsi after Flash magisk use this:https://github.com/ExpressLuke/phh-magisk-builder/releases/download/08-12-2020/magisk-v21.1-phh.zip
forum.xda-developers.com

bunta126 said:
But the battery is not replaceable...?
Click to expand...
Click to collapse
you need special usb cable i got same problem long time before
for edl mode

Update: I managed to get the bootloader and recovery working using the Nubia Emergency Tool. The system would not boot and even a dirty flash of the same ROM I was using would not make it boot. I could reinstall the ROM however and the phone is now working fine again.

So, I rebuilt my phone with a completely different ROM on Android 13, and today the same thing has happened: I chose to restart my phone and it has gone black and won't turn back on again.
It has been running perfectly fine on the new ROM until today, why would this same problem reoccur? I suppose battery is likeliest issue... although maybe there is something I'm doing to break the system?

Redmi 7A Dead, No display, no fastboot, no recovery

I have some previous threads on my Redmi 7A dead... but no one responded, some did but said I can't fix it, buy a new phone. I am not in a financial condition to buy a new phone. All I can do is fix this phone and continue using it till I get a new phone. But since 3 weeks I am not able to use my Redmi 7A. I was hopeless that this phone could be repaired or could be used again but I went through a few videos on YouTube and saw a ray of hope but still I was helpless I tried booting it into EDL mode using the test point method but nothing worked out. Please I NEED HELP to fix this phone. I have a brief description below of the timeline about how it
crashed, how it was in the service center, what happened after it.
Alright so,
At March 13, It was on AOD (I know it is not supported keep reading), running nusantra os latest version for (Mi-439 aka Redmi 7A, 8) which was last updated on Dec 4, 2022. So when It was on AOD I tried to unlock the phone and it froze. So I rebooted it abnormally. After it was booting it stuck on the Redmi logo but it wasn't going ahead, not showing the boot animation. So I tried to boot it in recovery mode, when it was booting in recovery mode the phone was just shutting down and trying to reboot itself again but it couldn't. So I tried to wipe everything using fastboot commands and the command which I used was -w. So after that instead of waiting at the redmi logo it was stuck in a bootloop, in fact booting in the bootloader (fastboot mode). So after that I lost hope and gave it to the nearby service center. Please note that the phone was turning on before giving it to the service center. After like one day I went there to check if it was done, they say that it's a hardware problem, they are not able to fix it, When I came home the phone didn't boot neither in the fastboot mode nor It was turning on. So I thought it's not charged so I charged it for 1.5 hours but still there was no sign of life. I asked them about the phone not turning on they told me that it's a hardware issue and hung up the phone, said I am in a hurry I will call you later. Till this day I received no call. So Now I am posting this because I see some hope of EDL mode. I even tried to boot it in the EDL mode but still it was neither booting in the EDL mode nor my computer is detecting my phone (I have all the drivers installed). Please help ASAP.

Gibbron1 said:
there was no sign of life
Click to expand...
Click to collapse
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's

mYXiao said:
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's
Click to expand...
Click to collapse
I bought another phone, but thanks for the reply and help you gave me. My new Phone is Mi A1.