Bricked Axon 7 after re-locking bootloader - ZTE Axon 7 Questions & Answers

Long story short. I had an Axon 7 A2017 B11 which I updated to B13. I was able to unlock the bootloader, root the phone then flash a custom rom Z.A.D.Mix7_v0.3. I was having fun with the phone but I did something very stupid when I realised I could not use Android pay due to unlocked boot loader. Without doing enough research, I went to fastboot and did a fastboot oem lock. The command was successful but I could no longer boot into the system or recovery or fastboot. I tried MiFlash with B07 which was posted in this forum, but it did not work, came back an error of bad format. Then I used axon7tool to flash TWRP 3.0.2 and the boot.img which I extracted from B13. I am now able to boot into TWRP and fastboot. But I still do not have a working system. I tried fastboot oem unlock, it does not let me do it. I flash ZAD Mix7 again but once I flash that it does not boot anymore. I am now really stuck. What should I do to go back to stock then start everything again. Thanks a lot for the help.

I understand your device doesn't boot into system anymore, but can adb on your pc detect it at all? If so, you can try following all steps after "B)" in my tutorial. I think your aboot img and fbop partition are messed up. If you can use adb to replace the files in aboot and fbop with files that allow the fastboot oem unlock command to be executed, it should be unlockable again. After that, custom ROMs should boot.

Stock bootloader
Controllerboy said:
If you can use adb to replace the files in aboot and fbop with files that allow the fastboot oem unlock command to be executed, it should be unlockable again. After that, custom ROMs should boot.
Click to expand...
Click to collapse
I'm having a similar issue. Although my phone boots to stock rom I seem to have messed up my bootloader. I had TWRP and unlocked bootloader. I, similarly, locked the bootloader and things seemed to be fine. After attempting to install Nougat received from OTA I realized my bootloader is corrupted. When I hold the power and volume up the phone seems to just turn off (or go to EDL mode? I'm not sure) I can always just hold power and it'll boot up normally. Is there a way to get the stock bootloader to work and keep it locked?

I also bricked my A7 after relocking my bootloader. I used tenfar's tool to make TWRP my boot.img, then flashed ZTE's stock B20 image. Here's the thread where I found the file links.
From there I updated all the way up to the OTA Nougat, but I suppose you can decide where you want to go after it's unbricked. Hope this helps.

Why are so many people relocking bl? Regardless, always take an ota before locking to ensure you are completely shock.

Stock bootloader
lafester said:
Why are so many people relocking bl? Regardless, always take an ota before locking to ensure you are completely shock.
Click to expand...
Click to collapse
Don't you have to be running a locked bootloader in order to be able to install OTAs?

aabnamak said:
Don't you have to be running a locked bootloader in order to be able to install OTAs?
Click to expand...
Click to collapse
Of course not.

aabnamak said:
Don't you have to be running a locked bootloader in order to be able to install OTAs?
Click to expand...
Click to collapse
No, you do not. I thought that was the case at first as well, but I was mistaken. You do, however, need the stock recovery and an untouched system partition.

My problem is that I don't seem to have a recovery at all. I realized once the ZTE logo pops up I can hold down both volume keys and get to the bootloader. The bootloader is locked but does not display a bootloader version or basedband version. I tried the tenfar tool (axon7root.exe) and now my phone doesn't boot into the system either. I really need help...

Just an update to everyone that helped.
I finally managed to fix it.
I used axon7tool to flash a signed TWRP, so that i can boot into TWRP. The signed TWRP is the only way to make it work. Then I downloaded the A2017 B11 from this thread
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
There are two zip files. The boot stack and the rom. Because it is a stock rom, I can boot into the system. The next thing I did was to enable the developer option and turn back on the option to allow OEM unlock.
I went back to TWRP. boot into the fastboot screen. Then I simply typed in 'fastboot oem unlock'.
I went back to TWRP, which says can't read encrypted device. I formated everything. mount the USB then flash the custom rom again.
Hola, phone fixed. Made me sweat for the whole day.

deleted...forgot I had a micro sd card. Flashed stock update from the card and it worked. Phew!

Related

Anyway to unlock oem from bootloader or TWRP?

