Database Users

fastboot flashable boot.img

Hi !
I might have erased the boot partion. I still got the unlocked bootloader screen, and can still get in fastboot, but that's it. I can't boot in TWRP. I've tried to flash the boot.img from the stock zip, but it doesn't work... anyway to fix this ? It's the A2017G model. All i need is to get into TWRP.

Exnocte said:
Hi !
I might have erased the boot partion. I still got the unlocked bootloader screen, and can still get in fastboot, but that's it. I can't boot in TWRP. I've tried to flash the boot.img from the stock zip, but it doesn't work... anyway to fix this ? It's the A2017G model. All i need is to get into TWRP.
Click to expand...
Click to collapse
can't you flash recovery? I think someone made a flashable TWRP somewhere

Choose an username... said:
can't you flash recovery? I think someone made a flashable TWRP somewhere
Click to expand...
Click to collapse
I've tried to flash TWRP several time, but it won't boot...

Exnocte said:
I've tried to flash TWRP several time, but it won't boot...
Click to expand...
Click to collapse
you can try getting into EDL and using MiFlash to flash one of the zips on the Russian page 4pda. Go to the debrick page (the one with the phone carnage pictures inside), find the links for the chinese full recovery package. it will get you to the 4pda page. from there find a package that suits your needs (there is one with aboot and fbop) and flaah with MiFlash
Otherwise download the full B10 recovery package and flash it with MiFlash. you won't lose data but it might conflict if you were on Nougat

I'm in this situation for some days...
No EDL, No recovery, only fastboot and FTU modes are accessible.
And we can't flash via Miflash. It sees the phone only in fastboot mode, and can't flash it.
 @op : 2 ways to recover :
- Test points method to force EDL and flash via miflash
- Return to ZTE
If any1 has other solutions ...
FYI : My tests so far :
- Flash boot / reboot / flash recovery : Stuck on ZTE logo, red led on permanently
- Hot load recovery (fastboot boot twrp.img): Command unknown
- Format userdata/cache : No work
- Flash via Miflash in fastboot : "Can't find Eraseall except Data.bat"
- Change drivers by some others one : No luck

Sn8K said:
I'm in this situation for some days...
No EDL, No recovery, only fastboot and FTU modes are accessible.
And we can't flash via Miflash. It sees the phone only in fastboot mode, and can't flash it.
@op : 2 ways to recover :
- Test points method to force EDL and flash via miflash
- Return to ZTE
If any1 has other solutions ...
FYI : My tests so far :
- Flash boot / reboot / flash recovery : Stuck on ZTE logo, red led on permanently
- Hot load recovery (fastboot boot twrp.img): Command unknown
- Format userdata/cache : No work
- Flash via Miflash in fastboot : "Can't find Eraseall except Data.bat"
- Change drivers by some others one : No luck
Click to expand...
Click to collapse
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.

tron1 said:
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.
Click to expand...
Click to collapse
Humm ... Early morning for me ... i meant DFU. Vol+ & - while powering the phone Result on a black screen, and driver is recognized as Handset Diagnostic Driver (DFU COm port x)
Ind in that kind of brick, FTM is not accessible either.

tron1 said:
I don't know what you mean with FTU mode, but if FTM is meant you should be able to send a "reboot edl" command to activate the EDL mode.
Click to expand...
Click to collapse
Yeah that pretty much sums it up. If you get ZTE handset diagnostic driver on Ports COM&LPT you'll have to take your device apart and use the test point. If it is recognized as Qualcomm HS-USB QDLoader 9008 it means that you're on EDL. I'd reccomend trying to use miflash like i described, if it doesn't work return it or take it apart

Maybe a bit late for a reply, but I was able to get out of a similar situation (from DFU) by holding power and volume down for a long time. That got me to FTM and then I could reboot into edl via "adb reboot edl". Then I used the Axon7toolkit to flash fastboot and from there I could get to twrp and back in business. Any questions, let me know.

@Piet : How long for the PWR+DWN ? I've tried for something like 40/45 seconds, without success.

Sn8K said:
@Piet : How long for the PWR+DWN ? I've tried for something like 40/45 seconds, without success.
Click to expand...
Click to collapse
From what I read you have to let the device discharge totally, then you can get ftm. I had my battery fully charged when i bricked so i just did the 4th categ unbricking process

your device is corrupted and cannot be trusted and may not work properly

Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command

