[GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM

[keessonnema]

Updated the OP. As for your troubles with getting the tool to work / getting into EDL, I'm a bit at a loss why this happens to some of you.

To be honest, I'm in a tight situation myself since I managed to mess up my Cellular/IMEI. When/if I get that working again, I can assist you guys

You got the wrong link mate.

This is the working one: https://www.androidfilehost.com/?fid=385035244224406988
EDIT: hmm nvm, I don't think it's there. Idk why the link is down..

 

[Controllerboy]

You got the wrong link mate.

This is the working one: https://www.androidfilehost.com/?fid=385035244224406988
EDIT: hmm nvm, I don't think it's there. Idk why the link is down..

Haha. Yes, I noticed. I replaced it with a working link.

 

[Xadro]

Just to clarify:
On my A2017G with B08 tenfars recovery was the only one working prior to unlocking the BL. After it was unlocked, the official one also worked.
I think you can however also backup and restore stuff with tenfars TWRP, as long as it is only /system /data or maybe /cache. To that matter one usually would not need to backup anything else.
I myself restored /system once from a backup i made with tenfars and all is fine.

 

[keessonnema]

Just to clarify:
On my A2017G with B08 tenfars recovery was the only one working prior to unlocking the BL. After it was unlocked, the official one also worked.
I think you can however also backup and restore stuff with tenfars TWRP, as long as it is only /system /data or maybe /cache. To that matter one usually would not need to backup anything else.
I myself restored /system once from a backup i made with tenfars and all is fine.

So
1. unlocking bootloader witn tenfars recovery.
2. flashing official recovery after that to do whatever you want.

---------- Post added at 04:55 PM ---------- Previous post was at 04:42 PM ----------

For everyone that's stuck in edl mode because of axon7tool saying "Failed to connect" do the following:

1. Install Zadig 2.2 drivers if you haven't done before.
2. connect phone to pc and confirm it says QUSB_BULK in device manager
3. adb reboot edl
4. when in edl mode open zadig 2.2 again and install driver
5. It works now.

 

[le_cactus]

New TWRP for A2017G by DrakenFX is up @Controllerboy could you update the OP?

Why can't I find a link to that new TWRP? I can find the TWRP_A2017G.B08.StockSystem_By_DrakenFX zip, but isn't there just a new recovery?


The OP still has a twrp-3.0.2-2-a2017u.img and I can't believe that would be a new official twrp voor the 2017g.


Thanks in advance,


Cheers,
/Cacti

 

[dprimic]

Why can't I find a link to that new TWRP? I can find the TWRP_A2017G.B08.StockSystem_By_DrakenFX zip, but isn't there just a new recovery?


The OP still has a twrp-3.0.2-2-a2017u.img and I can't believe that would be a new official twrp voor the 2017g.


Thanks in advance,


Cheers,
/Cacti

https://twrp.me/devices/zteaxon7.html

 

[martku]

Nice work with this thread: thanks a lot for collecting all informations.

1. The link to the twrp did not work any more.
2. I got stuck on step 16: the backup of the device. The command "axon7tool -r gpt boot recovery" always displays (Win10 x64):

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.

I also tried installing other drivers (additionally with disable the automatic installation of them) and/or replace them with Zadig, but I have not found a solution. The hardware manager displays the device as "QUSB__BULK" without a warning.

By the way: The device is a 2017G B05 and this is not the "Failed to connect" error. Any ideas?

 

[gregou]

By the way: The device is a 2017G B05 and this is not the "Failed to connect" error. Any ideas?

I have the same error... and the program stop running when i try to enter the following command "Axon7tool -w recovery", which is weird because i succeed to do the 3 backup files in EDL mode and my Zadig drivers are installed and working as showned in my device manager :-/
Is there any solution to use anything else than Axon7tool which, apparently, can brick phones from what a guy said on the facebook thread :-/

 

[billy_boolean]

Tried this on mine.
It dies...

Everything was fine until point 23.
After reboot I just get a red led and that's all.
Cannot go into recovery or anything. Power + Vol up or Power + Vol down > same result.
No answer to adl or adb command.

More over it's impossible to turn it of...

 

[keessonnema]

Tried this on mine.
It dies...

Everything was fine until point 23.
After reboot I just get a red led and that's all.
Cannot go into recovery or anything. Power + Vol up or Power + Vol down > same result.
No answer to adl or adb command.

More over it's impossible to turn it of...

When you're in edl mode the screen is black and it seems off (for some the red led is on). Hold your power button untill it vibrates. It takes a while.

 

[billy_boolean]

When you're in edl mode the screen is black and it seems off (for some the red led is on). Hold your power button untill it vibrates. It takes a while.

Thanks for your answer.
When I try to reboot the phone I get the ZTE logo only 1 second and get back to the black screen with red led

 

[keessonnema]

Thanks for your answer.
When I try to reboot the phone I get the ZTE logo only 1 second and get back to the black screen with red led

Hmm, that's strange. Connecting for adb doesn't work?

 

[billy_boolean]

Hmm, that's strange. Connecting for adb doesn't work?

C:\Axon>fastboot devices

C:\Axon>adb devices
List of devices attached


C:\Axon>

I can see it in the device manqguer under : Qualcomm HS-USB QDLoader 9008 (COM3)

 

[keessonnema]

C:\Axon>fastboot devices

C:\Axon>adb devices
List of devices attached


C:\Axon>

I can see it in the device manqguer under : Qualcomm HS-USB QDLoader 9008 (COM3)

Delete the Qualcomm driver, install Zadig 2.2 (link) driver and try again.

 

[billy_boolean]

Delete the Qualcomm driver, install Zadig 2.2 (link) driver and try again.

Same with WinUSB driver

 

[keessonnema]

Same with WinUSB driver

You definitely have a driver problem, try another usb port first, or reinstall drivers so adb is atleast working for you.

 

[billy_boolean]

You definitely have a driver problem, try another usb port first, or reinstall drivers so adb is atleast working for you.

Same
An other computer with driver from Zadig and qualcomm.

Impossible to turn it off and I only have this fuc*** red led

D:\Axon>axon7tool -w recovery
Device not detected
Failed to connect

D:\Axon>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached

 

[Oki]

23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP

I am trying to save a backup using TWRP before unlocking the bootloader. I have followed steps A.0 to A.22 but step 23 fails. When I try to enter into recovery, the phone enters into EDL mode. It happens both when trying the key combination or using "adb reboot recovery". I have an A2017U with the latest OTA update to date (B29). I am flashing the latest TWRP to date (3.0.3-0) and the custom one linked in the OP post. Both fail.

EDIT: I have found my issue. I wasn't flashing tenfar's signed version of TWRP 3.0.2-2 (http://d-h.st/dgWW). When using it then TWRP becomes persistent. The problem was a mismatch between the signature of the bootloader and Recovery images. Now I am able to do a TWRP backup of my system and I am now free for playing around with it.

NOTE: It would be very convenient to add a note in the OP guide reminding to disable the antivirus software, otherwise axon7tool wont work properly.

Regards

 

[projectseahorse]

Hi All,

I have a quick question as I'm having problem booting into edl mode. After following step 14 my device reboots and appears it is off without the red notification light on. I was unable to recognize the device as stated in step 15 or continue to carry on with step 16, instead I received an error message "error: failure to connect". I can no longer restart my device and was only able to boot up again by going into recovery mode( holding down the volume up and power button"). I tried again and it is the same result. Please help, thanks!

 

[Oki]

Hi All,

I have a quick question as I'm having problem booting into edl mode. After following step 14 my device reboots and appears it is off without the red notification light on. I was unable to recognize the device as stated in step 15 or continue to carry on with step 16, instead I received an error message "error: failure to connect". I can no longer restart my device and was only able to boot up again by going into recovery mode( holding down the volume up and power button"). I tried again and it is the same result. Please help, thanks!

Assuming you are using Windows, go to the device manager and ensure that when you plug your device in edl mode, it is identified in the device manager as QUSB_BULK without the warning signal.

If you have the QUSB_BULK with a warning icon then you need to install the Qualcomm usb driver.

If you obtain the Qualcomm HS-USB QDloader 9008 device instead of QUSB_BULK, then you have to use the zadig tool in windows. go to Options and activate List all devices. Then select QUSB_BULK in the drop down control at the top and WinUSB in the lower control. Then click on the button to replace the driver. After this, QUSB_BULK should appear in the Device manager and you should be able to execute axon7tool.


By the way, do not forget to deactivate the antivirus, otherwise axon7tool won't be able to transfer data.