Hi.
Few days ago I locked my bootloader while I was having a TWRP.
In result I coudn't EDL thru test point - HS-USB Diagnostic 900E, had full brick with only fastboot. Even LED was not blinking.
Today I found a solution, maybe someone will find it somehow helpful.
1. Unplug your battery from motherboard, connect USB to the phone and computer and get into the fastboot.
2. Open Miflash, it should be in fastboot mode. Flash fastboot rom, I don't know what it does but it may help.
3. Unlock your bootloader with MiUnlock, if you having any errors play with versions.
4. EDL should work fine now, I used a Annabathina's fastboot to EDL.
5. Just flash new software and enjoy your unbricked phone
Related
Alright, yesterday I decided to root my phone and install LineageOS through bkores' Axon 7 toolkit, starting from a A2017U on B19. Unlocked the bootloader, rooted, flashed TWRP with no problems. Then, I was a dumbass, and flashed LineageOS without first installing the Universal Bootloader or appropriate modem, which resulted in only being able to access the Fastboot and Recovery menus. Then, I panicked and decided to be an even bigger dumbass and locked the bootloader, which has lead me to this point.
For now, when I try to start the phone "normally," it just cycles through the screen with the blue ZTE logo a few times.
I can't get into EDL mode no matter what I try- I even hacked together a deep flash cable.
I can get into Fastboot mode if I hold down both volume buttons as soon as the ZTE screen pops up. From there, I can select "Start," which just takes me to the first boot loop, "Restart bootloader," which just takes me back into Fastboot, "Recovery mode," which doesn't take me to recovery mode and only puts me in the first boot loop, and "Power off," which does exactly what it says it does.
Device Manager recognizes it as "Android Sooner Single ADB Interface" when it's plugged in Fastboot mode. When not in Fastboot mode, it's recognized as "Handset Diagnostic Interface(DFU) (COM3)," with a model of "QUSB__BULK". Typing "adb devices" into the command line results in no connection in either mode.
Miflash recognizes it as a device when plugged in Fastboot, but any attempts to flash anything results in an error message saying "can not found file flash_all_except_storage.bat".
I've tried pretty much every method to restore it back to a usable state- Axon7Toolkit, MiFlash, axon7tool, all with no luck. All of the other threads on here with people in similar situations seem to be for those with AU2017G models, which hasn't helped. Is there anything I can do, or is it FUBAR?
Thank you in advance for the help.
Americ said:
Alright, yesterday I decided to root my phone and install LineageOS through bkores' Axon 7 toolkit, starting from a A2017U on B19. Unlocked the bootloader, rooted, flashed TWRP with no problems. Then, I was a dumbass, and flashed LineageOS without first installing the Universal Bootloader or appropriate modem, which resulted in only being able to access the Fastboot and Recovery menus. Then, I panicked and decided to be an even bigger dumbass and locked the bootloader, which has lead me to this point.
For now, when I try to start the phone "normally," it just cycles through the screen with the blue ZTE logo a few times.
I can't get into EDL mode no matter what I try- I even hacked together a deep flash cable.
I can get into Fastboot mode if I hold down both volume buttons as soon as the ZTE screen pops up. From there, I can select "Start," which just takes me to the first boot loop, "Restart bootloader," which just takes me back into Fastboot, "Recovery mode," which doesn't take me to recovery mode and only puts me in the first boot loop, and "Power off," which does exactly what it says it does.
Device Manager recognizes it as "Android Sooner Single ADB Interface" when it's plugged in Fastboot mode. When not in Fastboot mode, it's recognized as "Handset Diagnostic Interface(DFU) (COM3)," with a model of "QUSB__BULK". Typing "adb devices" into the command line results in no connection in either mode.
Miflash recognizes it as a device when plugged in Fastboot, but any attempts to flash anything results in an error message saying "can not found file flash_all_except_storage.bat".
I've tried pretty much every method to restore it back to a usable state- Axon7Toolkit, MiFlash, axon7tool, all with no luck. All of the other threads on here with people in similar situations seem to be for those with AU2017G models, which hasn't helped. Is there anything I can do, or is it FUBAR?
Thank you in advance for the help.
Click to expand...
Click to collapse
Ouch, DFU brick. I don't know if you can really do anything from fastboot, maybe unlock the bootloader again? fastboot oem unlock?
I'm wondering how you managed to lock the bootloader without having been warned tgat your phone would become a brick if ANYTHING was out of place (for example a custom recovery, or root) Every guide to relock has a big flashy warning. Did you use the toolkit to relock? If that's the case I'd say @bkores needs to add a warning to the option, maybe something like the "Type yes to continue" kind.
Okay, on to the other stuff. There are two ways to fix a DFU brick: send to ZTE, say it broke itself (Or be honest and pay $80, your choice) or take apart your device (I did this on my A2017G, with a lot of care and patience it works). There might be a solution that uses fastboot, but I'm unsure about flashing a system with fastboot, maybe it is possible though. You want EDL mode to use MiFlash and reinstall a working system on the phone. You are on DFU mode instead of EDL. google "4th category brick repair guide" for the actual guide that you need to use (it's here in XDA but it's faster to find via google). Just a small comment:
To download the stuff easily without having to translate the whole 4PDA page (the guys who made the method are Russians from 4pda), find the "MiFlash and Drivers" link. Open it, you'll find a bunch of spoilers. If you open them all you'll see that the actual files that you need to use have non-cyrillic titles, so download the A2017U_FULL_EDL (like 3 GB), and the MiFlash and drivers. Once you have everything you can simply follow the XDA guide and get it up and running again. Remember to keep the battery plugged to the motherboard though, it won't work otherwise
3 months back i hv flashed fastboot rom successfully. but now i stuck with different problems with no solution
1) mobile is dead, when i hold power button mobile screen blink for a second and off again
2)when mob is dead i cant go in developer option and do all that stuff
3)in fastboot mode when i type command "fastboot oem unlock" it shows error
4)when bootloader is locked i cant flash fastboot rom through mi flashtool
this all happen because of choosing wrong patched_boot file at the time of installing magisk manager.
cmd cammand only recognize my device but cant unlock. i find only one solution that is test point method. before i proceed to that need suggestion from u gye's should i go for testpoint or to service center coz mobile is still under warranty.
You can flash stock ROM in edl mode with locked bootloader.
Put phone in fastboot mode and type "fastboot oem edl".
You should be able to flash stock ROM with Miflash. If your device is not recognised update your drivers. Google for qualcomm qloader drivers.
Next time before flashing a modified boot.img try to only boot it and see if it works.
I have an A2017U, Android 7.1.1, build B35, on MiFavor 4.2 and was looking to upgrade to 5.2/Oreo. I get stuck because I can't boot into EDL mode. I have not unlocked the phone but do have developer options & USB debugging enabled. If I boot with vol up + vol down + power, nothing happens even if I wait 120 seconds. I get a slowly flashing red dot. ADB works fine -- my device is recognized -- and "adb reboot EDL" reboots the phone, but not into EDL mode, just into standard mode. MiFlash doesn't see the phone.
I'm clearly doing something wrong but I'm at a loss what, given how simple the instructions are.
prestonmcafee said:
I have an A2017U, Android 7.1.1, build B35, on MiFavor 4.2 and was looking to upgrade to 5.2/Oreo. I get stuck because I can't boot into EDL mode. I have not unlocked the phone but do have developer options & USB debugging enabled. If I boot with vol up + vol down + power, nothing happens even if I wait 120 seconds. I get a slowly flashing red dot. ADB works fine -- my device is recognized -- and "adb reboot EDL" reboots the phone, but not into EDL mode, just into standard mode. MiFlash doesn't see the phone.
I'm clearly doing something wrong but I'm at a loss what, given how simple the instructions are.
Click to expand...
Click to collapse
Try "adb reboot edl" from a booted phone.
EDL actually IS a black screen, usually without an LED though it might be red. Open Device manager and check under "unrecognized devices", or under "Ports (COM & LPT)". Should be there. If it is under Ports and it is callee Qualcomm HS-USB QDLoader 9008 then MiFlash should work
What are you planning to do? EDL back to B19 then unlock? Just curious
Choose an username... said:
Try "adb reboot edl" from a booted phone.
EDL actually IS a black screen, usually without an LED though it might be red. Open Device manager and check under "unrecognized devices", or under "Ports (COM & LPT)". Should be there. If it is under Ports and it is callee Qualcomm HS-USB QDLoader 9008 then MiFlash should work
What are you planning to do? EDL back to B19 then unlock? Just curious
Click to expand...
Click to collapse
I plan to update to Oreo/MiFavor 5.2.
How do I issue the command from a phone? I know how to use ADB from a PC but not from a phone. That is what I have done -- enable developer options, connect the phone, verify that it is connected (adb devices) and then issue the command (adb reboot EDL).
Use the Edl tool by Djkuz
Install it to PC or laptop with all updated drivers
Open edl tool with run as admin
Boot your phone into ftm
Turn your phone off
Press and hold vol dn + power till you see ftm screen
Plug in your phone
Follow the on screen till it detects your phone
Select unlock then edl fix
Edl tool is here
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
prestonmcafee said:
I plan to update to Oreo/MiFavor 5.2.
How do I issue the command from a phone? I know how to use ADB from a PC but not from a phone. That is what I have done -- enable developer options, connect the phone, verify that it is connected (adb devices) and then issue the command (adb reboot EDL).
Click to expand...
Click to collapse
Yes, but what are you going to do BEFORE updating to MF5.2?
you can't edl mifavor 5.2 because you will break stuff, besides you need an unlocked bootloader or you'll DFU brick your phone and you'll have to throw it in the trash.
I meant to issue adb reboot edl from your pc but with your phone on
On a side note, I recommend not using EDL Tool or axon7toolkit to unlock your phone. EDL Tool has a much better track record than other apps but it still has margin for error. The best way to unlock an A2017U is get a B19 EDL package and install it with MiFlash, then enter Fastboot and do "fastboot oem unlock".
Worked!
Syberclone said:
Use the Edl tool by Djkuz
Install it to PC or laptop with all updated drivers
Open edl tool with run as admin
Boot your phone into ftm
Turn your phone off
Press and hold vol dn + power till you see ftm screen
Plug in your phone
Follow the on screen till it detects your phone
Select unlock then edl fix
Edl tool is here
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
That worked, thanks!
Ive used all of the Axon 7 tools as well as adb commands and all work well in there own ways.
Script errors or command errors can be an issue as well as some software (ROMs, recovery and boot imgs) a few times I've had to edit a zip or img to make it work.
After a few boot loops on my HTC.
Is there an official MiFavor Update on 5.2?
My phone is still on 4.2 and can't find any updates.
SebaSnow said:
Is there an official MiFavor Update on 5.2?
My phone is still on 4.2 and can't find any updates.
Click to expand...
Click to collapse
only for Chinese (A2017) phones. It's 8.0 mifavor with the new mf5.0 interface (way more Chinese-looking). If you want to install it on a G or U you'll have to use one of the packages made for them (Usually for an update from other model to work you need to change its modem file to the one that your model uses, i.e. swap the chinese modem with the G's).
Hello everyone,
I want to install LineageOS 15.1 on my ZTE Axon 7 (A2017G) (from official stock rom) and I'm really struggling... I tried five times and my phone end in DFU mode everytime (hopefully there is this tuto https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 ). Can anyone tell me what I'm doing wrong ? I really don't understand... Here is my steps:
1) I unlock my bootloader with Axon7Toolkit
2) I install and update TWRP
3) I full wipe my device
4) I flash A2017G_OreoModem.zip and A2017UV2.1.0B20v01_Bootstack_by_DrakenFX.zip (from https://androidfilehost.com/?w=files&flid=270519)
5) I flash the last nigthly from https://download.lineageos.org/axon7
6) I reboot my phone
And after that my phone is bricked (dfu), when I boot I have the message "Your device is corrupt. It can't be trusted and may not work properly."...
Thanks in advance for your help !
@st3ph31: If you are getting the unlocked bootloader message then you are not in DFU, it is a standard message if you're unlocked. But if you're sure you're in DFU, you can use the DFU MultiDL tool to switch to EDL. The link is here on the A7 subforum, search for it. From EDL you can can flash whatever.
If you read the Los 15 and Los 16 threads
DM Verity enforcing is one fix via twrp or ADB
AnonVendetta said:
@st3ph31: If you are getting the unlocked bootloader message then you are not in DFU, it is a standard message if you're unlocked. But if you're sure you're in DFU, you can use the DFU MultiDL tool to switch to EDL. The link is here on the A7 subforum, search for it. From EDL you can can flash whatever.
Click to expand...
Click to collapse
I think I'm in DFU because when I plug my phone to my PC, it appears as "Handset Diagnostic Interface (DFU)" and I can't get away from this except with the DFU MultiDL Tool! My question is: how can I properly install LineageOS 15.1 without brick my phone ?
@st3ph31: OK, I only mentioned that because both DFU and EDL have a black screen, the device will appear to be turned off. If there is any text on the screen then you are in neither of those modes.
Don't use the LOS bootstack, very simple. LOS bootstack doesn't support accessing EDL via the hardware buttons, instead you will get DFU. @Oki released a B12 bootstack, you can still run LOS with that installed. It has to be flashed via EDL.
https://androidfilehost.com/?fid=1322778262904007731
DFU isn't always bad
Eg: DFU will show on your windows device if its not in Edl mode properly, Edl has been locked in some instances and will not connect as it should.
If you can boot into FTM?
FTM is with phone off, press and hold Vol down and Power till it boots to FTM.
If so use @djkuz Edl tool and see if you can unlock Edl or get to to boot to Edl.
You can flash via Edl if you follow the instructions exactly.
Hope this helps
st3ph31 said:
Hello everyone,
I want to install LineageOS 15.1 on my ZTE Axon 7 (A2017G) (from official stock rom) and I'm really struggling... I tried five times and my phone end in DFU mode everytime (hopefully there is this tuto https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 ). Can anyone tell me what I'm doing wrong ? I really don't understand... Here is my steps:
1) I unlock my bootloader with Axon7Toolkit
2) I install and update TWRP
3) I full wipe my device
4) I flash A2017G_OreoModem.zip and A2017UV2.1.0B20v01_Bootstack_by_DrakenFX.zip (from https://androidfilehost.com/?w=files&flid=270519)
5) I flash the last nigthly from https://download.lineageos.org/axon7
6) I reboot my phone
And after that my phone is bricked (dfu), when I boot I have the message "Your device is corrupt. It can't be trusted and may not work properly."...
Thanks in advance for your help !
Click to expand...
Click to collapse
I don't think you mentioned /vendor at all. If you follow LOS instructions, you'll see that you are lacking the vendor partition. Use the zip provided there (flash once, after recovery reboot flash again) then install orden's TWRP.
If you end up in DFU just use MultiDL and install a recovery again, or just get into Fastboot with the 5 second screen and install the recovery from there. I usually have to do that with my U. Try Oki's recovery with ADB support
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
[Thread Closed] Continue here.