Q - EDL Pack & boostack + radio - ZTE Axon 7 Questions & Answers

Hello guys!
quick question today, I have the 2017G and I have flashed the bootstack + radio for LineageOS 14.1
I have reverted back to stock (some call audio issues) through EDL. I flashed the latest B10 EDL.
My question today is: do I still need to flash the bootstack and radio for 2017G B10? Or does the EDL already contain that?
I am asking because I am having some weird bugs with Magisk and unreadable partitions when flashing modules that I did not have before flashing the universal bootstack.
Thanks a lot in advance!

rzarectha said:
Hello guys!
quick question today, I have the 2017G and I have flashed the bootstack + radio for LineageOS 14.1
I have reverted back to stock (some call audio issues) through EDL. I flashed the latest B10 EDL.
My question today is: do I still need to flash the bootstack and radio for 2017G B10? Or does the EDL already contain that?
I am asking because I am having some weird bugs with Magisk and unreadable partitions when flashing modules that I did not have before flashing the universal bootstack.
Thanks a lot in advance!
Click to expand...
Click to collapse
Some EDL have the modem included others don't. Just look into the files and if you see the NON-HLOS.bin it should be OK. Bootstack is included.
Nonetheless, to be sure flash bootstack N-B10 from Download Center. Can do no harm. That includes the right modem
If still having trouble flash universal B15.
Btw, did you wipe data and dalvic before edl flash?
Can do no harm too you know

raystef66 said:
Some EDL have the modem included others don't. Just look into the files and if you see the NON-HLOS.bin it should be OK. Bootstack is included.
Nonetheless, to be sure flash bootstack N-B10 from Download Center. Can do no harm. That includes the right modem
If still having trouble flash universal B15.
Btw, did you wipe data and dalvic before edl flash?
Can do no harm too you know
Click to expand...
Click to collapse
Hello Ray!
I have flashed the proper bootstack from your download center. This is an opportunity to thank you again for creating that. It saves all of us now considering what is going on with ZTE.
I did not wipe dalvic before the EDL pack, I did it now after flashing the bootstack. I hope it's not too late.
I will need to continue using my phone and see if any errors appear since they weren't happening 100% of the time.
Cheers!

Related

Emergency DL Mode TWRP - Nougat, Chinese version - no network fix

Hi,
1. If somebody experience this issue with lack of netwrok after Nougat full Rom update, like:
https://forum.xda-developers.com/showpost.php?p=71063185&postcount=121
than follow this fix from another thread:
https://forum.xda-developers.com/showpost.php?p=71054990&postcount=1456
for me it all seems to work fine now.
2. If somebody has issues with MiFlash, I think it is actually better to do the flash within first 5-10, after that it gives strange errors. If so, restrt EDL and press flash on MiFlash a bit faster .
Regards
I failed to boot nougat using these steps:
Boot to edl.
Flashed using miflash full b15 file and then b15 twrp file.
Flashed in twrp a2017 N modem.
Then it gets stuck at 5 secs screen and phone just reboots back to edl. Am i doing it wrong?
However it boots to nougat if only flashing just the b15 full.
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
RubiCom said:
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
Click to expand...
Click to collapse
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Wuchko said:
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Click to expand...
Click to collapse
Hi,
If you MiFlash B15 Full package it overwrites recovery partition...it is a full package after all. If you want TWRP on your nougat after that you need to Miflsh the B15 TWRP package. However inside the TWRP package, there is also modem driver file which you need to first replace with the new modem file, same as with B15 FULL package.
It is al soooo simple. I had some issues with MiFlash initially, as I read somewhere to "keep the vol up down, power fo 5 sec, release, wait 5seconds and than flash"
However I had near 100% success rate when I did press the flash button around 2-5 seconds after booting into EDL mode. Once you do oem unlock, the process is simple as burning ISO image on a CD
I have it now without that last step. It is unlocked, but without TWRP. I did however MiFlashed TWRP yesterday and it did work fine than as well. I don't however think I need TWRP anymore. I did Dalvik etc. reset during upgrading to Nougat... and that's all I needed it for. Maybe I'm wrong and I will MiFlash it again some day, but honestly, this was first time I flashed any Android phone as I come from Nokia- Windows Phone and all I wanted is working Daydream, Netflix VR for my long business flights. It works now. The rest I might need I will install from play store.
It does have that message about unlocked bootloader when you boot the phone, but it does not bother me and I read somewhere that it is better not to relock he phone.
How do I even know if it's OTA capable? When I checked updates, it says your phone is up to date.
Regards
Ok, now is everything much more clear to me, thank you!
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
otaconremo said:
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
Click to expand...
Click to collapse
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Wuchko said:
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Click to expand...
Click to collapse
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
otaconremo said:
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
Click to expand...
Click to collapse
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Wuchko said:
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Click to expand...
Click to collapse
this is actually wierd. I had this problem my my sims. And I had flashed this many times already trying out different methods including miflash and even stock flashable zips from draken. all yields to the same results.
Do you have any idea where to tweak carrier settings from system files? i tried *#*#4636*#*# but still fails.
Unfortunately I don't know it. I guess I had plenty of luck flashing these ROM's, considering how many people have problems..

