[GUIDE] How To Unlock Bootloader and Stay Stock (A2017U - A2017)

[peramikic]

Just did this process and everything works perfect.

Just one note for those who had the encrypted TWRP problem. When you go to format dalvik/cache/data/internal, you'll get the encrypted error (cannot read data). Don't worry. Go back and do a factory wipe first. Then format dalvik/cache/data. It should work. Then format internal.

Which model, U, G or V ?

 

[Guido83]

Which model, U, G or V ?

just successfully tested on G model

 

[jpde]

just successfully tested on G model

Any changes from the instructions in the OP? Which software version were you on, B02 or B03 (if that makes any difference)?

 

[regenwurm16]

Just did this process and everything works perfect.

Just one note for those who had the encrypted TWRP problem. When you go to format dalvik/cache/data/internal, you'll get the encrypted error (cannot read data). Don't worry. Go back and do a factory wipe first. Then format dalvik/cache/data. It should work. Then format internal.

Hi strifej,
do you mean you unlocked your EU version bootloader by just flashing the fastboot.img from OP and then doing the commands or did you have to flash an aboot.img aswell?

 

[strifej]

Which model, U, G or V ?

Hi strifej,
do you mean you unlocked your EU version bootloader by just flashing the fastboot.img from OP and then doing the commands or did you have to flash an aboot.img aswell?

I'm on U (North America), so, sorry, didn't do any of that aboot stuff. I was only mentioning it because I know a few people got TWRP encryption issues where it couldn't read your key. When I saw the same problem when trying to format, I freaked out too thinking it's over.. lol. But did a factory reset then went back to test and it low and behold, it worked, so wanted to share it right away. This way others hitting this issue can finally use SuperSU and Xposed without flashfire, etc.

 

[Guido83]

hmm but after a reboot, twrp is again asking for password. so it just worked omce

 

[strifej]

hmm but after a reboot, twrp is again asking for password. so it just worked omce

I just confirmed mine is still ok by booting into recovery. Maybe it's a Europe version problem?

Also, are you using the last TWRP posted by tenfar in his thread? Not sure if OP was updated to the newest (3.0.2-2) so you may have to look through the thread to find the post by tenfar.

I first did tenfar's method, which led to twrp encrypted. When I did this method, I did NOT reflash recovery. Only boot.

I would pm all the people that thanked you when you said G because they must have the same version and same problem. See if they're ok or not now.

Good luck

 

[Guido83]

I just confirmed mine is still ok by booting into recovery. Maybe it's a Europe version problem?

Also, are you using the last TWRP posted by tenfar in his thread? Not sure if OP was updated to the newest (3.0.2-2) so you may have to look through the thread to find the post by tenfar.

I first did tenfar's method, which led to twrp encrypted. When I did this method, I did NOT reflash recovery. Only boot.

yes I am using 3.0.2-2

 

[strifej]

yes I am using 3.0.2-2

Oh, I did one thing not in the instructions. In my eagerness seeing I could write to data, I flashed supersu 65 right away before booting into a clean rom. After booting into the ROM, I rebooted back to recovery to make backups of all my partitions.. I doubt it'd make any real difference, but at this point you're formatted, so you might as well try.. haha

Also, during initial setup of the phone, don't set fingerprint. Leave all security stuff unset so it's swipe only. Maybe if you set fingerprint first thing that causes the TWRP encryption bug? Because that's what happened to me using tenfar's method. I set fingerprint during rom setup, then I had the encryption bug. Sooo.. maybe after 1 or 2 reboots into twrp with NO security set, it avoids the problem.

 

[Guido83]

Oh, I did one thing not in the instructions. In my eagerness seeing I could write to data, I flashed supersu 65 right away before booting into a clean rom. After booting into the ROM, I rebooted back to recovery to make backups of all my partitions.. I doubt it'd make any real difference, but at this point you're formatted, so you might as well try.. haha

Also, during initial setup of the phone, don't set fingerprint. Leave all security stuff unset so it's swipe only. Maybe if you set fingerprint first thing that causes the TWRP encryption bug? Because that's what happened to me using tenfar's method. I set fingerprint during rom setup, then I had the encryption bug. Sooo.. maybe after 1 or 2 reboots into twrp with NO security set, it avoids the problem.

which super su exactly did you flash?

 

[blessingme]

UPDATE-SuperSU-v2.65-20151226141550

 

[Guido83]

