[GUIDE][A2017G] Reinstall TWRP and Root after update to Nougat

[dnlilas]

Hello,
There is a point I did not understand well.

Question: "get Fastboot" to work : Does it mean "unlock bootloader"?
If yes, then this guide does show how to unlock the bootloader (and so the OP should be changed to mention it).
If no, then what are the advantages of getting fastboot to work ?

 

[Choose an username...]

Hello,
There is a point I did not understand well.

Question: "get Fastboot" to work : Does it mean "unlock bootloader"?
If yes, then this guide does show how to unlock the bootloader (and so the OP should be changed to mention it).
If no, then what are the advantages of getting fastboot to work ?

Don't you guys know how to read?

 

[Choose an username...]

Hello,
There is a point I did not understand well.

Question: "get Fastboot" to work : Does it mean "unlock bootloader"?
If yes, then this guide does show how to unlock the bootloader (and so the OP should be changed to mention it).
If no, then what are the advantages of getting fastboot to work ?

Okay enough with that , fastboot is very useful if you need to flash stuff or lock your bootloader. Can get you out of a major shïtstorm.

Fastboot =/= bootloader unlock! You unlock the bootloader with Fastboot, but that is just one operation that you can do.

 

[dnlilas]

@Choose an username...
Thank you for your explanation.
Since now we can directly goes from stock Marshmallow A2017GV1.0.0B10 to stock Nougat A2017GV1.2.0B04
using update.zip provided by ZTE ( https://forum.xda-developers.com/showpost.php?p=72193661&postcount=121),
if your guide could aslo include the way to unlock the bootloader it would be very useful.
We have already such guide ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ),
but it addresses only stock Marshmallow owners. We need similar guide like yours for stock Nougat owners.

From what I understand, once fastboot worked in stock Nougat, we can use it to unlock bootloader, flash TWRP, and make root
easily in a row by typing:

adb reboot bootloader (to enter fastboot mode)
then:
fastboot devices (optional, just to check connection)
fastboot flash recovery twrp_rec_tenfar.img
Inside TWRP: upgrade to latest TWRP, reboot in TWRP, then flash supersu2.79
reenter fastboot mode: adb reboot bootloader
fastboot oem unlock (to unlock bootloader, then follow phone indication)

Are the above steps correct?

 

[SilentEYE]

I have a problem after flashing stock B04 rom. I don't know how to solve this.
I flashed the B04 Bootstack, then the B04 Rom, afterwards dm-verify and supersu on TWRP 3.1
After that, I got the TWRP message that there is no OS installed. I skipped that warning and now I cant boot only into Stock android recovery, into the (device unlocked) stock screen or into EDL (Vol buttons + power)

MiFlash does not work on QBulk or DFU mode.
By trying the axon7tool commands in DFU I got the device not connected error.
On Windows Device Manager the device is shown as Qbulk or DFU mode, depending on Zadig.

 

[Choose an username...]

I have a problem after flashing stock B04 rom. I don't know how to solve this.
I flashed the B04 Bootstack, then the B04 Rom, afterwards dm-verify and supersu on TWRP 3.1
After that, I got the TWRP message that there is no OS installed. I skipped that warning and now I cant boot only into Stock android recovery, into the (device unlocked) stock screen or into EDL (Vol buttons + power)

MiFlash does not work on QBulk or DFU mode.
By trying the axon7tool commands in DFU I got the device not connected error.
On Windows Device Manager the device is shown as Qbulk or DFU mode, depending on Zadig.

I bricked my device after rebooting without a system installed. not sure why it breaks so much when you do that.

i guess you tried MiFlash with Qualcomm HS-USB QDLoader 9008 drivers huh?

If you can boot into the stock recovery then you can flash an official zip. maybe you can flash B10 or B11

 

[SilentEYE]

I bricked my device after rebooting without a system installed. not sure why it breaks so much when you do that.

