yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Guides, News, & Discussion] ChandonPierre:
Interesting, it worked for me on B20_boot. Upgraded to B29, made sure to wipe everything first. Now it looks like Dolby doesn't work. Trying to play videos is extremely choppy as well. Disabling dolby allows audio to work but videos are still very choppy. Quite strange.

It seems like I remained bootloader unlocked w/ TWRP during the upgrade. Not sure if that has anything to do with it. I tried clearing the app cache for dolby as well as dalvik but it hasn't done anything.
[ZTE Axon 7 Guides, News, & Discussion] xpakage:
It has been said that flashing the boot stack for B27, then flash the boot stack for B29 will solve several sound/phone issue. Nothing is cleared or formatted. Just flash B27 boot stack then 29B boot stack, reboot, profit. You can find the files here. http://xdaforums.com/showpost.php?p=68873482&postcount=2
[ZTE Axon 7 Guides, News, & Discussion] ChandonPierre:
..........I can't believe that worked! It resolved some other issues with phone calls not coming in as well. Thanks so much!
[ZTE Axon 7 Guides, News, & Discussion] borijess:
I am on stock B29 and want to unlock bootloader. What do I need to do to rollback to B27 so I can unlock booloader?
[ZTE Axon 7 Guides, News, & Discussion] Locklear308:
Same, I've been searching everywhere for this answer lol.
[ZTE Axon 7 Guides, News, & Discussion] iconoclastnet:
I just got a grey axon 7 that came out of the box with B27. I was able to unlock the bootloader by first downgrading to B20 using the image from this thread:

http://xdaforums.com/axon-7/how-to/b20-factory-image-posted-t3492552/

and then using the file from the first post of this thread to enable fastboot oem unlock.

After that I was able to install twrp, etc.
[ZTE Axon 7 Guides, News, & Discussion] xtermmin:
No need to roll back.

Use tenfar's tool to flash just TWRP (not the boot.img), then follow this guide: http://xdaforums.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
[ZTE Axon 7 Guides, News, & Discussion] ronj1986:
To clarify, I should be on B20 to use the files posted by the OP??
[ZTE Axon 7 Guides, News, & Discussion] lolzballs:
Yes, you do.
[ZTE Axon 7 Guides, News, & Discussion] ronj1986:
Thanks I was able to figure that part out. Now rooting is kicking my butt.
[ZTE Axon 7 Guides, News, & Discussion] Tibedabeeto:
Here is what I did to get my phone unlocked and rooted, hope this helps anyone stuck on the process. I have 2017U (US) phone and I downloaded and placed all files on my sdcard from the beginning before placing it in my phone and going through this process.

My phone came preloaded with B27 so I needed to downgrade to B20 to unlock the bootloader. Link to download below....

Full B20

https://www.zteusa.com/axon-7#support

After downloading it and placing the zip file on my sdcard, I rebooted into recovery (Power + Vol Up at same time when phone is off) then flashed the update.zip file from the stock recovery. Once it ran successfully I rebooted then..

I followed this threads step to unlock the bootloader. In order to do this you need unlock the developer settings by going into your phones settings under "about phone" and tapping "build number" several times in order to see the developers options on the previous menu on the phone. You also need adb and all tools on your computer to run the adb and fastboot commands. I had wugfresh's tool when I had a nexus device so I just used his folder setup to run the commands within windows "cmd window".

Unlock Bootloader File

http://xdaforums.com/axon-7/how-to/bootloader-unlock-t3437778

Once unlocked from instructions above I went back into recovery to then go into bootloader. So I can then run the twrp fastboot commands to install twrp as my recovery. I had issues with the main link to download TWRP from the OP so if you go towards the end comments you will see my comment where I found another link to the TWRP image. (Which is what I used when I just did this and it works fine)

Install TWRP

http://xdaforums.com/axon-7/development/a2017u-twrp-3-0-2-0-touch-recovery-zte-t3439603

After running the fastboot command to install TWRP, I used the vol keys to select reboot into recovery option while still in bootloader then click power to reboot into TWRP

***The part below is what I did to get the rom I desired.*****

