Database Users

after updating to b27 how to install TWRP?

So followed @DrakenFX instructions per THIS, now how do I get TWRP back?
Cheers!

swehes said:
So followed @DrakenFX instructions per THIS, now how do I get TWRP back?
Cheers!
Click to expand...
Click to collapse
Reboot to bootloader and flash twrp using fastboot.
Code:
fastboot flash recovery file_name_here.img
This is assuming you are unlock and ha e check OEM unlocking in dev. Options

If your bootloader is already unlocked, just boot into fastboot and flash TWRP.

forgot to put it in OEM Unlock.

Is it possible to relock the bootloader?

I'm holding off twrp + bootloader unlock because I want to be able to undo in case I need to use my warranty. Is twrp/bootloader unlock reversible? Many thanks

Yes. Flash complete stock everything, boot into bootloader, connect to PC, and "fastboot oem lock".

Is it sure that it works??I have a A2017G and i have open BL and a B29 Custom Rom and i want back to Lock Bootloader

Kevinkuensken said:
Is it sure that it works??I have a A2017G and i have open BL and a B29 Custom Rom and i want back to Lock Bootloader
Click to expand...
Click to collapse
Yup! I've done it plenty of times. You do need to format the data partition though. This could mean that it'll wipe out even your internal storage, so back that up as well!

Im on stock and then i go to edl and then i type fastboot oem lock but nothing happend

Kevinkuensken said:
Im on stock and then i go to edl and then i type fastboot oem lock but nothing happend
Click to expand...
Click to collapse
Boot into bootloader, not EDL.

Erahgon said:
Yup! I've done it plenty of times. You do need to format the data partition though. This could mean that it'll wipe out even your internal storage, so back that up as well!
Click to expand...
Click to collapse
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.

BlazingBullets said:
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
Click to expand...
Click to collapse
Locking it again is good for when you want to sell the device or send it in for warranty repair.

BlazingBullets said:
and you can unlock it again afterwards?
Never heard of anyone wanting to lock the bootloader so I'd a newb in this kind of thing.
Click to expand...
Click to collapse
Yeah, the unlock procedure is the same as before. If you didn't restore the original boot image before the relock, then it's just a matter of booting into fastboot and unlocking the device. Note that this will cause your data to be wiped as well!

If you restore your boot.bin backup file from when your device was locked, does this lock the bootloader? "fastboot oem lock", "fastboot flashing lock" nor "fastboot oem device-info" does nothing for me. Is there any other way to check if your bootloader has been relocked?
Thanks

H0lmEd said:
I'm holding off twrp + bootloader unlock because I want to be able to undo in case I need to use my warranty. Is twrp/bootloader unlock reversible? Many thanks
Click to expand...
Click to collapse
Hi there,
Were you ever able to re-lock your bootloader on your A2017G?
I just want root for now but understand that I'll need to unlock the bootloader first. Before doing that, I want to make sure I can re-lock the bootloader if needed.
Thanks for letting us know!

joaste said:
Hi there,
Were you ever able to re-lock your bootloader on your A2017G?
I just want root for now but understand that I'll need to unlock the bootloader first. Before doing that, I want to make sure I can re-lock the bootloader if needed.
Thanks for letting us know!
Click to expand...
Click to collapse
Guys/Gals, it is seriously as simple as using the fastboot command in reverse. I've done it a few times already with mine.
If you used the following to unlock....
fastboot devices
fastboot oem unlock
.....then you can use the following commands to relock
fastboot devices
fastboot oem lock
fastboot devices is not necessary, but I do it to make sure the devices is being recognized by ADB/FASTBOOT

sauerkraut17 said:
Guys/Gals, it is seriously as simple as using the fastboot command in reverse. I've done it a few times already with mine.
If you used the following to unlock....
fastboot devices
fastboot oem unlock
.....then you can use the following commands to relock
fastboot devices
fastboot oem lock
fastboot devices is not necessary, but I do it to make sure the devices is being recognized by ADB/FASTBOOT
Click to expand...
Click to collapse
Thanks for the answer.
But there are a few files to flash before using that command according to this thread.
Doesn't anything need to be flashed again (e. g. stock files or anything)?

