Database Users

Upgrade to newer build after rooting with locked BL?

Some background on what I've done with the phone:
It came with B29 on it.
I used DrakenFX's BootStack and System files to downgrade it to B27
From there, I tried the steps in Tenfar's thread to root the phone without unlocking the boot loader.
I screwed something up along the way and after many hours, got my phone booting properly again and downgraded to B20.
From there, I followed the steps posted by mmamedov in tenfar's thread to actually get my phone rooted properly.
I'm pretty new to rooting and all this stuff since I'm jumping ship from iPhone, but I've done a bit of tinkering.
I don't quite understand where the "root" part resides and what updates would affect it.
Now, I'm on B20 but would like to upgrade to some of the newer versions. What are my options for doing that and would I have to wipe the phone to update?
Could I use the backup tool to flash the stock recovery instead of TWRP, and use the built in update through settings?
Or should I use TWRP and DrakenFX's newer BootStack/System files to update?
or something else?
Thanks
- Android Newbie

mozerxdaven said:
Some background on what I've done with the phone:
It came with B29 on it.
I used DrakenFX's BootStack and System files to downgrade it to B27
From there, I tried the steps in Tenfar's thread to root the phone without unlocking the boot loader.
I screwed something up along the way and after many hours, got my phone booting properly again and downgraded to B20.
From there, I followed the steps posted by mmamedov in tenfar's thread to actually get my phone rooted properly.
I'm pretty new to rooting and all this stuff since I'm jumping ship from iPhone, but I've done a bit of tinkering.
I don't quite understand where the "root" part resides and what updates would affect it.
Now, I'm on B20 but would like to upgrade to some of the newer versions. What are my options for doing that and would I have to wipe the phone to update?
Could I use the backup tool to flash the stock recovery instead of TWRP, and use the built in update through settings?
Or should I use TWRP and DrakenFX's newer BootStack/System files to update?
or something else?
Thanks
- Android Newbie
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2 rooting makes the OTA from ZTE not work