NO FINGERPRINT ON FULMICS AFTER OREO on H870

I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Same problem
siggey said:
I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Click to expand...
Click to collapse
Same problem with fingerprint with stock version after update.
I solved fkashing stock oreo zip after a full wipe + data.
siggey said:
I explain my situation:
I was on fulmics 4.2 and everything ok.
Tried a flash oreo without format /data
Bootllop
Ok clean install
Still bottloop
Cleaned everything, installed fulmics + ota
Now all ok except the fingerprint, it is like it does not exist, no option in settings at all.
Does someone have a solution without flashing back a kdz?
Maybe a flashable fingerprint driver?
Click to expand...
Click to collapse
with the oreo update there were also update files for the bootloader, you have to flash official nougat to recover the old version of the bootloader because the new bootloader is not compatible with nougat and created problems like the unrecognized fingerprint reader
Mindy07du44 said:
with the oreo update there were also update files for the bootloader, you have to flash official nougat to recover the old version of the bootloader because the new bootloader is not compatible with nougat and created problems like the unrecognized fingerprint reader
Click to expand...
Click to collapse
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
schoeni11 said:
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
Click to expand...
Click to collapse
yes the kdz or otherwise with the zip is possible but check if the files for the bootloader and in the zip
schoeni11 said:
I have the same problem with lineage 15.1. Flashed Oreo zip to test and now my fingerprint is gone in Lineage. Do you mean flash Nougat kdz to recover old version of the bootloader? or just a nougat zip?
Flashing a Nougat Zip (Open EU)worked for me. No need to flash kdz.
Click to expand...
Click to collapse
When you reinstalled lineage did you wipe anything?
Gobrel said:
When you reinstalled lineage did you wipe anything?
Click to expand...
Click to collapse
did a restore of my nandroid backup.
Please explain step by step
So last year i started learning a bit about roms as stuff like that so after searching i saw Fulmics Rom and i chose that one to flash on my device. On that day i was on Oreo. I did all the stuff (format data, wipe...) then flashed the Rom and it was ok But the fingerprint option was there sometimes and sometimes not... After a day or so it expired so i flashed again (after formatting etc) but no fingerprint. So i just gave up, i was happy that i didnt brick my phone so i just accepted it...But today it's kind of annoying i searched a lot and everyone talks about flashing stock Nougat and then the Rom or flash stock Oreo and then Nougat and then the Rom... Well i tried but with no success.
I hope someone can help me with that
Thank you

OP5 won't accept flashed recoveries