I was trying to flash the stock image and i guess i messed up somewhere because after i did that i locked the bootloder and not it is not booting past the google screen. i want to reflash all images but i cant cause the bootloader is locked. so is there anyway to unlock the oem in bootloader or recovery mode TWRP? i can access terminal in TWRP so any command that can help me?
TheTickReborn said:
I was trying to flash the stock image and i guess i messed up somewhere because after i did that i locked the bootloder and not it is not booting past the google screen. i want to reflash all images but i cant cause the bootloader is locked. so is there anyway to unlock the oem in bootloader or recovery mode TWRP? i can access terminal in TWRP so any command that can help me?
Click to expand...
Click to collapse
Maybe try and sideloading the it's through twrp. I can't remember if an unlocked bootloader is needed though. Also, you could maybe try flashing a custom ROM to see if you can boot into it.

A2017G How to relock bootloader on Nougat B10

I came back from LOS 16.0. Flashed A2017G_B10_NOUGAT_FULL_EDL in EDL but there's a warning that my bootloader is locked. I wanted to relock it but the warning prevents me from entering bootloader or fastboot (or maybe they are not even present....). Next I flashed A2017U_FASTBOOT_UNLOCK_EDL in MiFlash but it did not do anything. It flashed OK but I still cannot access fastboot. Should I flash some marshmallow rom? Thanks in advance.
I have the same problem. Cannot enter fastboot mode on Nougat ROM.
Ok I found the way usin Axon 7 Toolkit
1. Set the Android version to 7 using option 13
2. Perform unlock bootloader
Following instruction Axon & Tookit gives you EDL image of the proper fastboot partition giving the possibility to enter fastboot mode
then fasboot oem lock
I wanted to say thanks that works, but apparently my phone is bricked now - it hangs on green ZTE logo. PC recognizes it as DFU. Cannot enter EDL either. I guess I look for some guide how to recover from this situation
Managed to fix that. Somehow I was able to enter fastboot. It said my bootloader was locked so i flashed TWRP and from TWRP using ADB installed stock Nougat rom
ma_ko said:
I wanted to say thanks that works, but apparently my phone is bricked now - it hangs on green ZTE logo. PC recognizes it as DFU. Cannot enter EDL either. I guess I look for some guide how to recover from this situation
Managed to fix that. Somehow I was able to enter fastboot. It said my bootloader was locked so i flashed TWRP and from TWRP using ADB installed stock Nougat rom
Click to expand...
Click to collapse
If you was able flash twrp mens your boolaeder was unlocked?
No there's a TWRP that works on locked bootloader.
ma_ko said:
No there's a TWRP that works on locked bootloader.
Click to expand...
Click to collapse
Seems that TWRP was inatlled before the bootloder was locked again.

Trying to re-lock the bootloader

I have a A2017U that I just downgraded to B35 using this guide: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
I want to lock the bootloader to stop the annoying boot warning but can't get into fastboot when using AXON7TOOLKIT.
I tried flashing A2017U_FASTBOOT_UNLOCK_EDL (downloaded from https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128) through miFlash but I still can't get into the bootloader.
What can I do?
EDIT: Thanks everyone! I used the toolkit to unlock the bootloader again, then locked it. For some reason I couldn't access the bootloader even though i got the bootloader ulocked warning.
mateokross said:
I have a A2017U that I just downgraded to B35 using this guide: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
I want to lock the bootloader to stop the annoying boot warning but can't get into fastboot when using AXON7TOOLKIT.
I tried flashing A2017U_FASTBOOT_UNLOCK_EDL (downloaded from https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128) through miFlash but I still can't get into the bootloader.
What can I do?
Click to expand...
Click to collapse
You only want to lock it because of the boot warning? There are flashables to get rid of that... I dom't know which exact files there are for stock B35 or Oreo but there are some going around.
hell you could even go custom and use the splash bootstack if you wanted.
If you want to lock anyways, you have to get an A2017U B19 package and flash it via EDL Tool (or MiFlash). Right after that you'll have fastboot. enable oem unlocking then enter fastboot and issue fastboot oem lock and you're done. But it's way too overkill if you want to just get rid of the 5 sec screen
mateokross said:
I have a A2017U that I just downgraded to B35 using this guide: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
I want to lock the bootloader to stop the annoying boot warning but can't get into fastboot when using AXON7TOOLKIT.
I tried flashing A2017U_FASTBOOT_UNLOCK_EDL (downloaded from https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128) through miFlash but I still can't get into the bootloader.
What can I do?
Click to expand...
Click to collapse
you need to flash original stock rom for your device trough edl. (rom your device came from factory,marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)