Correct, but you would have already flashed those in order to use the unlock command in the first place.
Are you trying to relock on marshmallow or nougat?

sauerkraut17 said:
Correct, but you would have already flashed those in order to use the unlock command in the first place.
Are you trying to relock on marshmallow or nougat?
Click to expand...
Click to collapse
My phone is only a few days old. I'm debating whether to keep it or not (considering the Mate 9, but the price is not the same - love the form factor and bigger screen though - sound won't be the same and I think I'll miss the MiPop button on the Axon (never thought that would happen )).
I'm on the latest MM (B10 - the A2017G model).
Following the mentioned thread, I got to the point of installing TWRP (the signed version), only to realize that besides making backups, there is not much else I can do with that without unlocking the bootloader. I really just wanted to flash supersu and install adaway fro the time being until development matured for this phone (maybe also play around with viper - had great results on my LG G4).

HI, I get the error "FAILED (remote: unknown command)" in ADB when I enter "fastboot oem lock". Any way to fix this?

Guys, can anyone help me? I really need to lock the bootloader!
How can I fix the error "FAILED (remote: unknown command)" in ADB when I enter "fastboot oem lock"?
I'm on MM B11 Stock.
https://i.imgur.com/fdkgYs6.jpg

Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.

I soft bricked my phone

I wanted to unlock the bootloader and flash a custom rom, but I followed the wrong guide. I am or was running A2017U build 27 but I followed a guide for A2017G, here https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379.
My phone is stuck at the ZTE logo screen and will not proceed despite using TWRP to flash the backup image. Am I screwed?

project_86 said:
I wanted to unlock the bootloader and flash a custom rom, but I followed the wrong guide. I am or was running A2017U build 27 but I followed a guide for A2017G, here https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379.
My phone is stuck at the ZTE logo screen and will not proceed despite using TWRP to flash the backup image. Am I screwed?
Click to expand...
Click to collapse
If you still able to boot to TWRP, I recommend you flashing my B29 Bootstack + StockSystem from here : B29 Files Click Here , then you can flah Stock Recovery you'll be up and running again, i'll be uploading TWRP Flashable B29 recovery Here is the Stock Recovery Flashable Zip CLICK HERE ... YOU CAN UNLOCK using B20 Official ZIP + B20fastboot.zip (Official).
So here Steps:
1- Flash B29 Bootstack + StockSystem
2- Flash Stock Recovery
3- You'll have you device back and running

DrakenFX, thank you. Flashing the bootstack and stocksystem got me in working order. $20 coming your way as promised. Don't drink and flash folks. Lesson learned.

project_86 said:
DrakenFX, thank you. Flashing the bootstack and stocksystem got me in working order. $20 coming your way as promised. Don't drink and flash folks. Lesson learned.
Click to expand...
Click to collapse
you don't have to man, i'm just glad i'm here to help other. send me you hangouts via PM , i'll help you getting Unlock Bootloader before N get here,

Thanks I appreciate that.

***EDIT*** This was caused by the fastboot I had on my PC. Rebooting into Linux and using that fastboot worked fine.
I was able to downgrade to B20, however, flashing your P996A01B20Fastboot_ssl.zip file did not allow me to unlock the bootloader. After rebooting, going into the bootloader menu, and running "fastboot oem unlock" does nothing nor does "fastboot devices" see any device. Do you have any ideas why it is not working?
To be clear, when I ran the P996A01B20Fastboot_ssl.zip from stock recovery it said,
"script succeeded: result was [1.0000000] Install from SD card complete."

Bricked Axon 7 after re-locking bootloader

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!

Re-lock Bootloader

Hi all,
I am trying to re-lock my bootloader, but my fastboot commands aren't working. It says "remote error command not found."
I am running stock b19 (7.1.1) unrooted. The only thing modified is the bootloader, which is unlocked.
How do I fix this error. I installed the ADB drivers. I do not know what is causing this error. Any help will be appreciated.