amus76 said:
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
Click to expand...
Click to collapse
All right, do this:
-Put the phone in Fastboot
-Open command prompt
-Run "fastboot erase userdata"
If it doesn't work, do this:
-Set up a TWRP on your fastboot folder (rename it to "recovery.img" [BE SURE THAT YOUR PC SHOWS FILE NAME EXTENSIONS] and put it on the folder where fastboot is located)
-Open command prompt in the folder where Fastboot is located
-Run this command:
fastboot boot recovery.img
Your phone should enter TWRP. It's not installed, it just boots it once.
Then try to format data from TWRP. Right after that, use "adb push recovery.img /sdcard" to push the recovery img to your internal storage. Then go (on your twrp) to "Install" - hit "Install image", then select the recovery.img, and select "recovery" and swipe to confirm.
After it is done, install LOS again. If it is 15.1 or 16 you have to have a Vendor compatible TWRP, such as Ordenkrieger's TWRP (From LOS16 thread). Follow the instructions precisely

As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?

amus76 said:
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
Click to expand...
Click to collapse
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done

If you still have access the fastboot
Enter, reboot dm-verity enforcing
Check here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214

Choose an username... said:
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
Click to expand...
Click to collapse
I did the fastboot boot recovery.img the phone reboot, i get the warning screen for unlocked bootloader and straight after "your device is corrupted and cannot be trusted and may not work properly" with the same style as the bootloader warninr screen.
So without a recovery I can't flash fastboot images

For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.

Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?

Syberclone said:
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Click to expand...
Click to collapse
I didn't get access to EDL mode even through ADB, nor FTM screen. So MiFlash is useless
With Axon 7 tool, I tried to flash TWRP with no success, my phone was on DFU
Then I managed to dm-verity encrypted through ADB but the phone was not rebooting on recovery, still fastboot but the phone was not recognize by the PC
I have Qualcomm Drivers installed
Right now with Lineage, I can't acces FTM screen
I just pushed the button twice when I was with the red warninr screen and get access to TWRP (or Lineage boot screen)

Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted

Syberclone said:
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Click to expand...
Click to collapse
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time

amus76 said:
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
Click to expand...
Click to collapse
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.

Syberclone said:
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Click to expand...
Click to collapse
Just with "dm-verity enforcing" with ADB
Then: press button power when on the red warning, a pinguin will appear and again press the power button, it will reboot on TWRP or Lineage
My fasbtoot was inefficient a part for the dm-verity enforcing, no FTM also

amus76 said:
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Click to expand...
Click to collapse
I know this is an old reply, but I arrive from a google search. Sir, thanks a lot for this reply. I was stuck in your same situation and pressing the power button with the linux icon allowed me to go to TWRP. THANKS!

I get the pinguin, but if i press Power again, nothing happened. I have to wait for a while it reboots to System. I tried to hold Power while it is rebooting, but it always reboots to System. No chance to enter twrp...

[Q] Restore EDL Functionality on an A2017G after flashing Universal Oreo BootStack

Hi @ all
I switched to the latest official LineagOS 15.1 and everything works like a charm.
I realized that the Button Combo for EDL does no long work as already mentioned in the LineageOS thread. No problem so far since I can reboot to EDL via adb.
However, I would really like to restore this functionality.
For what I know the code for the EDL mode is inside the Application Bootloader (aboot). This would mean that emmc_appsboot.bin is responsible to provide this functionality. What I am unsure of is if the button combination to enter the EDL mode is also part of this partition.
aboot is also responsible to properly address fastboot mode which I managed to get working on STOCK Nougat A2017GV1.2.0B02 by flashing emmc_appsboot.bin of A2017GV1.2.0B01 besides the missing fastboot.img.
My guess is that the button combination is not part of aboot since I have tried several things to re-enable the button combination:
Extracted @Oki's files from his Full LineageOS EDL Package - Result: no EDL, password valid but
Flash @NFound's Universal BootStack as suggested here by @bornlivedie - Result: no EDL, password no longer valid after reboot
Flashed A2017GV1.2.0B01 emmc_appsboot.bin - Result: No EDL, password valid but the drawer seems to be crashing and I was instantly on the lockscreen again...
Flashed a couple of other BootStacks by @DrakenFX - Result: No EDL
Flashed @Oki's emmc_appsboot.bin on top of @DrakenFX's BootStack which I originally used - Result: no EDL, password no longer valid after reboot
So it seems that when you flash a BootStack and after that LineageOS it is somehow dependent on which BootStack you used and you cannot switch between them, at least on A2017G.
However, this is not the problem since I'd like to re-enable the button combination to enter EDL from a powered-off Axon 7.
It is not about the EDL cable. I know that this would also be a possibility and it is definitely not about the two contact points on the MB.
Does any one, maybe also @Unjustified Dev or @OrdenKrieger, have an idea on what exactly goes wrong here and might shed some light into this issue?
Thanks!