For me its not working at all. Whenever I boot once the system, TWRP is encrypted again, even when skipping the fingerprint/security settings.
The supersu patches also the boot image, so the device does not boot anymore until i restore the boot image.

 

[strifej]

For me its not working at all. Whenever I boot once the system, TWRP is encrypted again, even when skipping the fingerprint/security settings.
The supersu patches also the boot image, so the device does not boot anymore until i restore the boot image.

I can only suggestion restoring your phone to full stock using a factory image then try again. I used supersu 2.65 as noted a few posts above.

 

[peramikic]

For me its not working at all. Whenever I boot once the system, TWRP is encrypted again, even when skipping the fingerprint/security settings.
The supersu patches also the boot image, so the device does not boot anymore until i restore the boot image.

Can you reboot to bootloader and confirm it shows unlocked

 

[regenwurm16]

OH MY MOTHERF***ING GOD!!!
I used tenfar's tool to flash the TWRP recovery and then I flashed the modified fastboot.img from this thread and after trying the unlock command in fastboot it didn't work of course. So I became adventurous (even though I already ****ed up one phone) and flashed the aboot.img from the B20 stock thread http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818 to my phone and low and behold I could actually UNLOCK my B02 EU version without even touching the boot.img!!!
And it still booted, Wi-Fi is still working and it's really saying "DEVICE STATE - unlocked"
I'm so fu**ing happy!!!

 

[DrakenFX]

OH MY MOTHERF***ING GOD!!!
I used tenfar's tool to flash the TWRP recovery and then I flashed the modified fastboot.img from this thread and after trying the unlock command in fastboot it didn't work of course. So I became adventurous (even though I already ****ed up one phone) and flashed the aboot.img from the B20 stock thread http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818 to my phone and low and behold I could actually UNLOCK my B02 EU version without even touching the boot.img!!!
And it still booted, Wi-Fi is still working and it's really saying "DEVICE STATE - unlocked"
I'm so fu**ing happy!!!

So my idea of flashing aboot.img from b20 (U) to G to unlock BOOTLOADER came to fruition hehehe...cool thank for been brave and posting the results,

If someone else with the G can test this for 2nd confirmation ,I'll be adding the changes to my OP.

 

[regenwurm16]

I can furthermore confirm that mobile data works as well so I think every possible problem did not occur to me.
Now the next adventure is to update to B03. I suppose I would just need to reflash the old stock recovery. Can I do this while being in TWRP via the adb dd commands?

 

[DrakenFX]

I can furthermore confirm that mobile data works as well so I think every possible problem did not occur to me.
Now the next adventure is to update to B03. I suppose I would just need to reflash the old stock recovery. Can I do this while being in TWRP via the adb dd commands?

if you already have TWRP and unlock bootloader no NEED to do that.... just hold in there, i'll be creating a Flashable B03 zip (Been testing it for A2017U and i have use B03 on my USA version hehehe),
just give me little time or PM if you want to create one your self.

 

[regenwurm16]

Thanks for your effort most probably this will be the route to go now as ZTE is providing full OTA images it should pose no problem to make them into a TWRP flashable zip without the need to revert anything back to stock(recovery, fastboot or aboot).

 

[Starvirus]

Hi guys,

finally i got my B03 A2017G bootloader unlocked. Here is how I did it:

1. enable developer menu -> settings -> about phone tap 7 times on the build number
2. go to developer options -> enable oem unlock
3. backup your recovery and boot with axon7backup (axon7backup -d -p X) - get axon7backup from here: http://d-h.st/Ienb
4. flash twrp-3.0.2-2 with axon7root (rename the file as recovery.img and put it in the same directory as the axon7root.exe and execute axon7root -p X -r) - get axon7root from here: http://d-h.st/aPiC get twrp-3.0.2-2 from here: http://d-h.st/dgWW
5. boot into twrp, hold power and volume up until you are in twrp
6. execute: - get the aboot.img from here: https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw

#copy necessary files to internal sd card
adb push aboot.img /sdcard/
adb push fastboot_unlock.img /sdcard/

#make a backup to your internal sd of the partitions we are going to modify
adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img
adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img

#copy them to your pc
adb pull /sdcard/fbop_lock.img
adb pull /sdcard/aboot_lock.img

#flash the proper fastboot and aboot file
adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop
adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot

#boot to fastboot
adb reboot bootloader

7.

 fastboot oem unlock

8. follow instructions on your phone
9. boot into twrp -> vol up + power button
10. wipe data
11. enjoy the unlocked device

Hope this helps a few guys