I've been going through a similar learning curve as you I think.
I recommend @DrakenFX's nearly stock rom.
You will need to unlock the bootloader (I'm pretty certain) I believe that is covered and/or linked in the rom's page.
If it doesn't make sense keep reading until it does, is the advice I gave to myself.
I'm pretty new to certain parts of all the options involved in rooting and bootloaders etc. but I believe that the bootloader can be relocked if you don't get it officially unlocked and you do it yourself, I haven't confirmed that yet so don't take my word for it.
I ran into confusion when I unlocked and had driver issues with fastboot but I got there.
DrakenFX had a few posts that are really helpful. I used his B29 image and bootstack after I had TWRP installed.
He has another TWRP unlock zip that allows unlocking with ADB and then fastboot.
I ran into issues like I said and posted in his bootstack thread if you'd like to see if my problems might shed some light. My post didn't prompt any meaningful conversation but my driver issues sorted themselves out so I didn't have to pursue it much further.
Sorry for the lack of links but I hope this helps in some way.
Here's the ROM from DrakenFX that is close to stock B29, it looks like it will evolve into Nougat, can't wait for that.
http://forum.xda-developers.com/axon-7/development/rom-zaxon-dmix7-stock-base-rom-t3495970

b25 Update

I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance

2CanSan said:
I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
Click to expand...
Click to collapse
It's really simple actually: if you install B15 your data will be wiped, after that just skip everything and update to B29 (is B29 the latest? I have a G, dunno) and then use it. What you describe is not the actual performance that it should have, it's your specific case obviously.

I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery

tabletalker7 said:
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
Click to expand...
Click to collapse
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.

2CanSan said:
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
Click to expand...
Click to collapse
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.

tabletalker7 said:
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
Click to expand...
Click to collapse
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.

2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.

2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Choose an username... said:
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
Click to expand...
Click to collapse
OK on the A2017U units you need the official marshmallow B29 package to roll back, and that only works with stock recovery on a clean B15 N install. The Rollback package I told you to use earlier will roll you back to B29 marshmallow NO MATTER WHAT YOU ARE USING (I have used this a lot, and OBVIOUSLY there are differences between the the A2017U version in North America and the A2017G version in Europe). If you want stock and rooted, I personally recommend B29 marshmallow over B15 Nougat, but either way go for it (I think the marshmallow had a much better radio than any of the Nougat packages). If you are interested in TWRP and root, I found B29 marshmallow much easier for both, and the marshmallow version of android also gives you Xposed, but back to your first post, you mentioned wanting marshmallow, and this is the best way to get it.
Step by Step method
1. Roll back to B15. Use the update.zip method. It will factory reset your device so backup everything you can't lose
2. Use MiFlash to unlock and install TWRP - check that thread on XDA for instructions.
3. (If desired) In TWRP, install the B29 marshmallow rollback. Do not reboot into system afterwards.
4. (If step 3 is done) In TWRP, flash TWRP. The marshmallow rollback will overwrite recovery with stock recovery
If you do this you will have exactly what you wanted in your original post. I can personally tell you this works, as I have tried every custom rom on here and always wind up back at B29 marshmallow when all is said and done. It has never failed me, and it will never fail you either.

A2017U su binary not found after flashing supersu

Hi all
So it was all running nice and stable, before the evil b25 update that destroyed my axon 7 completely and made it useless, I'll tell how
so after updating I figured out I can't access fastboot to flash anything, and I figured out I wasn't the only one with this "meme" that zte made.
so I decided to roll back to b19 using Miflash and b19 edl package, I thought my problem would end here.
Then I flashed twrp via fastboot, and upgraded to b25 using b25 bootstack + b25 zip by drakenfx, all good.
then I tried to root b25 the good ol' way by flashing supersu zip, only to find that I'd end up with this newer meme, "unable to find su binary"
seems like the sort of thing you'd get if you had a locked bootloader, which is suspicious, judging that no one was able to get fastboot on b25
I also figured out I wans't the only one as people from "root b25" threads know that you can't root b25 even if you had twrp
so I rolled back again to b19 using miflash....you know the story
now here comes the interesting part, the meme, didn't go away, I tried to root my b19 a2017u by flashing supersu
I tried everything, flashing b19 bootstack, formatting data flashing different supersu versions etc.
, either ended up with a bootloop, or the famous "su binary is not installed"
I never had this before updating to b25 and now I can't get rid of it even without b25
can someone guide me to root stock b19 properly and get rid of this meme? (bonus if you know how to root b25 properly because I liked b25 more, there is a7x kernel for b25 so I guess we can root b25? maybe not? )
note that I don't want magisk, I just want the good ol' supersu, nothing more nothing less.
My opinion is the new b25 somehow messes the bootloader and now it's locked again, but this time you can't unlock it even if you downgrade and flash edl bootloader unlock via miflash.
guys, I think zte is just trolling us atm, you would not believe how much time I wasted flashing, I think my axon 7's nand is going to die soon.

First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79

buksua said:
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
Click to expand...
Click to collapse
Holding power and both volume keys at the same time for ~15 seconds (until the LED flashes) restarts EDL without actually having to get out y'kno.
Just saying

I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck

J0nhy said:
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
Click to expand...
Click to collapse
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
buksua said:
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
Click to expand...
Click to collapse
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.

J0nhy said:
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
Click to expand...
Click to collapse
UPDATE ON THE SITUATION:
It didn't... *sigh*
but...it worths to mention 1 thing I noticed after booting (regardless of supersu version flashed)
That su permissions get granted, but for a limited periods/times only, and then I get the "root undetected/su binary not found" error afterwords.
which was suspicious, so I ran "su" command in terminal emulator with the supersu you provided and this is what I got
ailsa_ii:/ $ su
WARNING: linker: /su/bin/sush: unused DT entry: type 0xaa1303e054ffff68 arg 0xaa1403e2d2800081
Basically a bunch of warnings like the one above, like a dozen of this line ending up with this specific note:
CANNOT LINK EXECUTABLE "sush": empty/missing DT_HASH/DT_GNU_HASH in "/su/bin/sush" (new hash type from the future?)
Im losing hope, but at the same time I think I found a thread, only need a dev to help me currently
I'll post this in supersu thread and see, maybe I get a helpful reply
I will also try changing to ext4 because I'm heavily doubting that the reason for all this is my use of f2fs on data partition only.

Ghostface009 said:
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
just like I said on the instruction you MUST check the mount system partition read-only before you flash
A2017UV1.1.0B25_bootstack_by_DrakenFX and A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip
If you when to keep TWRP after flashing Stock System, install SuperSU v.279
(reference)
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
maybe you didn't check the mount system partition read-only before you flash b25 was the problem in the first place.
If you can get your bootloader unlock again just try the method I've mention.
just read the instruction carefully step by step.
(note)
I've been going back and forth flashing different roms but ultimately I always have to come back to stock using the method I've mention. I have never use magisk unless it come with the rom.
I've always flash SuperSU after installing A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip with no problem.

buksua said:
just like I said on the instruction you MUST check the mount system partition read-only before you flash
A2017UV1.1.0B25_bootstack_by_DrakenFX and A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip
If you when to keep TWRP after flashing Stock System, install SuperSU v.279
(reference)
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
maybe you didn't check the mount system partition read-only before you flash b25 was the problem in the first place.
If you can get your bootloader unlock again just try the method I've mention.
just read the instruction carefully step by step.
(note)
I've been going back and forth flashing different roms but ultimately I always have to come back to stock using the method I've mention. I have never use magisk unless it come with the rom.
I've always flash SuperSU after installing A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip with no problem.
Click to expand...
Click to collapse
I can't 100% confirm that I tried this before, but I assure you I
tried most of possibilities like this, including step by step follow up of drakenfx's guide.
I may try later, but not now, that takes a lot of time and my a2017u's nand is dying of repeated flash :crying:
but lemme ask you, can/could you access fastboot on b25 stock??

Ghostface009 said:
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
Ghostface009 said:
I can't 100% confirm that I tried this before, but I assure you I
tried most of possibilities like this, including step by step follow up of drakenfx's guide.
I may try later, but not now, that takes a lot of time and my a2017u's nand is dying of repeated flash :crying:
but lemme ask you, can/could you access fastboot on b25 stock??
Click to expand...
Click to collapse
no fastboot on b25 but fastboot on b19
remember to flash B19-NOUGAT_FULL (Nougat 7.1.1) first than VERY IMPORTANT part is to flash B19-NOUGAT_TWRP (Nougat 7.1.1) right after.
just do step 1 and 2.
don't flash b25 yet if you want fastboot
if you want b25 and b25 root just follow step 3

buksua said:
no fastboot on b25
Click to expand...
Click to collapse
Yeah, not a big surprise
and I'll try everything later when I get enough time, but for now I look for a firmware flash-free method because I don't want to kill the ufs.

UPDATE FOR EVERYONE:
I FINALLY GOT SUPERSU WORKING (atleast this far)
sadly f2fs was the reason behind this error
Special thanks for @J0nhy
for providing the correct supersu version to flash :3

Ghostface009 said:
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
The file is no longer available through this link... is there another source?

zachstarmer said:
The file is no longer available through this link... is there another source?
Click to expand...
Click to collapse
wew, It's been a long time since my last login here.
afaik it was 2.79 su.
But why you're still on b25 when you can flash newer firmware? when I flashed b32 via edl, I got rid of all these probs (except f2fs, because zte decided that their stock firmware only supports ext4 )
I got fastboot and everything, root xposed etc, if you want the edl package you can search it in drakenfx's androidfilehost account :good:
make sure to backup internal storage manually and backup apps with TB for restoring after edl-flashing b32. I also suggest updating to b35 before rooting and restore since b32 was helluva buggy update

This is exactly why I won't run ZTE's stock ROM, it seems that only Magisk works on B32 and beyond. I have grown to hate Magisk over the years, due to a number of bad experiences with it on various ROMs/devices. On stock, Magisk makes my exFAT SD appear as corrupt, I refuse to format to vfat, fat32. I tried Phh's Superuser and SuperSU, either the device won't boot or I get errors about su not being available. So it's custom AOSP-based ROMs only for me. Which are far superior to stock in most ways.

Help installing TWRP as zip file (no go through Fastboot)

I downgraded from custom Nougat to stock Marshmallow as I discovered that the incall sound (hearing the caller from the ear speaker) is louder and clearer, so of course I lost TWRP recovery and root in the process which is normal. However, I now can't re-install TWRP as a .img file since although I can boot into Android Recovery I can't go into Fastboot mode (phone just re-starts every time) so of course it's no go whether I try Axon Toolkit or ADB via computer. I also tried the EDL route but same thing.
I have all the required ZTE and Qualcom drivers installed. My phone's model is the 2017G and the bootloader is still unlocked.
Only thing I can try is installing TWRP as a zip file through Android Recovery or directly from 'system update' via the phone's menu. Problem is I can't find a zip version of TWRP for the Axon 7
Any help/suggestions most grateful.

xectis said:
I downgraded from custom Nougat to stock Marshmallow as I discovered that the incall sound (hearing the caller from the ear speaker) is louder and clearer, so of course I lost TWRP recovery and root in the process which is normal. However, I now can't re-install TWRP as a .img file since although I can boot into Android Recovery I can't go into Fastboot mode (phone just re-starts every time) so of course it's no go whether I try Axon Toolkit or ADB via computer. I also tried the EDL route but same thing.
I have all the required ZTE and Qualcom drivers installed. My phone's model is the 2017G and the bootloader is still unlocked.
Only thing I can try is installing TWRP as a zip file through Android Recovery or directly from 'system update' via the phone's menu. Problem is I can't find a zip version of TWRP for the Axon 7
Any help/suggestions most grateful.
Click to expand...
Click to collapse
If you can use miflash there is a thread somewhere that has stock everything with twrp included. I'm on my phone so I can't find it right now. But if you can't find it by the time I get to my computer I'll look through my history to try and find it.

JTruj1ll0923 said:
If you can use miflash there is a thread somewhere that has stock everything with twrp included. I'm on my phone so I can't find it right now. But if you can't find it by the time I get to my computer I'll look through my history to try and find it.
Click to expand...
Click to collapse
Thanks for the response. I looked around for the thread you mentioned but had no luck in finding it yet but I'll keep looking meantime.
Thanks

xectis said:
Thanks for the response. I looked around for the thread you mentioned but had no luck in finding it yet but I'll keep looking meantime.
Thanks
Click to expand...
Click to collapse
So the thread I found was actually not for the g model sadly. But, have you seen this thread?
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547/page10
Down a ways there is a "TWRP flashable bootstack/stock system images" section. I think if you can flash those (maybe with miflash?) You should then have fastboot available to flash twrp again.

When you unlocked surely you learned how to use the tools to flash twrp without fastboot.
You can use miflash, the toolkit, tenfar's tool or tenear's tool.
There's a million and one guides on how to to this plus the actual tool threads.
Even the twrp thread has a guide.

JTruj1ll0923 said:
So the thread I found was actually not for the g model sadly. But, have you seen this thread?
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547/page10
Down a ways there is a "TWRP flashable bootstack/stock system images" section. I think if you can flash those (maybe with miflash?) You should then have fastboot available to flash twrp again.
Click to expand...
Click to collapse
I took a look. Not sure which version I should download. Am on B10 and that section only has bootstack versions up to B9. Does it matter which one I choose or should I get the closest which is B9. Also, should I install the stock system that goes with the bootstack version or just the bootstack.
Thanks for the link.

xectis said:
I took a look. Not sure which version I should download. Am on B10 and that section only has bootstack versions up to B9. Does it matter which one I choose or should I get the closest which is B9. Also, should I install the stock system that goes with the bootstack version or just the bootstack.
Thanks for the link.
Click to expand...
Click to collapse
Okay so since I was not paying that much attention (sorry) I just realized that those are bootstacks and stock systems that you can flash in TWRP. My bad. But I have been looking around and on that thread I just had you go to he mentions another thread with step by steps that may help you! Here it is. Good luck!

xectis said:
I took a look. Not sure which version I should download. Am on B10 and that section only has bootstack versions up to B9. Does it matter which one I choose or should I get the closest which is B9. Also, should I install the stock system that goes with the bootstack version or just the bootstack.
Thanks for the link.
Click to expand...
Click to collapse
JTruj1ll0923 said:
Okay so since I was not paying that much attention (sorry) I just realized that those are bootstacks and stock systems that you can flash in TWRP. My bad. But I have been looking around and on that thread I just had you go to he mentions another thread with step by steps that may help you! Here it is. Good luck!
Click to expand...
Click to collapse
Ignore the fastboot part. Just reinstall twrp with axon7tool, then install raystef66's TWRP flashable B09 bootstack and stocksystem zips (plus magisk if you won't relock), then follow his guide on how to get rid of the 5 seconds screen to get fastboot and, well, get rid of the 5 seconds screen
p.s. I basically just found out that I said the exact same thing on that crappy Q&A thread...