Once in TWRP I followed the guide below to update it back to B29 (No one answered my question on this thread if I had to install this B29 update before installing the rom so I did it anyways)

http://xdaforums.com/showpost.php?p=68873482&postcount=2

After I installed the 2 zip back to back, I rebooted back into recovery while I was in recovery to then do a factory wipe then install rom below.

Install Rom

http://xdaforums.com/axon-7/development/rom-zaxon-dmix7-stock-base-rom-t3495970

Reboot , phone reboots several times saying phone has unlocked bootloader. Eventually it will not reboot again and load into the Rom.

Profit!
[ZTE Axon 7 Guides, News, & Discussion] kgptzac:
Much thanks to [MENTION=2503351]Tibedabeeto[/MENTION] for the very informative summary on what needs to be done to a new Axon 7. Hopefully this is the last device which is BL unlockable where I have to downgrade the firmware to get it unlocked <_>
[ZTE Axon 7 Guides, News, & Discussion] Chinmonkie:
Just reading the latest 10+ pages of this tread is getting me excited for when my Axon 7 arrives. Thanks [MENTION=1068775]tibe[/MENTION]daeeto for making things easier to understand, its been a while since I have to use adb.
[ZTE Axon 7 Guides, News, & Discussion] ravi_mytouch:
Thank you for precise guide. Was able to root without any issues and upgrade to B29.

But I can't change my font size to small. The settings app crashes. Please help.
[ZTE Axon 7 Guides, News, & Discussion] ravi_mytouch:
That was fixed by a Reboot.

Before reboot, Changing the FONT to small in the display settings closed the Settings.
[ZTE Axon 7 Guides, News, & Discussion] xtermmin:
You didn't try rebooting first? :eek:
[ZTE Axon 7 Guides, News, & Discussion] Poli169:
Does this work for the zte 7 mini aswell or just the regular? I can't seem to find much on the mini forums.
[ZTE Axon 7 Guides, News, & Discussion] xtermmin:
Just the regular. You can't use updates for the regular A7 on the A7 Mini, entirely different device.
[ZTE Axon 7 Guides, News, & Discussion] project_86:
***EDIT***

This was caused by the fastboot I had on my PC. Rebooting into Linux and using fastboot from that worked.

When I get to this part, I cannot get "fastboot devices" to detect anything from the bootloader menu. The file flashes fine, but after I reboot back into the bootloader menu, it still says locked and "fastboot oem unlock" does not work. Any ideas?
[ZTE Axon 7 Guides, News, & Discussion] jman1234:
Can someone please post a clear guide on how to unlock the bootloader on b29? All I see are walls of text and it's confusing.
[ZTE Axon 7 Guides, News, & Discussion] cincibluer6:
Same question. I *think* maybe this but who knows. https://xdaforums.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165

I want to do this before upgrading to Nougat and losing that ability because anymore I think I might go LOS in the future.
[ZTE Axon 7 Guides, News, & Discussion] mr.mgmg:
this method work on 7.1.1?
[ZTE Axon 7 Guides, News, & Discussion] Gachmuret:
+1
[ZTE Axon 7 Guides, News, & Discussion] bkores:
No need for the guide. Use the unlock option in my toolkit here: https://xdaforums.com/axon-7/development/tool-axon7toolkit-t3573108 which will work on any build!
[ZTE Axon 7 Guides, News, & Discussion] Kinanizer:
Hey I recently got the Axon M and I'm trying to unlock it's bootloader. I figure it has to be very similar to the way it's been done here with the Axon 7. Now I'm sure I need to at least change a few things in that update file to make this work with my M, but I have no clue what to open the .p files and the .dat with. The only way I get anything from them is by opening them with a hex editor, but is that my best move or is there a program specifically designed for this? Or better yet is there a better way to accomplish my goal without modifying this update file?
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
what update file are you trying to modify?? Here in the Axon, unlock was initially simply a matter of entering Fastboot and using "fastboot oem unlock"

