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!
When every i try lock and relock my bootloader i cant because fastboot says stat not match i cannot do anything i tried flashing mm but it says command not allowed and i cant lock my boot loader and unlock it to allow it how can i get past this? Adb cannot see muly phone i cant boot into twrp and i only have access yo fastboot mode as erecovery didnt work with my un offical nrd90m update.
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.
Hello,
I have a galaxsy s5 906k and I've been reading on how to unlock the bootloader as I'm trying to install Remix OS and it seems I've come across a lot of misinformation.... and if possible can someone tell me what exactly I need to unlock the bootloader, as I can't find a list of the appropriate tools? Do I need twrp for my specific device?? Some have said yes and some no.
My phone is already rooted.
Also post unlock bootloader question, can I use the 900k rom from remix to install on my 906k?
EDIT**
I can only boot into download mode, not fastboot mode. adb devices returns the device, but fastboot devices returns nothing. Tried adb reboot-bootloader`and it just shows waiting for any device.
These all boot into download/odin mode!!!!!!
adb reboot download
adb reboot bootloader / adb reboot-bootloader
fastboot oem unlock
fastboot flashing unlock
Only one that boots into recovery mode! Then I go to Reboot to bootloader and it comes back to recovery mode!!!!!!!!!!
adb reboot recovery
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)