Choose an username... said:
Ignore the fastboot part. Just reinstall twrp with axon7tool, then install raystef66's TWRP flashable B09 bootstack and stocksystem zips (plus magisk if you won't relock), then follow his guide on how to get rid of the 5 seconds screen to get fastboot and, well, get rid of the 5 seconds screen
p.s. I basically just found out that I said the exact same thing on that crappy Q&A thread...
Click to expand...
Click to collapse
The link you provided is titled 'Get TWRP and root after updating to Nougat'. As am on Marshmallow I'll have to first update to Nougat? . So do I go ahead and flash stock Nougat from ZTE's page before following the instructions on that page? Sorry for my confusion.
**Update** I followed instructions of link you provided to install TWRP but I came to a brick wall every time. Short story is no matter what I tried I cannot install anything with either ADB, Miflash or Axon Toolkit. The big problem here is the Fastboot issue which otherwise would make things so much easier. Only thing left for me to do is just to upgrade stock firmwares via the phone's update option and remain bootloader unlocked. The Axon 7 is still a great phone, it's just too much hustle getting things done so I'll just have to sell it. Samsung and HTC phones are much easier to work with when it comes to rooting/installing custom ROMs.
***Update 2*** Success!! I managed to install fastboot/bootloader mode by following the section 'Get Fastboot' from that same link you provided so now I have latest TWRP installed and the 5 second notice has also disappeared. Am back in the running now. Many thanks for your help

