The ZTE downloads page says their was a FW update to Android 5.02, but that it was available OTA only. No downloadable package. ZTE very rarely issued updates, and only provided a downloadable package if the update couldn't be delivered OTA (ie if it had to be physically loaded onto the device). Instructions: Step 1: Download the full stock firmware (update package file) from download section above. Step 2: Transfer the A2017UV2.1.0B20SD.zip file to phone storage or SD Card. Step 3: Now, to avoid FRP Lock, you will need to delete (remove) the Google account from the phone.

1. Update Zte Software
2. Zte Android Update Package Windows 10
3. Android Updates For Zte

Use this page to identify software versions for the ZTE ZMAX as well as details on recent software updates.

On this page:

Identify the device's current software version

Android version 4.4.2 / Software version Z970V1.0.0B35

1. From the Home screen, tap Apps > Settings > About phone.
2. Read the build number on the phone.
3. Review the information in the Review software version details section below.

Android version 4.4.2 / Software version Z970V1.0.0B34

1. From the Home screen, tap Apps > Settings > About phone.
2. Read the build number on the phone.
3. Review the information in the Review software version details section below.

Review software version details

Determine update requirements

Customers' devices must meet the following requirements to update their software to the most current version:

• 50% or higher battery life
• Data connection
• File size is 17.2 MB

Update software versions

Update automatically over the air (OTA)

1. From the message Notification Screen, tap Download.
2. Tap Install Now.
3. Wait as your phone restarts and updates.

Check for update

1. From the Home screen, tap Apps > Settings > About phone.
2. Tap Additional system updates > ​Software update​ > ​Check for update​.
3. Wait while the device checks for updates.
4. If an update is available, tap to download and install.

Update Zte Software

Issues after updating

Zte Android Update Package Windows 10

If you experience issues after updating to the latest software version, follow these steps:

1. Wipe your cache partition to make sure that all system files on your device are put back in order.
   1. Turn off the device.
   2. Press and hold the Volume Up and Power buttons until the ZTE logo screen appears, then release.
   3. Press the Volume down button to highlight wipe cache partition.
   4. Press the Power button to select.
   5. Wait until the device displays 'Cache wipe complete.'
   6. Press the Power button to select reboot system now.
2. If wiping the cache partition does not work, you may need to perform a master reset.
   1. From any Home screen, tap Apps > Settings > Backup & reset > Factory data reset > Reset phone.
   2. If your phone is password protected, you'll be prompted to enter your Pattern, PIN, or Password.
   3. Tap Erase everything.

You can use the ota_from_target_files tool provided in build/make/tools/releasetools to build full and incrementalOTA packages for devices using A/B system updates ornon-A/B system updates. The tool takes thetarget-files.zip file produced by the Android build system as input.

For devices running Android 11 or higher, you can buildone OTA package for multiple devices with different SKUs. Doing so requiresconfiguring the target devices to use dynamicfingerprints and updating the OTAmetadata to include the device name and fingerprint inthe pre and postcondition entries.

Android 8.0 deprecated file-based OTA packages for non-A/B devices, which mustinstead use block-based OTA packages. Togenerate block-based OTA packages or devices running Android 7.x or lower, passthe --block option to the ota_from_target_files parameter.

Building full updates

A full update is an OTA package that contains the entire final state of thedevice (system, boot, and recovery partitions). As long as the device is capableof receiving and applying the package, the package can install the buildregardless of the current state of the device. For example, the followingcommands use release tools to build the target-files.zip archive for thetardis device.

The resultant .zip file contains everything needed to construct OTA packagesfor the tardis device.

ota_update.zip is now ready to be sent to test devices (everything is signedwith the test key). For user devices, generate and use your own private keys asdetailed in Signing builds for release.

Building incremental updates

An incremental update is an OTA package that contains binary patches to dataalready on the device. Packages with incremental updates are typically smalleras they don't need to include unchanged files. In addition, as changed files areoften very similar to their previous versions, the package only needs to includean encoding of the differences between the two files.

You can install an incremental update package only on devices that have thesource build used in constructing the package. To build an incremental update,you need the target_files.zip file from the previous build (the one you wantto update from) as well as the target_files.zip file from the new build. Forexample, the following commands use release tools to build an incremental updatefor the tardis device.

This build is very similar to the previous build, and the incremental updatepackage (incremental_ota_update.zip) is much smaller than the correspondingfull update (about 1 MB instead of 60 MB).

