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

[Xadro]

Its not working for me. Or Ive downloaded the wrong one...not sure.

This is the one i was using

 

[tuiyaan]

Tried B03,B05 & B06 2017G
unable to enter edl mode

failed to connect is the message, when axon7tool -r gpt is executed.

even tried to enter edl with xiomi deep flash diy cable
http://en.miui.com/thread-324300-1-1.html

failed all

 

[Diplodocus123]

This is the one i was using

The same as I used. Strange....

 

[Xadro]

So after all i can confirm the method is working for A2017G with B08, but i had to modify some steps:
Prior to Bootloader unlock only tenfar's recovery was working for me. (This)
Dont use it for any other purpose than BL unlock though, as it is buggy, especially DO NOT BACKUP OR RESTORE EFS with this.
After i unlocked the BL (procedure as in OP), i was able to fastboot flash the normal official recovery and it works.
So atm i only rooted stock by flashing supersu in TWRP but I'll probably soon will change to cm.

 

[tuiyaan]

So after all i can confirm the method is working for A2017G with B08, but i had to modify some steps:
Prior to Bootloader unlock only tenfar's recovery was working for me. (This)
Dont use it for any other purpose than BL unlock though, as it is buggy, especially DO NOT BACKUP OR RESTORE EFS with this.
After i unlocked the BL (procedure as in OP), i was able to fastboot flash the normal official recovery and it works.
So atm i only rooted stock by flashing supersu in TWRP but I'll probably soon will change to cm.

Could you please explain in detail how did get to edl mode?

 

[keessonnema]

So after all i can confirm the method is working for A2017G with B08, but i had to modify some steps:
Prior to Bootloader unlock only tenfar's recovery was working for me. (This)
Dont use it for any other purpose than BL unlock though, as it is buggy, especially DO NOT BACKUP OR RESTORE EFS with this.
After i unlocked the BL (procedure as in OP), i was able to fastboot flash the normal official recovery and it works.
So atm i only rooted stock by flashing supersu in TWRP but I'll probably soon will change to cm.

Thanks for confirming! I'll try it

 

[Dust2Dust]

So after all i can confirm the method is working for A2017G with B08, but i had to modify some steps:
Prior to Bootloader unlock only tenfar's recovery was working for me. (This)
Dont use it for any other purpose than BL unlock though, as it is buggy, especially DO NOT BACKUP OR RESTORE EFS with this.
After i unlocked the BL (procedure as in OP), i was able to fastboot flash the normal official recovery and it works.
So atm i only rooted stock by flashing supersu in TWRP but I'll probably soon will change to cm.

Now be so kind to tell me how you were able to download from that link without getting a digital STD !?!?

 

[neo4uo]

Can I use this to just flash TWRP and install root without unlocking the bootloader? I do not care anything about installing roms, I just want stock root for xposed and Titanium Backup?

 

[lafester]

Can I use this to just flash TWRP and install root without unlocking the bootloader? I do not care anything about installing roms, I just want stock root for xposed and Titanium Backup?

No. Follow tenfars thread for that.

 

[tuiyaan]

Anyone kind enough to make a video of this from beginning to end

 

[Dust2Dust]

Updated the main post to reflect changes noticed by users. Changed link to TWRP to the official version to avoid people bricking their devices by restoring EFS backup using crappy TWRP version.

I am not 100% sure this will work with B08 firmware, but I don't see why it shouldn't. It worked with all other firmwares. I think only Nougat will bring deep changes which might make this tool redundant. Also, having B08 shouldn't exclude you from booting to EDL and connecting as QUSB_BULK. It surprises me some people don't seem to be able to get it to connect as "QUSB_BULK". Uninstalling Qualcomm drivers and reconnecting should be enough, don't know why it behaves so different on different Windows machines...

I changed to this "official" recovery and get a black screen whilest booting into recovery, restored previous TWRP for now

 

[Controllerboy]

I changed to this "official" recovery and get a black screen whilest booting into recovery, restored previous TWRP for now

:s I had changed the TWRP version to the official one since the unofficial version creates dangerous EFS backups. Okay, I might change it back again but BEWARE not to backup and restore EFS with that recovery version, it killed my cellular data

 

[Dust2Dust]

:s I had changed the TWRP version to the official one since the unofficial version creates dangerous EFS backups. Okay, I might change it back again but BEWARE not to backup and restore EFS with that recovery version, it killed my cellular data

Have no plan to do so


Will the rest of your tut work flawless from here??


I mean unlocking bootloader in order to root the Axon ?? I have no need for CM.

 

[keessonnema]

Have no plan to do so


Will the rest of your tut work flawless from here??


I mean unlocking bootloader in order to root the Axon ?? I have no need for CM.

It's possible to unlock BL and root, but you have to be aware that you can't backup with twrp. Because the official one doesn't work and the tenfar ****s up efs backup.

I've asked a dev to help me with the A2017U TWRP to make it compatible with EU model. I'll keep you guys updated

 

[keessonnema]

My axon7tool gives me "Failed to connect" phone doesn't seem to work in edl, no red led etc. What to do? It's connected as QUSB_BULK.

---------- Post added at 06:50 PM ---------- Previous post was at 06:44 PM ----------

:s I had changed the TWRP version to the official one since the unofficial version creates dangerous EFS backups. Okay, I might change it back again but BEWARE not to backup and restore EFS with that recovery version, it killed my cellular data

I can't seem to enter EDL mode. No red led, my phone is connected as QUSB_BULK, what could be the problem, or how do I fix this? I've flashed 980234 roms and unlocked several bootloaders, but I can't seem to find out how to do this.

 

[Dust2Dust]

It's possible to unlock BL and root, but you have to be aware that you can't backup with twrp. Because the official one doesn't work and the tenfar ****s up efs backup.

I've asked a dev to help me with the A2017U TWRP to make it compatible with EU model. I'll keep you guys updated

No need for a backup, will restore with titanium. Good thing about new phones is that you can flash all the bits and pieces

 

[keessonnema]

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

 

[Controllerboy]

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

 

[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

Someone on the Facebook group suggested to update the winusb by zadig once the phone is rebooted to edl (rightclick the QUSB_BULK and click update driver)

 

[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.