xectis said:
The link you provided is titled 'Get TWRP and root after updating to Nougat'. As am on Marshmallow I'll have to first update to Nougat? . So do I go ahead and flash stock Nougat from ZTE's page before following the instructions on that page? Sorry for my confusion.
**Update** I followed instructions of link you provided to install TWRP but I came to a brick wall every time. Short story is no matter what I tried I cannot install anything with either ADB, Miflash or Axon Toolkit. The big problem here is the Fastboot issue which otherwise would make things so much easier. Only thing left for me to do is just to upgrade stock firmwares via the phone's update option and remain bootloader unlocked. The Axon 7 is still a great phone, it's just too much hustle getting things done so I'll just have to sell it. Samsung and HTC phones are much easier to work with when it comes to rooting/installing custom ROMs.
***Update 2*** Success!! I managed to install fastboot/bootloader mode by following the section 'Get Fastboot' from that same link you provided so now I have latest TWRP installed and the 5 second notice has also disappeared. Am back in the running now. Many thanks for your help
Click to expand...
Click to collapse
You could have bricked your device. I specifically told you not to follow that part. Also what has adb, axon7toolkit and miflash got to do with that guide? You have to use axon7tool just like a) it says there and b) i told you on the q&a thread

Choose an username... said:
You could have bricked your device. I specifically told you not to follow that part. Also what has adb, axon7toolkit and miflash got to do with that guide? You have to use axon7tool just like a) it says there and b) i told you on the q&a thread
Click to expand...
Click to collapse
Yes you did warn me about the fastboot part but I was stuck as nothing else worked. By using the Fastboot instructions I managed to install TWRP and root the phone. I used Miflash to install the fastboot package which was successful. Now I can boot to Fastboot and bootloader via TWRP. Remember am on Marshmallow so I guess that helped not to brick the phone? I don't know but it worked.