Can you enter FTM?
If so try using Djkuz Edl tool
I have a guide to restore Edl button combo
(Works on Beta Oreo, in not sure about Los or the bootstacks)
My Guide is here
https://forum.xda-developers.com/axon-7/how-to/guide-edl-mode-locked-t3848518

Syberclone said:
Can you enter FTM?
If so try using Djkuz Edl tool
I have a guide to restore Edl button combo
(Works on Beta Oreo, in not sure about Los or the bootstacks)
My Guide is here
https://forum.xda-developers.com/axon-7/how-to/guide-edl-mode-locked-t3848518
Click to expand...
Click to collapse
Thanks for your reply, I stumbled upon your thread before I guess but wasn't sure if this is gonna help me.
Unfortunately, I am not able to get into FTM...
However, I am able to boot into EDL mode, so do you think the EDL fix will also work if I am in EDL mode?
*EDIT*
I tried it and it worked!
Thank you so much for your input!

sToRm1nG said:
Thanks for your reply, I stumbled upon your thread before I guess but wasn't sure if this is gonna help me.
Unfortunately, I am not able to get into FTM...
However, I am able to boot into EDL mode, so do you think the EDL fix will also work if I am in EDL mode?
*EDIT*
I tried it and it worked!
Thank you so much for your input!
Click to expand...
Click to collapse
Awesome, I'm glad it did

I recently had a similar issue with my A2017U after getting a refurb back from ZTE as a result of RMA. The device they sent works perfectly fine and was running B35. But I couldn't get into EDL via the buttons, had to use ADB. Luckily the ROM was still booting.
Long story short, after flashing @djkuz's B12 Oreo EDL, the ability to access EDL via the hardware buttons returned as if by magic. I have since been able to EDL between B19, B32, B12, etc and the buttons to get into EDL still work. Now, I know you can't flash a U EDL on a G, I'm guessing you will brick. But maybe there is an equivalent Oreo EDL for the G that might do the same for you.
Just a suggestion.....

A2017G revert to stock questions

Good afternoon
I have an A2017G with a mod rom android Pie installed on it and with TWRP 3.2.3-0L v1.3
I'd like to revert it to stock in order to sell it.
I can't access to EDL mode with the keys combo, nor with "reboot edl" in a terminal on the phone, nor with "adb reboot download" on my ubuntu machine.
I can access the system (the rom) fine and also TWRP.
Any advice to fix that, any file to flash from TWRP, without screwing up vendor partition, imei, or whatever?
Thanks.

in twrp for zte there is an option to reboot to EDL

Voenix said:
in twrp for zte there is an option to reboot to EDL
Click to expand...
Click to collapse
Well, it just powers off...

chironfr said:
Well, it just powers off...
Click to expand...
Click to collapse
EDL mode has only black screen,
Maybe its online check Qcom bulk or some qualcomm 9008 port in device manager (if its on black screen)

Thanks.
I have sorted it out after digging deeply
Main thing to understand: it's not possible to relock it with nougat oreo or pie installed on it.
So I have:
- Copied all my stuff (pics, vids, books, etc...) to my computer
- Set up a clean W10 on a dedicated machine, without any antivirus crap, installed original qualcomm drivers, ADB toolkit and axon 7 EDL tool on it.
- backed up all partitions with Axon 7 EDL Tool
- from TWRP wiped system, data, storage.
- downgraded to the official original rom (Marshmallow) available on the page EDL
- flashed TWRP on the phone
- installed TWRP_UnlockBootloaderPackage_by_DrakenFX.zip with TWRP
- rebooted to fastboot, then I could finally type from ADB "fastboot oem lock", and that's it!
- The phone rebooted properly, asked me for the country, but since I want to sell it, I didn't go any further.

