Axon 7 Factory Images/Full OTAs

Search This thread

TeutonJon78

Senior Member
Jul 24, 2010
574
287
Full OTA images can be downloaded via:
A2017 -ZTE China's community site: http://www.myzte.cn/resource.php?mod=category&catid=196&netid=0&softid=0
A2017 - ZTE Devices (China) site: http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
A2017G - ZTE Devices site: http://www.ztedevice.com/support/detail?id=9824F5AD299B49D8A2EE4227CFB0DB8A
A2017U - ZTE USA Support Site: https://www.zteusa.com/axon-7#support
NOTE: The version numbers between the models have no correlation.

Archived Images:
6.0
A2017 - B11, B13
A2017G - B06, B08
A2017U - B20, B29

7.0
A2017U - B15

7.1.1
A2017 - B15
A2017U - B19

(MEGA Mirror) - because Baidu sucks (not that Mega is great, but hey, lots of free storage)

While only the US model has the ability to unlock the bootloader, the HW should be the same (except for the modem images and the Force Touch digitizer), so some important info can probably be pulled from these images.
 
Last edited:

benlenspace

Senior Member
Sep 24, 2014
65
17
All of the Chinese ROMs (and the A2017G B02 ROM) are now uploaded into my MEGA storage space. The link is in my signature. Downloading them from Baidu is just a terrible experience that no should have to endure.

thank you

im on chinese rom now... i really wanted to have the a2017U rom of the US version... maybe it will come soon...
 

satand

Senior Member
May 4, 2015
491
48
are there differences between the US and the EU rom? as i know is the hardware the same. though i am not sure about the modem. but the US rom should work on EU hardware and vice versa as well.
 

peramikic

Senior Member
Nov 12, 2008
524
298
Does somebody know if Chinese Stock ROMs are inclusive of stock bootloader?

Looks like it, here is the B06 update script
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
ui_print("Target: ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20160708.061559:user/release-keys");
show_progress(0.950000, 180);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/bootdevice/by-name/system", "176,0,32770,33153,33155,33663,65535,65536,65538,66046,98303,98304,98306,98689,98691,99199,131071,131072,131074,131582,163839,163840,163842,164225,164227,164735,196607,196608,196610,197118,229375,229376,229378,229761,229763,230271,262143,262144,262146,262654,294911,294912,294914,295297,295299,295807,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819585,819587,820095,851967,851968,851970,852478,884735,884736,884738,885121,885123,885631,917503,917504,917506,918014,950271,950272,950274,950782,983039,983040,983042,983550,1015807,1015808,1015810,1016318,1048575,1048576,1048578,1049086,1069783,1081344,1081346,1114112,1114114,1146880,1146882,1179648,1179650,1212416,1212418,1245184,1245186,1277952,1277954,1310720,1310722,1343488,1343490,1376256,1376258,1409024,1409026,1441792,1441794,1474560,1474562,1507328,1507330,1540096,1540098,1540606,1560470,1560471,1572768") == "02a6535757c8ece463ad215ae5eabc2ab23fcdaf" then
if range_sha1("/dev/block/bootdevice/by-name/system", "204,32770,33153,33155,33663,65535,65536,65538,66046,98303,98304,98306,98689,98691,99199,131071,131072,131074,131582,163839,163840,163842,164225,164227,164735,196607,196608,196610,197118,229375,229376,229378,229761,229763,230271,262143,262144,262146,262654,294911,294912,294914,295297,295299,295807,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819585,819587,820095,851967,851968,851970,852478,884735,884736,884738,885121,885123,885631,917503,917504,917506,918014,950271,950272,950274,950782,983039,983040,983042,983550,1015807,1015808,1015810,1016318,1048575,1048576,1048578,1049086,1069783,1070295,1080832,1081344,1081346,1081858,1113600,1114112,1114114,1114626,1146368,1146880,1146882,1147394,1179136,1179648,1179650,1180162,1211904,1212416,1212418,1212930,1244672,1245184,1245186,1245698,1277440,1277952,1277954,1278466,1310208,1310720,1310722,1311234,1342976,1343488,1343490,1344002,1375744,1376256,1376258,1376770,1408512,1409024,1409026,1409538,1441280,1441792,1441794,1442306,1474048,1474560,1474562,1475074,1506816,1507328,1507330,1507842,1539584,1540096,1540098,1540606,1560470,1560471") == "17ac644bdff59ffa07fa9b2d452c9107bdf6842f" then
ui_print("Verified the updated system image.");
else
  abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
  abort("system partition has unexpected contents after OTA update");