i guess you tried MiFlash with Qualcomm HS-USB QDLoader 9008 drivers huh?

If you can boot into the stock recovery then you can flash an official zip. maybe you can flash B10 or B11

Thank you for your reply.
I solved this problem after 6 hours.

Here is my solution, for other users.
https://forum.xda-developers.com/showthread.php?p=72217175

The only thing I still don't understand is :
Why does the stock rom stuck in a boot loop if you delete every Google app.( with file explorer or twrp)
You can hear the click of the front camera lens continuously on boot screen.

I think I managed this once by installing a permissive kernel. After boot success a enforcing custom kernel is working fine.

 

[sk0o]

/delete

 

[Choose an username...]

I finally find a way to fix the axon 7 tool for me on 7.1.1 b04 A2017G. the guides says "Put axon 7 tool on your adb folder, rename it too axon 7 tool.exe" but when I did this nothing worked. I change the filename to axon 7 tool without .exe and it worked

New problem:
C:\adb>axon7tool -w recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Writing recovery ...
F: failed to open recovery.bin
terminate called after throwing an instance of 'std::runtime_error'
what(): error: No error

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

You're only confusing people by posting this...

I'll add that you need to have file extension shown before attempting this

And that error is maybe because there is no recovery.bin there, or because you renamed it from

TWRP-x.x.x-x
to
recovery.bin

If that is the case then you should activate show file extensions, then change the name from

TWRP-x.x.x-x.img
to
recovery.bin

Windows should warn you that the file can get unusable, that's BS in this case so disregard.

Do you recall Windows ever warning you about that?

 

[sk0o]

You're only confusing people by posting this...

I'm sorry, everything is working fine now and I have twrp installed. Sorry for the confusion.

 

[Choose an username...]

I'm sorry, everything is working fine now and I have twrp installed. Sorry for the confusion.

But what was it then???

 

[sk0o]

But what was it then???

Dunno, switched from my desktop to my laptop and redownload all the files fresh again. After that it worked instantly. Thanks for all your hard work.

 

[Choose an username...]

Dunno, switched from my desktop to my laptop and redownload all the files fresh again. After that it worked instantly. Thanks for all your hard work.

Okay thanks :good: I'll change the guide to use @djkuz 's MiFlash TWRP file though. It will be much better since I use MiFlash on the same guide

 

[alidavarzani]