Then they got rid of fastboot on Nougat and it became harder to do, but still it was just a miflash package or pushing a couple files into the system to bring it back
[ZTE Axon 7 Guides, News, & Discussion] Kinanizer:
The P996A01B20Fastboot_ssl.zip. I was wondering if there was a way to change anything that makes it specific to the 7. It's just an idea that may not even work, but I was thinking if I could flash an Axon M version of that package then maybe I could unlock the bootloader and get twrp on there.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
as long as you don't mind bricking it... ?

honestly can't help you. I don't think it'll work but have no real reason. Do you have EDL packages for it, in case you brick it? Maybe try EDL Tool, it's able to do EDL backups, but I'm not sure if it works with other phones (the developer is [MENTION=6330152]djkuz[/MENTION], you can ask him).

btw, take a look at Controllerboy's unlock guide in the guides section. It uses a method to recover fastboot that requires going back to a build where fastboot was enabled (Which of course the Axon M does not have) but it might as well be useful. The method uses ADB from a signed TWRP to push a couple of files to the system (aboot and fbop).
[ZTE Axon 7 Guides, News, & Discussion] silouorig:
Does this method work with the G Version Android Oreo B02?
[ZTE Axon 7 Guides, News, & Discussion] runninghamster:
If you're looking to unlock the bootloader, simply just use the Axon 7 EDL Tool by djkuz.

Plug your phone into your computer, make sure to have USB Debugging and OEM Unlocking enabled in Developer options. Make sure to check allow for the prompt for USB debugging on the phone.

Search Google for 15s ADB Installer (XDA thread) and install the drivers. Make sure to also have the Qualcomm drivers installed if you don't already. Open a command prompt, and type 'adb devices' to make sure your device shows up (should be string of couple letters).Now simply type 'adb reboot edl' , and in the EDL Tool it should show your device as connected. Select Unlock Bootloader, and follow instructions on-screen, and you should be done within a couple minutes.
[ZTE Axon 7 Guides, News, & Discussion] FF7CloudsNobody:
It's been years since this came out but now I'm working on a project of my own and wondered what the original script changed in boot and system. If anyone has any ideas, I'd really appreciate it
[ZTE Axon 7 Guides, News, & Discussion] Unjustified Dev:
It basically broke the system on purpose so you can't take ota updates. The only real change is the bootloader that was capable of fastboot along with the fbop partition which became obsolete. In Oreo, the bootloader was capable of fastboot regardless of fbop containing any data
[ZTE Axon 7 Guides, News, & Discussion] djona12:
Yes of course, but aren't you getting this while trying to flash the file from OP ?

I know it comes after the "sd_upgrade_disable = 1" but i still don't like the looks of it :/
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
Nope, if you check a few post back... CAN'T Look for it cuz is like i was suspecting having that particular option disabled for some reason, but is enabled some [MENTION=1421381]jkuczera[/MENTION] but he already have the Boot_OTA installed which may enable update from SDCard...

If there is someone there who can test that out, just go to " Recovery > apply update from SDCard" so we know if is just us without the boot_ota or is just me having that issue
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
[MENTION=3044858]DrakenFX[/MENTION] did you enable OEM bootloader unlock in the settings and development menu?
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
No they are disabled....
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
I did the update from SD card when I was on B20. I did not use the update program from settings.
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
OK , to apply from SDCard , OEM ENABLE need to be check under Developer Options...

But fail.

.Image below.
[ZTE Axon 7 Guides, News, & Discussion] dennis96411:
We really need a second unlock OTA update package to compare with.
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
So it's likely that the package has an IMEI signature.
[ZTE Axon 7 Guides, News, & Discussion] dennis96411:
I wonder if the ZTE updater does something else (like changing flags in build.prop or creating a temporary file somewhere to give the recovery an okay to flash the update) before it reboots the phone to install the update.
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
Is this how you applied yours?
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
I used the link that I found and downloaded it to my desktop. Then I took that file and put it on my phone under / SD card. I cancelled the update from the update app. I then rebooted the phone into recovery, chose to update from SD card and selected the update. So either the URL itself is encoded, or there something more at play here.
[ZTE Axon 7 Guides, News, & Discussion] dennis96411:
I did notice a file called otacert in the update package, and found this. The update package might be individualized for each phone with its own key (not necessarily the IMEI). If this is true, can't we just grab the otacert from a previous update package downloaded through the ZTE updater by ourselves?
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
Can you do MD5 or CRC32 hash of the file you have so we can compare the downloaded one, just to exclude corruption