TheWoerbler said:
Hi all,
I am trying to re-lock my bootloader, but my fastboot commands aren't working. It says "remote error command not found."
I am running stock b19 (7.1.1) unrooted. The only thing modified is the bootloader, which is unlocked.
How do I fix this error. I installed the ADB drivers. I do not know what is causing this error. Any help will be appreciated.
Click to expand...
Click to collapse
I think fastboot commands were disabled in b19. There's no harm in keeping it unlocked unless you're wanting to use Android Pay (in which case Magisk can hide the unlocked bootloader), or you're needing to return the phone for warranty reasons.

bluestudy said:
I think fastboot commands were disabled in b19. There's no harm in keeping it unlocked unless you're wanting to use Android Pay (in which case Magisk can hide the unlocked bootloader), or you're needing to return the phone for warranty reasons.
Click to expand...
Click to collapse
So I installed the factory image from ZTE's website, which uninstalled twrp and SuperSU (which I knew it would), but I am still unable to use fastboot commands. What might be causing this problem?

As far as I know you need to rollback and flash DrakenFX's fastboot command zip in order to be able to use fastboot again.

iNaruX said:
As far as I know you need to rollback and flash DrakenFX's fastboot command zip in order to be able to use fastboot again.
Click to expand...
Click to collapse
So I changed some settings in Windows Device Manager, now fastboot is working...kinda. I type "fastboot oem lock" and it hangs up for 5 seconds and gives me the error "FAILED (command write failed (Unknown error))...
I solve one problem, and another pops up... Thoughts?
EDIT: In regards to DrakenFX's fastboot command zip, where would I get that? Is it the full systemstock?

I read this guide for the Axon7 A2017G, but the zips used are for the A2017U.
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
The first couple of steps restore the bootloader and get fastboot commands up and running via EDL mode.

iNaruX said:
I read this guide for the Axon7 A2017G, but the zips used are for the A2017U.
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
The first couple of steps restore the bootloader and get fastboot commands up and running via EDL mode.
Click to expand...
Click to collapse
I am currently running B29 (6.0.1). Will this still work, even though I am on a different version of Android? Or should I update to B19?

Oh...if you are on MM this should work for you.
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Just flashable zip in Recovery, no need for EDL.
I'm not an A2017U though...

iNaruX said:
Oh...if you are on MM this should work for you.
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Just flashable zip in Recovery, no need for EDL.
I'm not an A2017U though...
Click to expand...
Click to collapse
Just for clarification: I am trying to LOCK my bootloader, not UNLOCK. Sorry if I've been unclear. I need to RE-LOCK my bootloader...everything else is stock (recovery, no SuperSU, etc.)
P.S. Thank you for your help, I really appreciate you taking the time.\
EDIT: AHHHHHHHHHHHHH I GOT IT!!!!! Thank you so so much!!! I really appreciate your help, you have no idea!! I followed the last guide you sent me and replaced "unlock" with "lock." You're the best, man...or woman!

TheWoerbler said:
Just for clarification: I am trying to LOCK my bootloader, not UNLOCK. Sorry if I've been unclear. I need to RE-LOCK my bootloader...everything else is stock (recovery, no SuperSU, etc.)
P.S. Thank you for your help, I really appreciate you taking the time.\
EDIT: AHHHHHHHHHHHHH I GOT IT!!!!! Thank you so so much!!! I really appreciate your help, you have no idea!! I followed the last guide you sent me and replaced "unlock" with "lock." You're the best, man...or woman!
Click to expand...
Click to collapse
Haha cheers, I think you got it, I sent that guide just to enable fastboot commands, glad it worked :good:

I need to re-lock the bootloader on my A2017U. I put in a warranty repair claim with ZTE for a dead SIM2 slot. They said if I could relock it to stock, they would not charge the $79.99 out-of-warranty fee.
My only concern with the guides above is that I'm on the RR Nougat ROM. Will any of the links above work for me?

Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.

TheBoozer said:
Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.
Click to expand...
Click to collapse
This guide should do the trick: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413

soren25 said:
This guide should do the trick: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
Click to expand...
Click to collapse
Thank you very much for your help, I am now back to stock B15. The only thing left for me is to relock the bootloader.