Unlock bootloader on non-booting device?

I updated to Pie today using OTA. This resulted in a bootloop. Since my bootloader was already unlocked, I booted TWRP (not flashed) and swapped slots. This resulted in booting to the recovery "no command" prompt instead. So I downloaded the only ROM Xiaomi has on their site - 8.1 - and flashed this with the "flash_all_except_storage" script. Still bootloops, only now the bootloader is relocked.
So, anyone know how to unlock the bootloader on a non-booting Android One device? Is there an EDL mode on these?
tin2001 said:
I updated to Pie today using OTA. This resulted in a bootloop. Since my bootloader was already unlocked, I booted TWRP (not flashed) and swapped slots. This resulted in booting to the recovery "no command" prompt instead. So I downloaded the only ROM Xiaomi has on their site - 8.1 - and flashed this with the "flash_all_except_storage" script. Still bootloops, only now the bootloader is relocked.
So, anyone know how to unlock the bootloader on a non-booting Android One device? Is there an EDL mode on these?
Click to expand...
Click to collapse
Seriously? No one reads thread online?! I quote to NEVER, EVER, FLASH OREO/NOUGAT ROMS AFTER UPDATING TO PIE!!!
I downloaded the latest OFFICIAL ROM when it was already bootlooping.... Seriously? I'm supposed to go searching online for 3rd party information rather than the official?
Now how about people with useful information instead of arrogance?
If I'm not wrong you just need to boot into bootloader and fastboot oem unlock. With unlocked bootloader, go fastboot mode and flash official stock pie fastboot rom

Super Stucked, Nothing Helps now.

I had hardbricked my devices while installing an OTA update and the device was Hardbricked .
I blank flashed the device and it booted and bootloader.
Now the problem starts here.
I flashed the OEM_Lock.bat as I wanted to relock the bootloader. I'm not sure what went wrong but the flash didn't complete and stuck in middle.
The problem remains here is it shows
Fastboot Reason: Failed to initialize partition table
I am unable to flash anything now. Recovery.img fails, bootloader.img fails, twrp flashing fails.
Nothing flashes as Bootloader is locked.
I went to Motorola Service Centre. They also couldn't do anything and simply said that their software doesnt read the phone.
Is there anyone whoe can really help me out with anything left to do?
Any method to force flash recovery, even twrp?
Phone is detected as Fastboot athene_16mp S in computer. It doesnt detect as "Qualcomm HS-USB QDLoader 9008".
What firmware are you attempting to flash?
Your device looks like it's still on the blank flash provided bootloader, which means you have to flash at least the GPT and bootloader. The lack of a serial number and the generic identifier implies you have not been able to flash an actual GPT and bootloader. Also, OEM_locked is normal until you get an actual bootloader flashed over the blank flash bootloader, which usually means trying to flash a GPT and bootloader at least as new as the latest version you had on your device (regardless of downgrades).
I'd suggest downloading the latest Nougat stock ROM we have from here. Do not use any of the scripts at this time.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Edit - also, this post probably is better suited to the Q and A section...
echo92 said:
What firmware are you attempting to flash?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Click to expand...
Click to collapse
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
mysteryno46 said:
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
Click to expand...
Click to collapse
Eh, you live and learn. Besides, you've now got your device running now!
Honestly, it's up to you. Having a locked or unlocked bootloader will not affect your ability to receive OTA updates - you should still receive updates so long as your firmware matches your software channel (and since your device was XT1643, the NPJS25.93-14-18 April 2018 security update should be the correct firmware). At this moment in time, you'll have to use the NPJS25.93-14-18 firmware to re-lock your bootloader - we don't have the stock Oreo firmware at this time. Thus, if you update to stock Oreo, you will not be able to re-lock your bootloader until you can get a leak of the Oreo firmware.
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Back to Locked Bootloader, complete stock.
echo92 said:
Eh, you live and learn. Besides, you've now got your device running now!
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Click to expand...
Click to collapse
I am back to Locked Bootloader as feel the same as you said that anyone buying might get scared by looking the warning sign. Thanks for helping out. :highfive:
Oreo Update via OTA has already started rolling out as per the news I've been reading. I just wanted to see the oreo 8.1 before I sell the phone.
Anyways I got a new device now, Realme C1, 3|32GB as my smartphone usage has declined a lot recently and might remain similar. This device will suffice my requirements.
Thanks for the help and support. :victory:

Categories

Resources