---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------

how about the using the ota.certs from the b20 patch, should be in the store already since it's generic

Edit: both certs have same hash so they are most likely the same
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
I'm pretty sure a corrupted zip won't open. Either way I'll check next time I'm up at my desktop.
[ZTE Axon 7 Guides, News, & Discussion] dennis96411:
Looks like only META-INF\MANIFEST.MF and META-INF\CERT.SF are different between the bootloader unlock package and the B18 to B20 update package. In both packages' MANIFEST.MF and CERT.SF, otacert has the same SHA1-Digest and SHA1-Digest-Manifest values, so if I'm not looking at this incorrectly, they are signed with the same key.

This is what I got from CERT.RSA (same in both):

Certificate:
Data:
Version: 3 (0x2)
Serial Number:
eb:82:60:d0:f9:82:66:4e
Signature Algorithm: sha1WithRSAEncryption
Issuer: C=CN, ST=Shanghai, L=Shanghai, O=ZTE, OU=Smartphone Software Dept., CN=ZTE/emailAddress=support@zte.com.cn
Validity
Not Before: Mar 8 07:13:43 2011 GMT
Not After : Jul 24 07:13:43 2038 GMT
Subject: C=CN, ST=Shanghai, L=Shanghai, O=ZTE, OU=Smartphone Software Dept., CN=ZTE/emailAddress=support@zte.com.cn
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:ba:5c:c7:31:af:9c:e5:02:76:5f:60:27:8a:3e:
0b:7e:c3:8c:bf:7e:60:7b:4b:36:52:26:f0:b1:e2:
11:4a:2a:ae:a6:f4:21:e0:eb:4b:e1:95:54:38:80:
b9:2e:29:bd:65:fa:91:5b:25:da:cf:f3:22:f5:60:
a4:2a:4a:b5:96:0c:08:4f:72:e2:25:2e:3d:d4:72:
6c:df:6c:c4:50:84:ce:26:ad:77:f8:f5:e7:ac:db:
1c:95:64:ed:fc:2a:3b:52:48:1c:3f:ca:0b:c7:e4:
f4:ab:5f:a2:85:52:a4:1d:c5:57:9c:88:b8:1a:b5:
86:28:38:4a:51:18:a6:5d:78:bf:87:00:8d:04:30:
5b:2c:3a:8c:34:d2:33:cf:e3:82:01:f5:58:bd:52:
21:07:3a:ab:d3:1d:59:83:21:d4:16:3a:60:20:59:
79:40:df:ab:1d:5a:c4:9e:6c:bc:d6:5e:39:b6:bc:
1e:8e:25:a3:d5:f7:7c:f1:cb:eb:72:9b:7d:e6:91:
db:9c:d8:31:d0:88:7e:93:15:4a:f8:62:6b:43:39:
92:7b:cb:78:d9:d9:5c:c9:53:75:55:89:83:6e:9e:
6f:c3:6b:43:40:3d:8c:2d:6f:27:8e:82:bf:b9:9e:
95:7b:09:fc:d8:e3:7e:a5:a8:b6:1a:02:51:c9:8f:
1d:fb
Exponent: 3 (0x3)
X509v3 extensions:
X509v3 Subject Key Identifier:
BA:35:54:44:B0:9E:70:19:D4:E2:FF:6E:A6:13:07:FC:87:62:83:7F
X509v3 Authority Key Identifier:
keyid:BA:35:54:44:B0:9E:70:19:D4:E2:FF:6E:A6:13:07:FC:87:62:83:7F
DirName:/C=CN/ST=Shanghai/L=Shanghai/O=ZTE/OU=Smartphone Software Dept./CN=ZTE/emailAddress=support@zte.com.cn
serial:EB:82:60:D0:F9:82:66:4E