xectis said:
Yes you did warn me about the fastboot part but I was stuck as nothing else worked. By using the Fastboot instructions I managed to install TWRP and root the phone. I used Miflash to install the fastboot package which was successful. Now I can boot to Fastboot and bootloader via TWRP. Remember am on Marshmallow so I guess that helped not to brick the phone? I don't know but it worked.
Click to expand...
Click to collapse
Well again, if you want to be on Nougat, download raystef66's flashable B09 bootstack and stocksystem, flash them on TWRP with Magisk 15.2, and follow his guide on how to get rid of the 5 seconds screen (all in twrp, don't get out of it).
Just do all of that or you'll lose fastboot. Also that zip that you got from that ancient guide doesn't work on anything else than Marshmallow

Choose an username... said:
Well again, if you want to be on Nougat, download raystef66's flashable B09 bootstack and stocksystem, flash them on TWRP with Magisk 15.2, and follow his guide on how to get rid of the 5 seconds screen (all in twrp, don't get out of it).
Just do all of that or you'll lose fastboot. Also that zip that you got from that ancient guide doesn't work on anything else than Marshmallow
Click to expand...
Click to collapse
Thanks for the advice. If I keep the phone I'll wait for a stable Oreo update. Nougat didn't impress me much.

Help with Flashing a custom ROM ( absolute first time )