Hello everyone.
I can't flash any recovery via fastboot, I can only flash two recovery files one is the original twrp and second is the original op5 recovery. those cannot install the new ota.
If I try to flash any other recovery file, it enters the qualcomm boot recovery mode, white led and nothing else on phone and a qual 9008 port on pc.
What should I do? My brain kinda melted, so I might forgot to add more infos.
SweetyVolty said:
Hello everyone.
I can't flash any recovery via fastboot, I can only flash two recovery files one is the original twrp and second is the original op5 recovery. those cannot install the new ota.
If I try to flash any other recovery file, it enters the qualcomm boot recovery mode, white led and nothing else on phone and a qual 9008 port on pc.
What should I do? My brain kinda melted, so I might forgot to add more infos.
Click to expand...
Click to collapse
The questions you need to answer:
Is your bootloader unlocked?
Do you have a custom recovery installed?
Is your storage encryped?
What's your actual rom?
What do you want to do(installing ota from android ota menu isn't working for you or why you don't use that method)?
Please give EXACT file names of the files you're trying to flash!
Is your bootloader unlocked? Yes, although I locked then unlocked again for trying.
Do you have a custom recovery installed? yes, I tried both
Is your storage encryped? probably no, I wiped everything but before it wasn't necessary to enter a unlock code or fingerprint etc.
What's your actual rom? It was on oreo, now I don't have a rom lol
What do you want to do(installing ota from android ota menu isn't working for you or why you don't use that method)?
Installing from Ota wasn't successful, sideload does not work, installing custom recoveries result in qualcomm boot (black screen with white led)
only twrp working is this untouched twrp but it has not able to flash the new pie.. https://twrp.me/oneplus/oneplus5.html
twrp from the clockworkmod not able to boot.
My intent is to flash new pie and root. I can't able to flash the pie's original beta recovery too. https://oxygenos.oneplus.net.s3.amazonaws.com/recovery.img
Also I can't mount vendor too I don't know if this causes the problem or not....
SweetyVolty said:
Also I can't mount vendor too I don't know if this causes the problem or not....
Click to expand...
Click to collapse
Ok, so it seems you have an old Oreo stock oos rom before without vendor partition and trying to flash an pie rom and pie recovery, but still on Oreo firmware that's not possible cause newer recoveries need pie firmware which comes along with oos pie roms and you're missing the vendor partition which comes with 5.1.4.
Your starting point is the same as mentioned here https://forum.xda-developers.com/oneplus-5/help/qa-help-thread-newbies-post-t3624656/post79251968
OOS 5.1.4 then you have a vendor partition, then you can install one of those stock Pie oos roms.
You can install oos 5.1.4 with stock recovery or with siankatabg's or with this one
https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
Then you just need to follow the instructions for the stock oos or beta rom.
If you have any concerns or further questions, please feel free to ask here

Fastboot flashable version of EUI ROM 14s for those with splitscreen issues

