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

Tuamor

New member
Apr 9, 2017
4
1
0
I managed to flash correctly using miflash. But when I tried to install twrp using axon7tool, it says that my fastboot device is not connected. Any advice?
 

Choose an username...

Senior Member
Oct 16, 2016
2,677
923
0
I managed to flash correctly using miflash. But when I tried to install twrp using axon7tool, it says that my fastboot device is not connected. Any advice?
I've had a new problem with this method, after updating to B02. MiFlash seems to flash the fastboot image but it doesn't work. I assume that your phone just booted to the system when axon7toolkit said it didn't find fastboot... that's what happens in my phone

What you can try is:
-Download axon7tool from tennear here
-Put it in C:/, and also get TWRP 3.1 and rename it to recovery.img, then duplicate it and rename the copy to recovery.bin (BE SURE that your Windows shows the file extensions, otherwise google how to make it show them), then put both files in C:/
-Fire up CMD, then adb reboot edl, then see if your device appears listed under Ports (COM & LPT) on the Device manager, as Qualcomm HS-USB QDloader 9008 or as a device with a yellow warning sign. If it does do this:
  • (Skip this step if it appears like a yellow warn sign) right click on it, click Uninstall, then check Uninstall driver software too (I think it was called like this), then OK
  • Download Zadig
  • Hold the 3 keys (vol +/-, power) at the same time until you see the red notification light on the phone or until the device manager flickers and shows a new device
  • Use Zadig to install the missing driver
-Okay, now you have it as Universal Serial Bus devices. Now hold the 3 buttons again until the light appears or Device manager flickers
-Get CMD again and write cd.. as many times as you need to until you get to C:/
-Now write axon7tool -w recovery, hit Enter/return, and pray
After it finishes flashing (hopefully) a Success! Rebooting in 5, 4, 3 will appear. I heard somewhere that you had to unplug the device before the countdown ended, then restart it manually, because twrp would get replaced or whatever. I did that and it worked. Do or do not, it's your choice. i didn't have time to test

I'll have to modify the guide a lot and add all this stuff later - for now it stays like this
 
Last edited:
  • Like
Reactions: tuiyaan and nsabir

Choose an username...

Senior Member
Oct 16, 2016
2,677
923
0
@Choose an username...
As far as I know the partition layout on the A2017G is different from the one on the A2017U.
Is this still considered safe? I would do it only to get fastboot running as I am already unlocked.
Look, I've done it 4 times already, no problems whatsoever. A lot of people have also tried. But the only thing you have to be aware of is that the method in the OP probably won't work if you're on Nougat B02. If that's the case you'll have to forget Fastboot for now and flash the recovery directly with axon7tool, which I don't like because axon7tool is too finicky and may or may not work

This method will not unlock your bootloader (i think), it is just to get Fastboot. But you won't get it on B02
 

sToRm1nG

Senior Member
Oct 24, 2013
558
354
63
Near Zurich
Look, I've done it 4 times already, no problems whatsoever. A lot of people have also tried. But the only thing you have to be aware of is that the method in the OP probably won't work if you're on Nougat B02. If that's the case you'll have to forget Fastboot for now and flash the recovery directly with axon7tool, which I don't like because axon7tool is too finicky and may or may not work

This method will not unlock your bootloader (i think), it is just to get Fastboot. But you won't get it on B02
Thanks for the clarification.

In regards to B02, fastboot partition is not touched by the update, so maybe you can still have fastboot after upgrading to B02 when applied at B01. I agree with you that it would be a bit risky to apply it on B02.
 
Last edited:

Choose an username...

Senior Member
Oct 16, 2016
2,677
923
0
Thanks for the clarification.

In regards to B02, fastboot partition is not touched by tje update, so maybe you can still have fastboot after upgrading to B02 when applied at B01. I agree with you that it would be a bit risky to apply it on B02.
Well I flashed the fastboot package like an hour ago, and I couldn't access fastboot. Pity that I did a full reinstall. I might still have fastboot if i didn't
I don't know if it's risky though. Maybe backing up then restoring the fastboot partition would do the trick?
 

sToRm1nG

Senior Member
Oct 24, 2013
558
354
63
Near Zurich
Well I flashed the fastboot package like an hour ago, and I couldn't access fastboot. Pity that I did a full reinstall. I might still have fastboot if i didn't
I don't know if it's risky though. Maybe backing up then restoring the fastboot partition would do the trick?
That's very unfortunate...
I'm not sure if this will solve it since there is no fastboot.img nor a fastboot.img.p inside the OTA. It's a pitty that ZTE does everything to prevent us from doing what XDA users are supposed to do, fastbooting the s*** out of our devices. :(
 

Choose an username...

Senior Member
Oct 16, 2016
2,677
923
0
That's very unfortunate...
I'm not sure if this will solve it. It's a pitty that ZTE does everything to prevent us from doing what XDA users are supposed to do, fastbooting the s*** out of our devices. :(
well said

A friend bought an OP3T, wanted my help rooting it. I literally did fastboot oem unlock and just flashed superSU...
 

sToRm1nG

Senior Member
Oct 24, 2013
558
354
63
Near Zurich
1.2.0B02 stock
Unfortunately, it seems that this is no longer working on V1.2.0B02
This method will not unlock your bootloader (i think), it is just to get Fastboot. But you won't get it on B02
You would have to downgrade to V1.2.0B01

*EDIT*
I guess I know why it is no longer working on V1.2.0B02
Here an extract from the updater-script:
Code:
[..]
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/aboot:755496:0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08:763772:5e2c84f772691ae91f258228910c3f6dbeb21950", "0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08", "5e2c84f772691ae91f258228910c3f6dbeb21950") || abort("E3005: \"EMMC:/dev/block/bootdevice/by-name/aboot:755496:0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08:763772:5e2c84f772691ae91f258228910c3f6dbeb21950\" has unexpected contents
[..]
ui_print("Patching emmc_appsboot.mbn image...");
apply_patch("EMMC:/dev/block/bootdevice/by-name/aboot:755496:0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08:763772:5e2c84f772691ae91f258228910c3f6dbeb21950",
            "-", 5e2c84f772691ae91f258228910c3f6dbeb21950, 763772,
            0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08,
            package_extract_file("patch/emmc_appsboot.mbn.p")) ||
    abort("E3008: Failed to apply patch to EMMC:/dev/block/bootdevice/by-name/aboot:755496:0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08:763772:5e2c84f772691ae91f258228910c3f6dbeb21950");
[..]
aboot is an essential part to get fastboot to run.
 
Last edited:

sToRm1nG

Senior Member
Oct 24, 2013
558
354
63
Near Zurich
Sorry that message was for the other guy

I have 0 knowledge on coding. No idea how you can fix this. If someone fixes whatever there is to fix I'll update the guide
Sure no problem. :)
I quickly made a "downgrade" flashable zip to downgrade aboot image to V1.2.0B01 if somebody is willing to test it: https://www.androidfilehost.com/?fid=673368273298947023

I am not accountable for the potential loss of data or the potential bricking of the device experienced by flashing this zip file!

*EDIT*
If it is not working use this zip file to restore aboot to V1.2.0B02: https://www.androidfilehost.com/?fid=457095661767153575
 
Last edited:
  • Like
Reactions: wineds