chironfr said:
Thanks.
...
Main thing to understand: it's not possible to relock it with nougat oreo or pie installed on it.
...
Click to expand...
Click to collapse
In fact, as mentioned by Axon 7 EDL toolkit's author in this post https://forum.xda-developers.com/showpost.php?p=78267172&postcount=200
at least with Marshmallow and Nougat (supported by the toolkit), you can first enable fastboot (unlock fastboot) with the toolkit on stock Marshmallow or Nougat, then use "fastboot oem lock" to lock bootloader in bootloader (fastboot) mode.
Remember to use stock ROM (either by flashing with FULL_EDL package, or by using stock recovery applying to official ZTE update.zip, otherwise the phone would be bricked. User data will be erased (equivalent to factory reset).

a2017g downgrading from oreo to naugat then to marshmallow (want unloack bootloader)

Hey guys My phone is " zte axon 7 a 2017 g" version oreo , b03: i want to downgrading from oreo to naugat then downgrading from naugat to marshmallow (want to unloack bootloader ) can i downgrading two times without no problem with locked bootloader

Can you please not spam on every single Axon 7 thread.
The instructions to downgrade to Nougat are simple, and do-able via the EDL Tool.
It's not possible to use the EDL Tool on Linux, so I'd recommend finding a Windows machine.
•Download the tool, and extract to the root of your C:\ drive as instructed in the thread
•Download the B12_Nougat_A2017G_FullEDL package from the EDL Tool thread, and extract all the files to the flash/full folder of the tool
• On your device, enable USB Debugging and OEM Unlocking from the developer settings
• Connect your device, and open the tool. It will prompt you and then automatically reboot the phone into EDL mode.
• Select 'Flash' and then 'Full' and wait for the flashing to finish.
• It will prompt to reboot your phone, after which you'll find it is now running Nougat.
From there, you can go back to Settings and enable USB Debugging and OEM Unlocking from the developer settings once more, and reconnect your device and open the tool. This time, select 'Unlock' and 'unlock bootloader'.
Once the bootloader is unlocked, follow the instructions in the LineageOS 16 thread, and flash the latest version of twrp (can also be done via the tool), universal bootstack, modem, and finally ROM/GApps/Magisk as needed.

runninghamster said:
Can you please not spam on every single Axon 7 thread.
The instructions to downgrade to Nougat are simple, and do-able via the EDL Tool.
It's not possible to use the EDL Tool on Linux, so I'd recommend finding a Windows machine.
•Download the tool, and extract to the root of your C:\ drive as instructed in the thread
•Download the B12_Nougat_A2017G_FullEDL package from the EDL Tool thread, and extract all the files to the flash/full folder of the tool
• On your device, enable USB Debugging and OEM Unlocking from the developer settings
• Connect your device, and open the tool. It will prompt you and then automatically reboot the phone into EDL mode.
• Select 'Flash' and then 'Full' and wait for the flashing to finish.
• It will prompt to reboot your phone, after which you'll find it is now running Nougat.
From there, you can go back to Settings and enable USB Debugging and OEM Unlocking from the developer settings once more, and reconnect your device and open the tool. This time, select 'Unlock' and 'unlock bootloader'.
Once the bootloader is unlocked, follow the instructions in the LineageOS 16 thread, and flash the latest version of twrp (can also be done via the tool), universal bootstack, modem, and finally ROM/GApps/Magisk as needed.
Click to expand...
Click to collapse
thanks for your reply i was waiting for this response ; but i will ask something after unloack bootloader throw windows can i flash the twrp and the the lineage os using linux and if u can tell me please some things should'nt do it like stuck on edl mode that's why am afraid to brick up my phone !

afef said:
thanks for your reply i was waiting for this response ; but i will ask something after unloack bootloader throw windows can i flash the twrp and the the lineage os using linux and if u can tell me please some things should'nt do it like stuck on edl mode that's why am afraid to brick up my phone !
Click to expand...
Click to collapse
You need to flash TWRP initially with the EDL Tool aswell. LineageOS / other ROM additions such as GApps and Magisk are flashed via TWRP, which is the recovery on the device and doesn't require a computer.
The phone shouldn't get stuck on EDL mode, but if it does - no need to worry. You can just let the battery drain which can take a few hours and then plug your phone back into your computer and try the tool again.

runninghamster said:
You need to flash TWRP initially with the EDL Tool aswell. LineageOS / other ROM additions such as GApps and Magisk are flashed via TWRP, which is the recovery on the device and doesn't require a computer.
The phone shouldn't get stuck on EDL mode, but if it does - no need to worry. You can just let the battery drain which can take a few hours and then plug your phone back into your computer and try the tool again.
Click to expand...
Click to collapse
thanks a lot, you helped me much

runninghamster said:
You need to flash TWRP initially with the EDL Tool aswell. LineageOS / other ROM additions such as GApps and Magisk are flashed via TWRP, which is the recovery on the device and doesn't require a computer.
The phone shouldn't get stuck on EDL mode, but if it does - no need to worry. You can just let the battery drain which can take a few hours and then plug your phone back into your computer and try the tool again.
Click to expand...
Click to collapse
hey another time , thanks again for your help and sorry for my english , i want this time if you can tell me please when i should upgrad to oreo b02 after flash twrp or before flash twrp . and why i should back on oreo b02 after unloacking !