[ROM] ZTE Axon M Stock Firmware/Firehose

[myfire888]

i'm not living in us but i got the phone from somebody who brought this phone from us . it's sim unlocked not bootloader thats why we cannot flash custom roms. I have the update but i cannot flash it . ZTE is complicated phone to update . i have a samsung at&t and i update without an issue . samsung is easy to update. Before you update your phone do a research regarding your phone's model. Your phone should support 4G / LTE . Did you check network settings ? Mobile networks or network settings . it should say 2G/3G/4G etc.. check it. I cannot find any tutorial or solution to flash update on axon m unfortunately. I downloaded every single drivers but still can't flash it .

nope. there's only an option on prefered network type : GSM/WCDMA/LTE (I think wcdma is 3g and lte for 4g ?).
but I can only get e (which means edge) on the top notification.
If i change it to "LTE/WCDMA", then there is no internet at all (actually there's no signal at all, cannot even make phone call and sms if I choose this)
I have inputted and double check every apn settings for my simcard, so the apn should be right. and the simcard works 4G perfectly on my xiaomi phone.

just incase. my phone is unlocked because I can use it to call, sms and edge with my simcard right ? (it's the first time I bought at&t phone which have to be unlocked, so maybe I just misunderstand the terms lock/unlock, so maybe this phone still locked ?).

and the mobile tethering wouldnt on too, whenever i click on, it hangs for a while then error msg : "there is a temporary network problem that prevents the enablement of the mobile hotspot function. please retry later"

 

[galaxys2ci]

I think something is wrong with ATT Z999 firehose programmer file that is provided by developer. Because it doesn't work. I did install every single drivers correct and my phone is detected by pc . booted into edl mode via adb command but it always gives a sahara fail error. I do not know what to do at this point . Just hoping that anyone comes up with an idea to solve this.
Thank you
Regards

 

[deadman96385]

I think something is wrong with ATT Z999 firehose programmer file that is provided by developer. Because it doesn't work. I did install every single drivers correct and my phone is detected by pc . booted into edl mode via adb command but it always gives a sahara fail error. I do not know what to do at this point . Just hoping that anyone comes up with an idea to solve this.
Thank you
Regards

The programmer is vaild, just the phones edl mode is not standard so it requires some custom initialization process that is yet unknown to anyone outside of ZTE.


Sent from my iPhone using Tapatalk

 

[galaxys2ci]

Ok thank you for your respond and i appreciated that . I have never had zte before , that is the first one that i have and never played with edl mode before. I always had samsung and they are easy to update . But zte not that easy . Could you tell me how to do this process if you do not mind . I do not know how to do it . There must be a way to do it i believe.

Again thank you for your respond Deadman96385
Regards

 

[Razor512]

Can the stock EDLs be used to update the the Z999 AT&T version of the device.

Since if you purchase this device to use on a different network, the updater will not work for OTA updates, can the EDL be used for this?
Want to use Nougat AT&T Z999 B37


I was also wondering, the website only lists B35 (forum will not allow me to post a link, but it can be found by googling the change logs for the Z999).

 

[deadman96385]

Can the stock EDLs be used to update the the Z999 AT&T version of the device.

Since if you purchase this device to use on a different network, the updater will not work for OTA updates, can the EDL be used for this?
Want to use Nougat AT&T Z999 B37


I was also wondering, the website only lists B35 (forum will not allow me to post a link, but it can be found by googling the change logs for the Z999).

Currently edl mode is not working properly on the axon m so these files are useless.

 

[Razor512]

Hopefully one day there will be a way to update devices like this without having to purchase AT&T service.

Currently stuck on B30.

 

[Reverender]

i updated/unbricked mine with UAT now on B37 but not mutch has changed.

 

[galaxys2ci]

Hello everyone , finally i had a success with flashing my z999 axon m from B22 to B37. I was trying with qfil but wasn't successful and i did this firmware upgrade with uni android tool (uat) and it worked. I would like to thank to developer Deadman96385 for sharing firmwares and other necessary files that i was looking for .

Regards

 

[deadman96385]

i updated/unbricked mine with UAT now on B37 but not mutch has changed.

Hello everyone , finally i had a success with flashing my z999 axon m from B22 to B37. I was trying with qfil but wasn't successful and i did this firmware upgrade with uni android tool (uat) and it worked. I would like to thank to developer Deadman96385 for sharing firmwares and other necessary files that i was looking for .

Regards

Would either of you guys be willing to test flash a magisks patched boot.img with uni. You take the b37 boot.img put it on the phones storage and then in the magisks manager app click the install and then patch boot.img button then find and select the b37 boot.img this will tell me what the status of the bootloader is and what the next steps will need to be to allow ROMs and such.

 

[Jemini024]

Would either of you guys be willing to test flash a magisks patched boot.img with uni. You take the b37 boot.img put it on the phones storage and then in the magisks manager app click the install and then patch boot.img button then find and select the b37 boot.img this will tell me what the status of the bootloader is and what the next steps will need to be to allow ROMs and such.

just got the phone in the mail... im up for playing around with some thing..i have experience working with lots of other phones.

---------- Post added at 10:35 PM ---------- Previous post was at 10:31 PM ----------

Hello myfire888 , according to my knowledge you cannot flash custom roms or custom recoveries to AT&T devices unless you unlock their bootloaders. I have an AT&T AXON M as well . I got it a month ago and it is 4G/LTE support. Phone is good but as i said we cannot flash custom roms on AT&T devices or unlock bootloaders. I've done a research and there is no way to unlock bootloaders of at&t devices(thsi is what i know so far, maybe there are some people who can do it but not me ). I have a galaxy S7 EDGE AT&T and it is the same like axon m. You need updates from AT&T only . Recently i found AT&T 's updates from xda but i was unable to flash the rom. I installed every drivers and other files and got a sahara error failed many times. I will not buy AT&T devices anymore. They work good but we cannot flash custom roms or recovery . We are lucky that some developers upload these updates on XDA otherwise it is really hard to find them. AT&T does not provide their update on their website. That sucks.
Good luck friend

Comparing this phone to the galaxy s7 is wrong in all ways..locked bootloader vs signed...and giving miss information is not cool..you are able to flash other firmware as long as same boot version on the s7..i can confirm this because i have a g930p/g935p aka sprint using g935u/g930u both phones rooted and running smooth on bootloader v9... example "https://forum.xda-developers.com/verizon-s7-edge/how-to/s7edge-verizon-firmware-modded-lte-bands-t3827369"

 

[01000010]

Would it be possible to flash the China Oreo ROM over the TIM-branded italian Axon M (4g/64g)?

 

[Sili213]

Would either of you guys be willing to test flash a magisks patched boot.img with uni. You take the b37 boot.img put it on the phones storage and then in the magisks manager app click the install and then patch boot.img button then find and select the b37 boot.img this will tell me what the status of the bootloader is and what the next steps will need to be to allow ROMs and such.

I just did this and it seemed to have patched it successfully. Did it to the b37 boot.img like you requested, while running on b35. Thanks for all you do around here.

- Device platform: arm64-v8a
- Existing zip found
- Copying image to cache
- Boot image is signed with AVB 1.0
1022+1 records in
1022+1 records out
1047368 bytes transferred in 0.011 secs (95215272 bytes/sec)
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER      [0]
KERNEL_SZ       [12763729]
RAMDISK_SZ      [5530226]
SECOND_SZ       [0]
EXTRA_SZ        [0]
RECOV_DTBO_SZ   [0]
DTB             [0]
OS_VERSION      [7.1.2]
OS_PATCH_LEVEL  [2018-09]
PAGESIZE        [4096]
NAME            []
CMDLINE         [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] buildvariant=user]
CHECKSUM        [6786e511bb27a849e5df52a8140e52fb83d053ce]
KERNEL_DTB      [3577041]
KERNEL_FMT      [gzip]
RAMDISK_FMT     [gzip]
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Backing up stock boot image
- Patching ramdisk
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[true]
Remove pattern [,verify]
Remove [verity_key]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [fstab.qcom] -> [.backup/fstab.qcom]
Backup mismatch entry: [init] -> [.backup/init]
Backup missing entry: [verity_key] -> [.backup/verity_key]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Loading dtbs from [kernel_dtb]
Patch @ 019857B6 [736B69705F696E697472616D667300]->[77616E745F696E697472616D667300]
- Repacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
HEADER_VER      [0]
KERNEL_SZ       [12763729]
RAMDISK_SZ      [5530226]
SECOND_SZ       [0]
EXTRA_SZ        [0]
RECOV_DTBO_SZ   [0]
DTB             [0]
OS_VERSION      [7.1.2]
OS_PATCH_LEVEL  [2018-09]
PAGESIZE        [4096]
NAME            []
CMDLINE         [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] buildvariant=user]
CHECKSUM        [6786e511bb27a849e5df52a8140e52fb83d053ce]
KERNEL_DTB      [3577041]
KERNEL_FMT      [gzip]
RAMDISK_FMT     [gzip]
Repack to boot image: [new-boot.img]
HEADER_VER      [0]
KERNEL_SZ       [12762953]
RAMDISK_SZ      [5722323]
SECOND_SZ       [0]
EXTRA_SZ        [0]
RECOV_DTBO_SZ   [0]
DTB             [0]
OS_VERSION      [7.1.2]
OS_PATCH_LEVEL  [2018-09]
PAGESIZE        [4096]
NAME            []
CMDLINE         [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] buildvariant=user]
CHECKSUM        [0778bfc5598863f2569744363a8db323b81f3379]
- Signing boot image with test keys