Heyyo, For those who had to QFIL and their x2 now is stuck with split screen and if you can't navigate TWRP? Try this out
Please NOTE! This WILL wipe your userdata! You've been warned!
https://mega.nz/file/zqx0WK4K#HiR0Iv44ZFN75VJ4ydg-bxAWoBC6uM7gk-NhbZpXNAE
Make sure your x2 is in fastboot mode and USB is plugged into your PC.
If you're using Windows? Please run the fash-all.bat
If you're using Linux? Please run the flash-all.sh from terminal.
After you're done with this? I would recommend switching to EUI ROM 30s or something and then format data and switch to a custom ROM.
Good luck!
Hello. Thank you for upload fastboot flashable EUI Rom. I installed it successfully. I had split screen issue with Qfil flashable rom.
Unfortunately split screen issue is not solved. Please let me know what point I have to check. My lemax2 original version is LeEco LEX821. (LeMax2_WW)
6G memory and 64G storage version.
Heyyo @JPsato254 , dang that's unfortunate that it didn't work for you hmm... Well? The next thing to try would be the official stock EUI ROM 14s and see if that works. I would recommend using TWRP 3.1.0-0 for this as newer TWRP versions might not want to flash EUI ROM 14s. http://g3.letv.cn/186/36/69/letv-hdtv/0/upload/tmp/20160603113824161/LE_X2_X820-CN-FN-FEXCNFN5601405314S-5.6.014S.zip?b=123456&platid=5&splatid=500
Heyyo @JPsato254 , dang that's unfortunate that it didn't work for you hmm... Well? The next thing to try would be the official stock EUI ROM 14s and see if that works. I would recommend using TWRP 3.1.0-0 for this as newer TWRP versions might not want to flash EUI ROM 14s. http://g3.letv.cn/186/36/69/letv-hdtv/0/upload/tmp/20160603113824161/LE_X2_X820-CN-FN-FEXCNFN5601405314S-5.6.014S.zip?b=123456&platid=5&splatid=500
I may be late to the party, but even after flashing to 14s version I still have the same problem. It's a firmware related problem (not ROM, firmware, like the NON-HLOS.bin file).
EDIT: Flashed 21s Indian ROM, works now.

Axon 7 Can access TWRP but cannot get into bootloader menu