Hi Dear zte company First of all my axon build number was A2017 b07,then i upgraded it to global version through out this(ztedevice.com/support/detail?id=CF924E214F0D466A9712B8F09523F0CF]) Link. Everything was ok by this version and it worked well.then i just enhance my phone to nougat version through out this(ztemobile.de/support/downloads/?product_id=2100#)link.unfortunately[/url] after this upgrading the sim doesn't work .it can be detected by axon however the sim s antenna is empty. Through out these problems i decided to downgrade it to the global version as zte suggestion but the sim s antenna is empty in this version too.it should be mentioned that before these actions there was no problem with this version.(my carrier service is mtn irancell and ir-tci ).i will really appreciate you if you answer me as soon as possible. With best of regards, Thanks.

i have sent it to zte but they did not respond. i wanted to flash my phone in case that may be fixed , but after i disconnected cable BEFORE THE COUNTDOWN ENDS and after the holding the power button for like an eternity until the phone reboots, it can not boot to TWRP or neither stock one. right now i downgraded to marshmallow A2017G B10 .cause i have the same problem as you(not detecting QUSB BULK but detecting qualcomm) i fallowed this thread.i knew that this thread will work for nougat but cause i already did all the steps by this thread ' [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM ' but it could not work i decided to try this one.

please help me!! pleeeeease i will appreciate you.

---------- Post added at 12:28 PM ---------- Previous post was at 12:06 PM ----------

i forgot one thing , when i did this 'Finally, on the CMD window, run axon7tool -w recovery. If it fails try holding the three buttons, opening cmd again and trying this step again. ' (i failed and did holding the three buttons) , then i wrote axon7tool -w recovery in cmd but it responded 'device not detected' and then i turn the phone on and i typed ' adb reboot edl' and then again i run' axon7tool -w recovery' and it did! before countdown i unplugged cable but in recovery mode nothing monitored' neither stock bootloader nor twrp.

pls read it for explaining problem without details.
after i run 'axon7tool -w recovery' my phone restarted and when i hold volume up and power nothing have appeared to screen. it means nor TWRP or stock recovery mode exists. when i wanted to reset factory nothing will be done because of lack of recovery mode.
please help me. i should notice that my bootloader is locked and also i should mention that i already updated my phone to nougat and then i downgraded to marshmallow again(a2017g b10)

 

[derfinsterling]

Thanks for the guide - but I didn't get it to run.
It was very helpful in getting "back" to the QUSB_BULK driver stage, but anytime I try to execute the axon7tool, I just get "Failed to connect". I seem to be in EDL mode, but can't execute anything. When booting up, I can see it listed in adb devices and I can boot to the stock recovery. But beyond that... no luck.

Any advice?

 

[Choose an username...]

Thanks for the guide - but I didn't get it to run.
It was very helpful in getting "back" to the QUSB_BULK driver stage, but anytime I try to execute the axon7tool, I just get "Failed to connect". I seem to be in EDL mode, but can't execute anything. When booting up, I can see it listed in adb devices and I can boot to the stock recovery. But beyond that... no luck.

Any advice?

How did you get to EDL mode? Via 'adb reboot edl'?
Cam you boot to system? Are you using an USB port on the front of the PC? (Disregard if you're using a laptop)
And did you try axon7toolkit? It should be able to help you, at least if you could boot to system. You can flash an official zip through the stock recovery and try with it. this guide is pretty old

 

[derfinsterling]

How did you get to EDL mode? Via 'adb reboot edl'?
Cam you boot to system? Are you using an USB port on the front of the PC? (Disregard if you're using a laptop)
And did you try axon7toolkit? It should be able to help you, at least if you could boot to system. You can flash an official zip through the stock recovery and try with it. this guide is pretty old

Yes - I can boot to system va adb reboot edl. The device still shows up on device manager (took me a while to figure out that there was no other indication that my phone was actually still on...)
It reboots fine into system from EDL when I long-press the power button. However: When I'm in EDL and enter on the command line

axon7tool -r recovery gpt boot

All I get is "Failed to connect to Device"

I tried multiple re-starts, different usb ports on my laptop... I'm stumped. I'm not a complete novice on this, I have successfully played around with almost every phone I owned, installed custom roms, bricked and unbricked a couple of them... But I never ran into a phone that would as stubbornly refuse to let me have my way with it

 

[onehellofawhat]

after working on it for 8+ hours i have managed to get everything working. except this two...
cant update LOS 14.1 (installed the one on this thread)
cant update twrp (3.0.3.0.)
what do i do now?

 

[Choose an username...]

after working on it for 8+ hours i have managed to get everything working. except this two...
cant update LOS 14.1 (installed the one on this thread)
cant update twrp (3.0.3.0.)
what do i do now?

i think you're on the wrong thread, there's no LOS here.

To update TWRP just go to the download center on the Guides section, download the latest TWRP.img (3.1.1-0 i think) and put it on the internal storage. go to TWRP, Install, Install image, select the .img, select install to recovery, install, and voila

 

[onehellofawhat]

i think you're on the wrong thread, there's no LOS here.

To update TWRP just go to the download center on the Guides section, download the latest TWRP.img (3.1.1-0 i think) and put it on the internal storage. go to TWRP, Install, Install image, select the .img, select install to recovery, install, and voila

yeah wrong thread sorry.
also i tried that but i remember it gave an error, then i couldnt enter bootloader again. so i had to revert all of it by writing "adb push ..." it doesnt download from the official app and supersu says its occupied.