X509v3 Basic Constraints:
CA:TRUE
Signature Algorithm: sha1WithRSAEncryption
a4:89:03:5d:a0:ab:28:68:ac:f9:34:12:41:cd:81:44:cb:26:
8c:ad:a2:5e:52:1c:f9:2c:76:16:cc:8d:33:93:12:c6:8f:88:
e5:50:67:4b:07:93:d2:43:3e:85:d1:26:56:6f:2d:72:2f:64:
2b:73:1b:e6:02:8e:91:7c:1a:ff:ee:2b:8e:e3:1c:9b:01:1b:
92:fd:2f:22:3f:2c:d7:2d:3c:e4:de:7e:3d:da:05:09:25:2f:
15:20:79:b9:5a:68:ad:80:14:66:fe:ca:09:97:f2:99:46:4b:
03:b3:f6:9e:26:82:bf:14:42:d3:ec:75:73:fa:83:11:1e:8c:
8d:e8:67:c0:73:e0:79:ad:b4:bf:86:c1:a6:c2:64:0c:6e:17:
d3:b6:67:8b:d7:d6:80:98:6c:05:4b:00:ac:fe:49:4a:0c:55:
76:3d:87:34:9a:fd:3b:71:f8:77:87:d2:81:cf:5d:d6:74:03:
65:72:c6:92:e2:14:85:dd:6d:d0:bd:cd:68:c1:f0:01:90:82:
66:08:34:31:e5:41:11:b8:84:f1:fd:f8:da:69:0e:58:f1:77:
5f:53:d5:c1:33:90:51:11:14:42:3c:75:69:13:09:a1:3c:99:
13:50:7d:28:52:b7:b3:77:bd:6f:a4:7c:42:ea:f2:b9:64:bc:
33:16:f4:93

I'm not really good with cryptography, but it seems like otacert and CERT.RSA are related. I ran an OpenSSL command on CERT.RSA and it produced the same certificate as otacert.
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
fastboot.img is also different, but what is also different is the CERT.RSA, so in essence everything except otacert is different

Edit: so the RSA file has same certificate but if different on the binary level
[ZTE Axon 7 Guides, News, & Discussion] dennis96411:
Does this involve a private signature key?
[ZTE Axon 7 Guides, News, & Discussion] max1001:
That's the public key, not a private key. This is probably the same across all the devices. Are there any other cert files you can upload? I am decent with PKI.

---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------

FYI, the command to unlock is no longer fastboot oem unlock in Android 6 and up. It's now

flashing unlock

A lot of ppl are still not aware of this command changes.

https://source.android.com/security/verifiedboot/verified-boot.html
[ZTE Axon 7 Guides, News, & Discussion] dennis96411:
I'm not sure if this is what you meant.
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
Yeah the was for the case for the last nexus line, but in this case it seems an older fastboot code is still used, at least ZTEs aboot does since their unlock still uses the old syntax
[ZTE Axon 7 Guides, News, & Discussion] dennis96411:
Is it possible to take the files out from the update package, then repackage it and sign it with our own certificate? That's unless something's linked to individual devices.
[ZTE Axon 7 Guides, News, & Discussion] dennis96411:
Well since we're at a loss at the moment, I figured I'd try some random stuff. I repacked the bootloader unlock OTA and signed it with a test certificate. It might be worth trying? Download here.
[ZTE Axon 7 Guides, News, & Discussion] max1001:
No, it would check to see who the CA of the cert is. Unless the cert is issued by a trusted CA, wouldn't work. It's like going to the bank and using a home made ID and Credit Card.
[ZTE Axon 7 Guides, News, & Discussion] KyJelly69:
What, that doesn't work for you?
[ZTE Axon 7 Guides, News, & Discussion] rczrider:
Haha
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
Lol.

