Database Users

Switching between N and MM roms

Good morning, (at least where I'm at) I want to test out a Nougat rom or two and I am currently on a Marshmallow rom (specifically Resurrection Remix). I know I have to flash the radios for Nougat, and also the vendor image. However,if I end up going back to my old rom will I have to flash MM radios again or will the new radios still work? Also will there be any other problems when going between Nougat and MM? I don't believe this question has been asked. At least I could not find it. If it was feel free to just leave the link below! Thanks for you help!

Hi mate.
Radios are backwards compatible, so the Nougat radio will work on MM, however in case you want to go back you can also do it.
About downgrading from N to MM this are the steps I used to return to stock MM. The only thing that cannot be downgraded is the bootloader.
1. Enabled OEM unlock in developer options.
2. Booted into bootloader and used "fastboot flashing unlock" to unlock bootloader.
3. Rebooted phone and went through initial setup (Still in Nougat).
4. Booted into bootloader and flashed radio.img and rebooted bootloader.
5. In bootoader, I booted TWRP without flashing it using "fastboot boot twrp.img"
6. In TWRP I did a factory reset, then went into advanced wipe and marked all the options and proceeded to wipe. Finally I used the option of wipe data.
7. Booted into bootloader again from the options in TWRP, and started doing the following commands:
a. fastboot flash boot boot.img
b. fastboot erase cache
c. fastboot flash cache cache.img
d. fastboot flash recovery recovery.img
e. fastboot format system
f. fastboot flash system system.img
g. fastboot erase vendor
h. fastboot flash vendor vendor.img
i. fastboot format userdata
8. Then proceeded to boot the phone and now I'm running MM again.

You do need only this...from Marshmallow just update to the last Nougat version NRD90U, with the stock factory image...then you can with a custom recovery, switch between N and M without any problem...just flash custom via recovery and it works...no need to flash boot, bootloader, vendor ecc any time... only rom

Thanks, if i would have known that i would have updated my stock to Nougut first before unlocking, when i get home tonight i will go back to stock and update. Then i will reflash twrp and my custom rom. Thanks!

A2017G How to relock Bootloader to original mode.

Hi,
is it possible to relock the bootloader to original factory mode.

fastboot oem lock (will erase userdata)
Also you should restore the fbop partition: /dev/block/bootdevice/by-name/fbop
For more reference see:
https://forum.xda-developers.com/axon-7/help/lock-unlocked-bootloader-t3444044
https://forum.xda-developers.com/showpost.php?p=68738854&postcount=100
Also please don't open a thread to a question that has already been answered several times.

After i unlocked bootloader my phone now is recognized as A2017U. When i relock it will it then recognized as original A2017G ?

I am interested in a tutorial about going back to stock for G model

The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.

Bomberus said:
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Click to expand...
Click to collapse
At the moment i am on B09 rooted but I installed it via TWRP using DrakenFx's tutorial from here : https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Futhermore when I unlocked the bootloader I was on B03 and I saved the aboot.img and fbop_lock.img .
Now I would like to go back to fully stock to prepare for the android N update.
I would highly appreciate it if you could offer me some directions for this matter.

Never tried this method (so I take no responsibility) but in order to receive ota you need an unmodified system with locked bootloader.
To lock your bootloader:
First backup all your apps, data and internal sdcard !
Connect your phone to a PC and start adb:
Type: "adb reboot bootloader"
Phone will restart: (if you are on linux, run fastboot with root permission)
Type: "fastboot oem device-info" (just to check things)
"fastboot oem lock" (will lock your bootloader)
According to DrakenFX you should have the stock recovery already installed. So you can flash a sd card upgrade from ZTE "http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6" (to bring you back to stock)
If you still have TWRP use DrakenFX files to flash your system back to stock, but this time do not flash supersu.
You should be good to go and just have to wait for ZTE to release the update and apply it via the updater UI.
BTW this is my fastboot oem device-info output:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.059s]
finished. total time: 0.059s
Click to expand...
Click to collapse

dodo34 said:
Hi,
is it possible to relock the bootloader to original factory mode.
Click to expand...
Click to collapse
You mind my asking the reason WHY you want to Relock?
If is cuz the N update , I'll rather keep it unlock base on @lokissmile thread and I'm 100% sure I'll be releasing N TWRP Flashable Zips for all variants when N is available.

i have G model and flashed the aboot of the U modell.
How to flash back now the aboot of the G modell back ?

Any help for the G modell ?

dodo34 said:
Any help for the G modell ?
Click to expand...
Click to collapse
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.

LifeSupportZ said:
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
Click to expand...
Click to collapse
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"

peramikic said:
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
Click to expand...
Click to collapse
if he mod the updater_script from official zte update to make it flash friendly, this is what i'll do,
* Mod updater script and remove aboot and recovery for now
* flash new zip without file mention above
* boot to bootloader while having custom recovery
* lock back the bootloader
* boot to custom recovery and perform " format data "
* create a flashable zip with stock aboot and recovery
* flash new zip with aboot and recovery
* reboot to recovery and check if boot to stock recovery and while in there perform a factory reset
i know is a lot of steps but, seems like is the way to go to get everything back in place without zte noticing anything.