So my current phone recently broke. So I decided to dust of my old Axon 7 which was still using Android 6.0.1. A bit old for these days since a lot of apps won't work. The best thing I could think of was to install a different rom. After a lot of work I finally managed to unlock the bootloader and install TWRP. Then I tried to flash a rom but to no avail. I have tried many things and now I can access only TWRP and EDL through ADB. I cannot access the Bootloader menu anymore. Does anyone know what to do next? How can I fix this and try to flash something again?
Edit: Forgot to mention that I currently have the most recent version of TWRP installed. And the flashing error I get is Error 7, Googled that and tried every "fix" but none of them worked. Another strange thing is that my phone used to be A2017G, but now when I connect it to my pc it shows up as A2017U, Is this a driver issue or did I change something unintended?
You can also boot to EDL from TWRP in terminal (reboot edl) and dfu/edl mode by pressing vol up+vol down and power button.
If your phone boot in dfu mode, use EDL Tool by djkuz.
Don't worry if it show up as A2017U - you won't lose any bands.
You didn't wrote much so I won't help.
Axon 7 scene is a little messed up. I'm getting lost in it myself. We've probably got 3 or 4 different twrp recoveries for different roms.
- official twrp from twrp.me website, compiled with marshmallow zte kernel for ailsa_ii - for stock roms, up to nougat.
- unofficial for ailsa_ii - for custom roms, up to nougat
Then, I don't know when, but device codename was changed from ailsa_ii to axon7.
- unofficial nfound/oki lab compiled with oreo zte kernel for axon7 - for oreo stock roms
- unofficial oki lab/twrp 3.2.3 for axon7 - for oreo/pie custom roms
Don't use twrp for oreo/pie roms on nougat bootstack.
There are two 3.2.3 twrp recoveries. One with vendor support, which isn't available anymore in LOS 16.0 thread, I attached it.
Other one without vendor support - from LOS 15.1 thread.
It doesn't change much. You will just gain an option to mount vendor partition in twrp.
Oki lab twrp for custom roms has a party tool for creating vendor partiton.
You can also use Party v0.5 script, to create vendor partition in twrp 3.2.3.
512MB vendor - for LOS and most custom roms
800MB vendor - for some old custom roms made by nfound
klałn said:
You can also boot to EDL from TWRP in terminal (reboot edl) and dfu/edl mode by pressing vol up+vol down and power button.
If your phone boot in dfu mode, use EDL Tool by djkuz.
Don't worry if it show up as A2017U - you won't lose any bands.
You didn't wrote much so I won't help.
Axon 7 scene is a little messed up. I'm getting lost in it myself. We've probably got 3 or 4 different twrp recoveries for different roms.
- official twrp from twrp.me website, compiled with marshmallow zte kernel for ailsa_ii - for stock roms, up to nougat.
- unofficial for ailsa_ii - for custom roms, up to nougat
Then, I don't know when, but device codename was changed from ailsa_ii to axon7.
- unofficial nfound/oki lab compiled with oreo zte kernel for axon7 - for oreo stock roms
- unofficial oki lab/twrp 3.2.3 for axon7 - for oreo/pie custom roms
Don't use twrp for oreo/pie roms on nougat bootstack.
There are two 3.2.3 twrp recoveries. One with vendor support, which isn't available anymore in LOS 16.0 thread, I attached it.
Other one without vendor support - from LOS 15.1 thread.
It doesn't change much. You will just gain an option to mount vendor partition in twrp.
Oki lab twrp for custom roms has a party tool for creating vendor partiton.
You can also use Party v0.5 script, to create vendor partition in twrp 3.2.3.
512MB vendor - for LOS and most custom roms
800MB vendor - for some old custom roms made by nfound
Click to expand...
Click to collapse
Thanks for the reply! I was a bit ahead of you and managed to create a vendor partition using the Party v0.5 script, now I can flash ROMs just fine but the system won't boot (blinking red light, black screen)
I am using the most recent TWRP version for Axon 7 (3.5.2_9-0), I am not sure if this is part of the problem
I've found some possible fixes related to my original question for getting into the bootloader menu, but I have no idea on what to change to regain access to it. I do remember that it said the device name was ailsa_ii as you mentioned, and that the bootloader version was not specified (it was just blank)
Edit: never mind the bootloader menu issue, I managed to get back into it. But the system still won't load.
On which bootstack you are right now?
Which rom you want to try?
Custom roms won't work on stock bootstacks.
First, I would recommend to backup persist/efs partition, before futher changes.
Second, I would recommend upgrade stock marshmallow to nougat, then nougat to oreo and after that, flash universal v2 oreo bootstack.
Bootloader/fastboot was locked by zte on most stock roms.
For what for you need fastboot mode? EDL mode isn't enough?
If you really need fastboot, you may try this aboot on oreo bootstack. Didn't try it with universal v2.
I have no idea what bootstack I am on right now to be honest. How can I check this?
I want to install LineageOS 17.1.
The bootloader is unlocked, I am sure of that.
Sorry for my ignorance, I know I am in way over my head but I am dedicated to make this work.
So you probably on stock marshmallow bootstack.
I still recommend to upgrade system step by step. From 6.0.1 to 7.0, then to 8.0 B02 and applying A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip.
Why this way? Most of a7 users did that at beginning and official updates may do some changes to persist partition.
Some people complained about 50% battery bug, which came out of nowhere.
If you want take a risk, you can flash DrakenFX bootstack straight away or flash A2017G_B02_OREO_FULL_EDL in edl mode and then DrakenFX bootstack. At least - please - do efs partition backup using EDL Tool by djkuz, before doing such a jump.
I don't know if this gonna work. If you brick your device, you will have to download full edl packages, which may take even more time, than official way to upgrade.
Well, that didn't work. Guess it is bricked now because I cannot access recovery anymore, and my pc can no longer find it. Thanks for your help but I think it is time to buy a new one.
DNYO31 said:
Well, that didn't work. Guess it is bricked now because I cannot access recovery anymore, and my pc can no longer find it. Thanks for your help but I think it is time to buy a new one.
Click to expand...
Click to collapse
Have you tried booting phone to edl mode by holding vol-up + vol-down and pressing power button?
ZTE logo might not appear, but you should enter to dfu/edl mode by pressing those buttons.
It's really hard to make a brick of Axon 7.
In 2016-2017, I had to ground test points on the motherboard to leave DFU mode, but it's not necessary anymore.

Categories

Resources