I was looking into the footer error, for OTAs on other phones, and sometimes even the file name would make a difference. But if it's all the same like it was on [MENTION=1421381]jkuczera[/MENTION] 's update (same file location, name) and file CRC32 matches the one he has, it might be that the signature is tied to the device app. For instance the updater-binary is different between two OTAs, i expected the binary to be standard and take queues from updater-script. Problem will be in changing this without braking the crypto chain, all the files are in the SF/MF and if sha1 key don't match, it won't work
[ZTE Axon 7 Guides, News, & Discussion] rczrider:
I wish I understood more than half of what you guys are saying.
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
[MENTION=3044858]DrakenFX[/MENTION]

can you verify if the zip file on the sdcard is same as the one you downloaded. The on i got has CRC32 f031d661 and MD5 hash bab1e10494a82d6f2c9f172439b3b8b3 size is 61391631.

More i read about this it ends up being a bad file. Nexus forums were littered with OTAs failing with that error. I had this in the past where file woul be corrupted if i transfered it from the PC to Phone

Also give the ADB sideload a try, it should work since this looks like a standard android recovery with Mi logo

Link for reference: http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5
[ZTE Axon 7 Guides, News, & Discussion] walka.gh86:
Man, you posted you've been able to root the axon 7 did you?
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
Is the same as yours, i don't have my laptop with me so i can try side loading the update, I'll try when i get back home.
[ZTE Axon 7 Guides, News, & Discussion] jkuczera:
Can you try this one? [MENTION=3044858]DrakenFX[/MENTION]
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
Found what throws out that error

https://github.com/CyanogenMod/android_bootable_recovery/blob/cm-13.0/verifier.cpp - start at line 108

My CPP is rusty, but let's see what is used in footer check
[ZTE Axon 7 Guides, News, & Discussion] rczrider:
I did not. Maybe you're thinking about me posting in another thread in following up with [MENTION=540283]tenfar[/MENTION] (who said he had root for the Chinese variant)?
[ZTE Axon 7 Guides, News, & Discussion] dennis96411:
Did anyone try the zip I uploaded earlier?
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
This is quite a different file. Did you notice that the first file (the zip one) had a system folder with build.prop the display for A2016U, which is Axon Pro. I just noticed that

ro.product.model=ZTE A2017U

ro.build.display.id=A2016UV1.0B18

ro.product.name=P996A01

That file was not in the manifest, which is strange, every file from the zip should be on there otherwise the hash is bad

---------- Post added at 04:48 PM ---------- Previous post was at 04:46 PM ----------

It will not pass the signature check since the certificate is not already stored on the device. Only ZTE and maybe Qualcomm dev keys would work, otherwise Secure Boot would have no purpose

---------- Post added at 04:54 PM ---------- Previous post was at 04:48 PM ----------

Just checked and this file has the proper footer, bytes 3 and 4 from the end should be FF, which they are and that's what the footer error checks
[MENTION=3044858]DrakenFX[/MENTION] give it a try please
[ZTE Axon 7 Guides, News, & Discussion] Az Biker:
Thread Cleaned!

The irony of disrespectful adults telling other users to let the adults work, is remarkable!

Follow XDA Rules which include being respectful to other users (even if you disagree with them) and not using vulgarity (even if it is the only way to show that you're an adult).

This will be your ONLY warning.
[ZTE Axon 7 Guides, News, & Discussion] DrakenFX:
[MENTION=5940484]Jose-MXL[/MENTION]

THANK YOU [MENTION=1421381]jkuczera[/MENTION] You DID IT man, Marry Xmas to all :D... if anyone want to jump , just download the NEW uploaded by [MENTION=1421381]jkuczera[/MENTION] and change the ext. from " .up " to " .zip " and flashed over stock recovery.

attachment as proof
[ZTE Axon 7 Guides, News, & Discussion] peramikic:
HELLZ YEAH!!! I knew it when i saw the new file footer, I almost PMd you. Where did the first file come from [MENTION=1421381]jkuczera[/MENTION]?
[ZTE Axon 7 Guides, News, & Discussion] TeutonJon78:
Is this file modified from ones that people received as OTAs, or is it the same file that everyone is getting?

[MENTION=3044858]DrakenFX[/MENTION], did you try unlocking the bootloader then? Just flashing the update wouldn't necessarily do that part as well.