endif;
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
package_extract_file("xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("sec.dat", "/dev/block/bootdevice/by-name/sec");
package_extract_file("splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("echarge.img", "/dev/block/bootdevice/by-name/echarge");
package_extract_file("adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("mdtp.img", "/dev/block/bootdevice/by-name/mdtp");
package_extract_file("emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");
package_extract_file("BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
package_extract_file("cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_dir("cache", "/cache");
 

ciko84xp

Senior Member
Jul 16, 2008
144
4
Rossano Calabro
Thanx man...
boot.img is exactly what I wanted to see... ;)
(Unless this does not refer to the system boot, but if I am not wrong refers to the bootloader)
 
Last edited:

peramikic

Senior Member
Nov 12, 2008
524
298
Thanx man...
boot.img is exactly what I wanted to see... ;)
(Unless this does not refer to the system boot, but if I am not wrong refers to the bootloader)
boot.img is your kernel and ramdisk
emmc_appsboot is your aboot (bootloader), although this is not a complete bootloader, it is the part most often talked about. sbl1 and sbl2 are not included in B06 but also have more static code that changes less often
 

ultramag69

Senior Member
Nov 6, 2007
5,996
1,080
Waratah
are there differences between the US and the EU rom? as i know is the hardware the same. though i am not sure about the modem. but the US rom should work on EU hardware and vice versa as well.

With a locked bootloader you'll probably find you can't flash any other region rom...
If you try make sure you have your stock rom on hand to reflash or you may end up with a brick...
 

TeutonJon78

Senior Member
Jul 24, 2010
574
287
are there differences between the US and the EU rom? as i know is the hardware the same. though i am not sure about the modem. but the US rom should work on EU hardware and vice versa as well.

The EU ROM is supposed to be closer to the Chinese ROM than the US ROM, as it doesn't include the stock android theme. The modem images are definitely difference. When I md5sum'ed the E07 ROM against the G-B02 ROM, there were only 2 parts the same, all of them inconsequential. The B02 ROM is also at the newer security patch level of July, like the U-B20 ROM is.

Does somebody know if Chinese Stock ROMs are inclusive of stock bootloader?

They release the full packages that contain any partition changed since launch. As @peramikic said, it doesn't include EVERY partition. That's the slight difference between a full factory rom and the full updates. The full factory image would include copies of EVERY partition to get the phone up from a blank state. The full OTA images just include everything that's changed since launch.

I also compared the OP3 released images against CM13 images for that phone, and it's basically the same setup of image files -- things like SBL1 and SBL2 just aren't included, as they aren't touched.
 
Last edited:
  • Like
Reactions: blessingme

ciko84xp

Senior Member
Jul 16, 2008
144
4
Rossano Calabro
With a locked bootloader you'll probably find you can't flash any other region rom...
If you try make sure you have your stock rom on hand to reflash or you may end up with a brick...

Right man! Just for this i try to understand if this is the right smartphone for me or not! Until 10 years i've used only my personal CustomROM with all my tweaks (my build.prop it's really big! :D ), but if ZTE can't give me this chance, my choice will fall on OP3! ;)

They release the full packages that contain any partition changed since launch. As /u/permikic said, it doesn't include EVERY partition. That's the slight difference between a full factory rom and the full updates. The full factory image would include copies of EVERY partition to get the phone up from a blank state. The full OTA images just include everything that's changed since launch.

I also compared the OP3 released images against CM13 images for that phone, and it's basically the same setup of image files -- things like SBL1 and SBL2 just aren't included, as they aren't touched.

You're right too... I hoped they were Factory Stock ROM and not OTA Updates... but I was wrong. :(
I hope ZTE will release the Stock ROM (full factory format, like Samsung), because i would cook my personal CustomROM (as I usually do), but I do not want to risk without having the ability to restore it! :(
 
Last edited:

ultramag69

Senior Member
Nov 6, 2007
5,996
1,080
Waratah
Right man! Just for this i try to understand if this is the right smartphone for me or not! Until 10 years i've used only my personal CustomROM with all my tweaks (my build.prop it's really big! :D ), but if ZTE can't give me this chance, my choice will fall on OP3! ;)

:(

But you can root the rom now thanks to tenfar, here - http://xdaforums.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
As you have root access you can alter or replace the build.prop, just not the whole rom.

Using the breakdown of the roms though it appears there are people looking for Un-officcial Bootloader unlock...
Time her may be our friend, unless ZTE wises up and unlocks them for us...
 

Top Liked Posts