Related
Hello everyone,
So I've read that I can re-lock the bootloadder and tried to do it.
First I have flashed b10 and flashed the su so I wont loose TWRP. I entered fastboot with adb and then I typed fasstboot oem lock, I got a message on the pc with ok.
Since then I cannot boot to the phone.
The phone shows the zte logo for 0.5 seconds but not booting and with constant red led.
Tried power + vol up, power + vol down, all three buttons, vol up + vol down and then connect to pc - nothing at all. The phone wont get past this 0.5 second zte logo.
In all connections I have listed above the phone shows in device manager as QUSB_BULK. At first it was with yellow acclamation mark and then I installed the zadig driver. Now it is connected "normally".
What can I do?
Please refer me to the right tutorial or guide me.
Thanks
I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.
This said, I suggest two methods:
Method A)
Revert back to bootloader unlocked so you will be back as before.
Your current situation with recognized QUSB_BULK driver is good.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?
Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.
And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.
Then the phone should be back operational again as before.
Method B)
Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery
(TWRP if possible), you are saved since with TWRP you can reflash everything.
Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot recovery": does it boot to recovery?
If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed
TWRP for daily operation) is not accepted.
- so you need to reflash tenfar's signed TWRP mentioned in this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).
tenfar's signed recovery is accepted even if the bootloader is locked.
- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!
(reunlock, upgrade TWRP, flash ROM, root...)
dnlilas said:
I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.
This said, I suggest two methods:
Method A)
Revert back to bootloader unlocked so you will be back as before.
Your current situation with recognized QUSB_BULK driver is good.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?
Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.
And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.
Then the phone should be back operational again as before.
Method B)
Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery
(TWRP if possible), you are saved since with TWRP you can reflash everything.
Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot recovery": does it boot to recovery?
If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed
TWRP for daily operation) is not accepted.
- so you need to reflash tenfar's signed TWRP mentioned in this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).
tenfar's signed recovery is accepted even if the bootloader is locked.
- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!
(reunlock, upgrade TWRP, flash ROM, root...)
Click to expand...
Click to collapse
I'll try to do it but yesterday tried to go to edl or recovery in cmd no device found. Tried to flash recovery but it hangs on "waiting for device" so I don't thing I can get to these edl, recovery, fastboot status.
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
dnlilas said:
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
Click to expand...
Click to collapse
I'll try all these guides and update with results
dnlilas said:
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
Click to expand...
Click to collapse
So for sure I'm doing something wrong. Can you please guide me with this tool?
Ironically you helped me unlock the bootloader and I need your assistance relocking it.
Edit: I have the 3 files backed up from the unlocking procedure they should help no?
The phone is not recognized in any adb status edl or fastboot
I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?
QuantumFluxx said:
I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?
Click to expand...
Click to collapse
I don't want to keep twrp or anything. I want to sell the phone so all I want.t is to go back to locked stock phone.
I cannot boot to recovery or fastboot or edl. If I could I would use miflash and flash b10 and be done with it
I think that the initial problem arose when you flashed SU and tried to relock the bootloader with TWRP installed
What does Windows Device Manager show when you connect the phone to your PC?
Update: sorry bud. I totally missed that bit in your OP. DOH! Will update.
Update:
Have you seen this?
https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990
https://forum.xda-developers.com/showpost.php?p=70948893&postcount=28
Sorry that I can't be of more help...
I think what went wrong with my device is that after flashing stock b10 I flashed su so I won't lose twrp. Now when I tried to lock the boot loader made a conflict as I could not have locked bootloader and this version of twrp (for unlocked device). Now I just need to find a way to flash stock recovery (I have a backup from the unlocking procedure) without edl or fastboot as I cannot seem to find a way to enter these states (cause I have no recovery) I'm hoping it makes sense (pretty early in the morning)
So no one can help?
I can't believe the phone is beyond repair
@ItsNewDroid
Sorry I do not have solution, just some idea.
It "seems" that you cannot boot to either system, recovery, bootloader, EDL! adb/fastboot commands are not recognized.
There is still hope since your phone is still recognized somehow as QUSB_BULK (not unknown device) with Zadig driver under USB device.
So you can try to uninstall Zadig WinUSB driver and use Qualcomm bulk drivers so that the phone appears under COM port as Qualcomm HS-USB QDLoader 9008.
If you get 9008 then you are in EDL mode, and MiFlash could be used to flash.
Qualcomm bulk drivers, MiFlash... are available from Download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
The problem is to find available "EDL packages" recognized by MiFlash to flash.
These packages could be stock recovery, signed TWRP, or full ROM (any version, MM, or Nougat).
This would allow booting to either recovery or system.
The problem is that I did not see many such packages for A2017G, but only for A2017U.
You may have to ask other members how to build such "EDL packages" (for ROM, sometimes it is called "fastboot ROM").
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
Edit:
Miflash is not recognized in any key combination.
Edit 2: So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?
ItsNewDroid said:
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
Edit:
Miflash is not recognized in any key combination.
Click to expand...
Click to collapse
Oh no, you unfortunately got the dreaded DFU (device firmware mode).
Looks like it a serious brick. Some topics and articles:
https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
https://community.zteusa.com/thread/14699
https://www.reddit.com/r/Axon7/comments/5oqgfj/a2017g_bricked_cannot_get_past_dfu_mode/
https://www.youtube.com/watch?v=nqF3nr3y-Eg
@dnlilas
Man there are changes!
So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?
Excellent! Try to remember how you get to this menu.
Does "adb devices" command recognized? Status "xxx recovery"?
Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:
"fastboot oem unlock"
It should ask on phone to erase data (like factory reset). Then say yes.
Edit: the screen capture you took is the bootloader menu (equivalent to come into with "adb reboot bootloader").
When in bootloader, I believe you can use Volume-Up and Volume-Down to navigate (to go to recovery, system, bootloader or other mode). Validate with Power button. It is important to remember how to get to this bootloader menu.
dnlilas said:
Excellent! Try to remember how you get to this menu.
Does "adb devices" command recognized? Status "xxx recovery"?
Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:
"fastboot oem unlock"
It should ask on phone to erase data (like factory reset). Then say yes.
Click to expand...
Click to collapse
I held the 3 buttons not connected to power or pc. As soon as I felt the vibration before zte logo I let go of the vol up button and it booted to fastboot.
I dont want to unlock the bootloader I want to sell the phone ( this is the reason I came to this situation) I tried to boot to recovery from this menu but it could not.
My guess is that I have twrp recovery and as the bootloader is locked it can not boot.
I need either a twrp for LOCKED bootloader or a stock recovery.
I'm searching the forum but could not find.
You are a wizard! Every time you reply I have good news :good::laugh:
@ItsNewDroid
Download tenfar's signed TWRP here:
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Important: check md5 6eeb1a9d02470a840bc68019184d9a72
A2017G-TWRPrecovery3.0.2.2tenfar.img
to insure correct download.
Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).
Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.
The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.
In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),
make a copy of it with the name recovery.bin:
copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin
Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.
If OK, then issue the command:
axon7tool-1.5-win64.exe -w recovery
If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).
Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).
Good luck to you!
dnlilas said:
@ItsNewDroid
Download tenfar's signed TWRP here:
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Important: check md5 6eeb1a9d02470a840bc68019184d9a72
A2017G-TWRPrecovery3.0.2.2tenfar.img
to insure correct download.
Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).
Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.
The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.
In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),
make a copy of it with the name recovery.bin:
copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin
Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.
If OK, then issue the command:
axon7tool-1.5-win64.exe -w recovery
If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).
Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).
Good luck to you!
Click to expand...
Click to collapse
So this is the new situation: adb devices phone is not recognized. Fastboot devices device IS recognized. Issuing axon7tool - w recovery I get device not connected failed to connect. Any idea?
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
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
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).
Hi,
i used Miflash in edl mode to get back to stock rom. after flash and reboot I used the recovery mode to do a factory reset.
It seems to work. It shows Android Recovery, but the bootloader is still unlocked.
What mode do I need to enter to use the "fastboot oem lock" command? I always see "waiting for device" and nothing happens
When I type "adb devices" I can see the phone. I saw there is a command "fastboot devices", too. but it shows me no result.
Stevie123 said:
Hi,
i used Miflash in edl mode to get back to stock rom. after flash and reboot I used the recovery mode to do a factory reset.
It seems to work. It shows Android Recovery, but the bootloader is still unlocked.
What mode do I need to enter to use the "fastboot oem lock" command? I always see "waiting for device" and nothing happens
When I type "adb devices" I can see the phone. I saw there is a command "fastboot devices", too. but it shows me no result.
Click to expand...
Click to collapse
Reboot to fastboot using
adb reboot fastboot
Click to expand...
Click to collapse
Then, try to use fastboot cmd
Thanks, before I can try that I have to solve another problem.
That doesn't work. The phone isn't entering a special mode. I can choose fastboot from the bootmenu, too. But nothing happens. The phone does a restart, shows the bootmenu again and boots android after 5 seconds.
@Stevie123
You need to enable fastboot (bootloader) mode since it is disabled by ZTE, so that the selection from menu to be effective (after enabling it, in fastboot mode, your command "fastboot devices" (to check) and "fastboot oem lock" (to lock bootloader) will be accepted).
You can use Axon 7 EDL tool to unlock the bootloader.
It's already unlocked. I have to make another unlock procedure again to get access to fastboot? The EDL Tool tells me that I have to wipe and reset the phone after it. So it seems I can't keep my data and just lock the bootloader.
Either Lock or Unlock will wipe your data. And yes, the unlock procedure by Axon 7 EDL tool includes the enabling of fastboot. So you have to re-unlock if you want to relock.
I think this EDL tool doesn't work very good. It flashed something to make fastboot available, but I had a green ZTE Logo screen and this screen also had errors like white spots. The original ZTE logo is in cyan. But the fastboot worked and I could lock the phone. But I couldn't do anything else anymore. I couldn't reach Android and reflashing also didn't work. So I tried to use the EDL Tool to unlock my bootloader again. It said success, but it didn't work. It was still locked.
Well, I had to wait until the phone was empty. Luckily I could reach EDL Mode again. I used the MiFlash again to Downgrade to Android Nougat B12. I read somewhere that the fastboot is included there. So I had the right ZTE Logo back and it worked. I could leave the Bootloader locked. The final update I did with a SD Card to the lastest Android Software for Axon 7. Luckily without a brick. It's a pity that they don't offer any Updates anymore.