Hey guys, I wanted some help on flashing LineageOS 14.1 to my Axon 7 A2017G.
I've looked at a bunch of guides but they all seem outdated or way too confusing.
I tried to follow the guide under the "Axon 7 Toolkit " thread where there were some instructions on how to flash a rom for noobs and when going to test for fastboot, it says I don't have fastboot.
Tried to get fastboot by following some guide and using miflash but ended up doing something to my device where android asked for a password when i booted up, where as I didn't have a password and had to end up factory resetting my device. LOST ALL MY DATA
If someone could please give me a simple, easy to follow guide on how to unlock bootloader, and flash custom rom, I would be immensely grateful.
Also if there is a guide on how to restore back to stock rom and factory settings in case I need to send phone back to ZTE at any point that would also be helpful.
:good:

The toolkit guide is probably the easiest one.
Read the whole thread and try again.
Sent from my ZTE A2017U using Tapatalk

runninghamster said:
Hey guys, I wanted some help on flashing LineageOS 14.1 to my Axon 7 A2017G.
I've looked at a bunch of guides but they all seem outdated or way too confusing.
I tried to follow the guide under the "Axon 7 Toolkit " thread where there were some instructions on how to flash a rom for noobs and when going to test for fastboot, it says I don't have fastboot.
Tried to get fastboot by following some guide and using miflash but ended up doing something to my device where android asked for a password when i booted up, where as I didn't have a password and had to end up factory resetting my device. LOST ALL MY DATA
If someone could please give me a simple, easy to follow guide on how to unlock bootloader, and flash custom rom, I would be immensely grateful.
Also if there is a guide on how to restore back to stock rom and factory settings in case I need to send phone back to ZTE at any point that would also be helpful.
:good:
Click to expand...
Click to collapse
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.

Choose an username... said:
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Click to expand...
Click to collapse
I will try this today, thank you for your time in typing this

runninghamster said:
I will try this today, thank you for your time in typing this
Click to expand...
Click to collapse
Or try this tool to unlock your bootloader....way more advanced by the way thnx @djkuz
Just install the axon 7 drivers, this tool and....UNLOCK with ease :good:
Also all files to revert back to stock, flashing modem, recovery... etc are well discribed there. Just take a peek there...
Just another advice : do read all threads carefully, no matter what you're doing, do backup regularly and all will be OK :good:

raystef66 said:
Or try this tool to unlock your bootloader....way more advanced by the way thnx @djkuz
Just install the axon 7 drivers, this tool and....UNLOCK with ease :good:
Also all files to revert back to stock, flashing modem, recovery... etc are well discribed there. Just take a peek there...
Just another advice : do read all threads carefully, no matter what you're doing, do backup regularly and all will be OK :good:
Click to expand...
Click to collapse
Thank you so much, will try today!

Choose an username... said:
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Click to expand...
Click to collapse
Followed your steps and managed to unlock the bootloader successfully. Afterwards I tried to flash TWRP using the Axon Toolkit and this error appears. Have 0 clue why. A little help please.
View attached >>>
EDIT: nevermind, tried to boot into recovery and twrp booted, not sure why the error appeared though. thanks for the help!