Distribute an incremental package only to devices running exactly the sameprevious build used as the incremental package's starting point. You must flashthe images in PREVIOUS-tardis-target_files.zip or PREVIOUS-tardis-img.zip(both built with make dist, to be flashed with fastboot update), instead ofthe ones under the PRODUCT_OUT directory (built with make, which will beflashed with fastboot flashall). Attempting to install the incremental packageon a device with some other build results in an installation error. When theinstall fails, the device remains in the same working state (running the oldsystem); the package verifies the previous state of all the files it updatesbefore touching them, so the device isn't stranded in a half upgraded state.

For the best user experience, offer a full update for every 3–4 incrementalupdates. This helps users catch up to the latest release and avoid a longinstall sequence of incremental updates.

Building OTA packages for multiple SKUs

Android Updates For Zte

Android 11 or higher supports using a single OTApackage for multiple devices with different SKUs. Doing so requires configuringthe target devices to use dynamic fingerprints and updating the OTA metadata(using OTA tools) to include the device name and fingerprint in the pre and postcondition entries.

About SKUs

The format of a SKU is a variation of combined buildparameter values andis typically an undeclared subset of the current build_fingerprint parameters.OEMs can use any combination of CDD-approved build parameters for a SKU whilealso using a single image for those SKUs. For example, the following SKU hasmultiple variations:

• modifierA is the device level (such as Pro,Premium, or Plus)
• modifierB is the hardware variation (such asradio)
• modifierC is the region, which can be general(such as NA, EMEA, or CHN ) or country- or language-specific (such as JPN,ENG, or CHN)

Many OEMs use a single image for multiple SKUs, then derive the final productname and device fingerprint at runtime after the device boots up. This processsimplifies the platform development process, enabling devices with minorcustomizations but different product names to share common images (such astardis and tardispro).

Using dynamic fingerprints

A fingerprint is a defined concatenation of buildparameters such asro.product.brand, ro.product.name, and ro.product.device. The fingerprintof a device is derived from the system partition fingerprint and is used as anunique identifier of the images (and bytes) running on the device. To create adynamic fingerprint, use dynamic logic in the device's build.prop file toget the value of bootloader variables at device boot time, then use that data tocreate a dynamic fingerprint for that device.

For example, to use dynamic fingerprints for tardis and tardispro devices,update the following files as shown below.

• Update the odm/etc/build_std.prop file to contain the following line.

• Update the odm/etc/build_pro.prop file to contain the following line.

• Update the odm/etc/build.prop file to contain the following lines.

These lines dynamically set the device name, fingerprint, andro.build.fingerprint values based on the value of thero.boot.product.hardware.sku bootloader property (which is read-only).

Updating OTA package metadata

An OTA package contains a metadata file (META-INF/com/android/metadata) thatdescribes the package, including the precondition and postcondition of the OTApackage. For example, the following code is the metadata file for an OTA packagetargeting the tardis device.

The pre-device, pre-build-incremental, and pre-build values define thestate a device must have before the OTA package can install. Thepost-build-incremental and post-build values define the state a device isexpected to have after the OTA package installs. The values of pre- andpost- fields are derived from the following corresponding build properties.

• The pre-device value is derived from the ro.product.device build property.
• The pre-build-incremental and post-build-incremental values are derivedfrom the ro.build.version.incremental build property.
• The pre-build and post-build values are derived from thero.build.fingerprint build property.

On devices running Android 11 or higher, you can usethe --boot_variable_file flag in OTA tools to specify a path to a file thatcontains the values of the runtime variables used in creating the device'sdynamic fingerprint. The data is then used to update the OTA metadata to includethe device name and fingerprint in the pre- and post- conditions (using thepipe character | as the delimiter). The --boot_variable_file flag has thefollowing syntax and description.

• Syntax: --boot_variable_file <path>
• Description: Specifies a path to a file that contains the possible values ofro.boot.* properties. Used to calculate the possible runtime fingerprintswhen some ro.product.* properties are overridden by the import statement.The file expects one property per line where each line has the followingformat: prop_name=value1,value2.

For example, when the property is ro.boot.product.hardware.sku=std,pro, theOTA metadata for tardis and tardispro devices is as shown below.

To support this functionality on devices running Android 10, see the referenceimplementation.This changelist conditionally parses the import statements in the build.propfile, which enables property overrides to be recognized and reflected in thefinal OTA metadata.