****************************
 Output file is placed in 
 /storage/emulated/0/Download/magisk_patched.img 
****************************
- All done!

 

[phidung3721]

I just did this and it seemed to have patched it successfully. Did it to the b37 boot.img like you requested, while running on b35. Thanks for all you do around here.

Would you mind sending me the b37 boot.img? I don't know why but it would take me 7 hours to download the full zip. Thanks mate.

 

[Reverender]

Got no pc atm. Will try patching boot img and then flashing it again. Who knows. Ill try on wendsday

 

[Reverender]

Ive patched it and reflashed it with the new boot img.
Sadly it didnt work phone reboots twice then ends up in android recovery.

 

[Reverender]

can someone create (compile) TWRP for Axon M recovery.img ?

 

[01000010]

Has anybody tried WITH SUCCESS to install the CN ROM over the TIM Firmware by using this technique (similar to back2stock used elsewhere)?
(or could somebody please test this idea?)
- downloading the CN update package (e.g. http://devicedownload.zte.com.cn/support/product/201801151455513/sd/20190228103417154.zip)
- extracting the update.zip from it
- extracting the META-INF/com/google/android/updater-script
- commenting the second line as shown below to deactivate the check on the ro.product.name=P996A26 property
- replacing the META-INF/com/google/android/updater-script file in the update.zip with the commented one
- uploading the update.zip file to the external sdcard
- rebooting the phone?

getprop("ro.product.device") == "fujisan" || abort("E3004: This package is for \"fujisan\" devices; this is a \"" + getprop("ro.product.device") + "\".");
# COMMENTED getprop("ro.product.name") == "P996A26" || abort("This package is for \"P996A26\" product; this is a \"" + getprop("ro.product.name") + "\".");
ui_print("Target: ZTE/P996A26/fujisan:8.1.0/OPM1.171019.026/20190218.120220:user/release-keys");
show_progress(0.750000, 0);
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") ||
  abort("E1001: Failed to update system image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
package_extract_file("ddr.img", "/dev/block/bootdevice/by-name/ddr");
package_extract_file("echarge.img", "/dev/block/bootdevice/by-name/echarge");
package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");
package_extract_file("rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("mdtp.img", "/dev/block/bootdevice/by-name/mdtp");
package_extract_file("xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("recovery.img", "/dev/block/bootdevice/by-name/recovery");
package_extract_file("sec.dat", "/dev/block/bootdevice/by-name/sec");
package_extract_file("NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("fingerid.mbn", "/dev/block/bootdevice/by-name/fingerid");
package_extract_file("splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
package_extract_file("cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("keymaster.mbn", "/dev/block/bootdevice/by-name/xblbak");
show_progress(0.200000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/persist", "/persist", "");
create_persist_flag();
set_progress(1.000000);
unmount("/persist");

 

[lulujyc]

Are there anyone can tell me the possibilities to flash the Japanese version directly from the Chinese Oreo 2..1? (Hardware is 6g ram 128g rom) Thanks?

 

[01000010]

Yesterday the updated version of TIM-branded italian firmware has been distributed. (version TIMV1.0.0B07, Android 7.1.2)
Has anybody a link to it?