Now i am on B06.
I put update.zip B08 and select update. But it boots to TWRP recovery and update fails.

@dodo34 If you are trying to restore from the OS system update you need to reflash your stock recovery for it to work properly. Wait for someone to confirm what I just said, but that's how it worked for me.

how can i flash my original recovery. what is the command for cmd ?

Please help restoring back original recovery.

dodo34 said:
Please help restoring back original recovery.
Click to expand...
Click to collapse
rczrider said:
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Click to expand...
Click to collapse
Try this guide from newbie unlock thread.

I get this error.
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

what i did.
Flashed Draken TWRP System Image B06
Flashed Draken TWRP Stcok Recovery B06
Flashed full update.zip B08
Now my phone is recognized as A2017G on the PC
But when i reboot the phone i get a message that the phone is unlocked and not trusted ?
why ?

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!

Help! ([BOOTLOADER] image not signed or damaged)

I unintentionally skip the "format data" link and the all step, so the code unlock the bootloader but I cant flash the recovery it says "[BOOTLOADER] image not signed or damaged", the phone works but I cant flash anything, any ideas?

What device do you have, what (stock) firmware do you have on the device and what firmware are you trying to flash?

Hello is a stock Moto G5 Plus with 7.0 android and I am trying to flash the Vanche's Modified TWRP or the 3.1.2 version but I keep getting the same message "[BOOTLOADER] image not signed or damaged", is like if the BL relock itself.

I think that's a standard warning from the bootloader - TWRP is not signed software, which fastboot expects. However, as your bootloader is unlocked, it'll allow the flashing of TWRP, just with the warning message alerting you to the fact you're not flashing Motorola firmware via fastboot.
1)Do you see [OKAY] appear when you flash the TWRP?
2)After flashing TWRP, do you boot to recovery to fix TWRP? Easiest way is after flashing, on your device (if still in the device bootloader), use the volume keys to select 'Recovery' and press Power to confirm.
The instructions here suggest you need to boot to recovery after flashing to fix TWRP as the recovery, else the stock recovery may overwrite TWRP. https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659 or https://forum.xda-developers.com/g5-plus/how-to/how-to-how-to-supersu-moto-g5-plus-t3587684

ok thanks, I will try that, so skipping the "format data" thing has nothing to do with it?

I'm not sure - though you'd have to unlock your bootloader so your data would be wiped anyway as part of the unlock, and that you'll have to decrypt your data. Perhaps someone with more experience in flashing on G5 plus devices can comment.

Help: Boot loader locked, recovery and OS won't boot

I'm wondering how bad I've messed this up. I have a new LEX727 that had Stock EUI 5.8.21 on it. I enabled developer mode and allowed OEM unlocking in the OS. I then booted into download mode, unlocked the bootloader, and flashed TWRP recovery 3.2.1-1. After that, I couldn't boot into recovery any longer. I tried the process over and over again with different version s or TWRP and I still couldn't boot into recovery.
The next thing I tried is a went into download mode, issued the command fast boot format userdata (my partition was encrypted so I needed to do this) and then fastboot boot <twrp.img> and booted into recovery. In recovery, I mounted the system partition, and then I installed the latest Lineage OS image. I reboot, saw the splash screen, and then nothing.
I rebooted back into download mode and tried to boot with "fastboot boot <twrp.img>" again but now my bootloader is locked again.
So, if you are keeping tally, my bootloader is locked, my recovery won't boot, and I don't have a working operating system. How bad is that? Any way to recover?
Thanks
Cymerej

Fastboot doest work with locked bootloader.
What process did you use to unlock bootloader?
Just make sure you have a 727.
Did you reformat data in twrp?
Sent from my SM-A730F using xda premium

mchlbenner said:
Fastboot doest work with locked bootloader.
What process did you use to unlock bootloader?
Just make sure you have a 727.
Did you reformat data in twrp?
Click to expand...
Click to collapse
Thanks for the response, mchlbenner. Yes, fastboot does work, but it doesn't allow me to flash recovery because the boot loader is locked. It gives me an error message when I try. Do you know how I can use fastboot to restore to factory image?
To unlock the boot loader I followed these steps:
1. Booted into stock Android
2. enabled developer mode (pressed on the build number 7 times)
3. went into the developer options and made sure the USB debugging and allow boot unlock were enabled
4. rebooted into download mode
5. ran the command "fastboot oem unlock-go" which said it was successful
I am positive I have a 727
No, I didn't reformat the data in twrp. I reformatted it in fastboot with the command "fastboot format userdata".

You will have to flash this bootloader.
You have to read how to do this.
You have to reformat data in twrp
https://www.mediafire.com/file/nvsw2fhnt1e2q7d/x727-5.8.019s_bootloader-unlock.zip
Sent from my SM-A730F using xda premium

Its fixed, Thanks for help.
I was able to get my phone up and running again using the instructions in this thread:
https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
Thanks for the help.
-Cymerej