yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] empat:
Hi! Tried to follow the steps:

Instaled Miflash, and trough Miflash tried to unlock bootloader. It was, apparently, successfull. After that, tried to flash B19 rom with TWRP.

Again apparently it was successfull, but it seems this was not the true: after that, for some reason, I was not able to boot into recovery or anything else (I think the bootloader was not truly unlocked).

I had to flash verson B 19 full. It was, however, verson B19 U, american. With that I succesfully booted the device.

In my country, however, this firmware apparently has no coverage for 3g or 4g signal, at last for my carrier.

Any idea of how to proceed? My fisrt intention would be to move to some chinese or european version, with enough coverage, then, if possible, proceed top root the device.

Thanks in advance!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] czeczek69:
I didnt understand guys, i should flash B19-NOUGAT_FULL (Nougat 7.1.1) first then B19-NOUGAT_TWRP (Nougat 7.1.1)? I am at A2017 B17 stock now...

Could you help me?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] 2CanSan:
Here we go. New to qualcomm so my first attempt was a complete failure. Got locked into a 5 second bootloop.

Thank heavens for jcaduono and his unbrick method. Encryption problems. All hell breaks out Should I format user data with fastboot before step 11?

1) Load drivers into computer and test ( Look in Device Manager)

2) Developers Options - Oem Unlock - USB Debugging

3) Reboot into EDL ( Power+Volume Up+Volume Down ) or adb reboot edl

4) Plug phone into computer - Run MiFlash - Refresh to find phone - Browse to A2017U_FASTBOOT_UNLOCK_EDL

5) Flash ( May have to refresh on error)

6) Power+Volume Up to enter stock Recovery

7) Select Bootloader

8) fastboot oem device-info

9) If locked - fastboot oem unlock

10) fastboot flash recovery twrp*file.img

11) Power+Volume Up to enter TWRP Recovery

BOOM
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] vikramanananda:
Hi Dev i like to downgrade my zte axon 7 to 6.0

I used your method to give life back to my phone

I like to downgrade to 6.0 by using MI flash but your post don't have B29-NEW_FULL (Marshmallow 6.0)

can you provide
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] 2CanSan:
I tried and failed. That B29 file is not available anymore I think, I have a kit but the phone would not let me

drop from Nougat to Mar. The bootloader would not install > 7 I can upload the file and you can try

http://www.android.gs/downgrade-zte-axon-7-to-android-7-0-or-android-6-0-stock-android-firmware/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] vikramanananda:
Thank you

i will check and try this method to downgrade

my really problem is i bought this phone from eBay marked as broken and now return

i managed to gave like by using your method once i boot i found the phone stuck

in google lock (FRP) i google for solution's but came up with nothing for 7.0

if i manage to downgrade to 6.0 i may bypass the google lock

hope you under stand my problem

thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] 2CanSan:
Did you try this method?

https://www.youtube.com/watch?v=IfhhkL-_fPY
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] czeczek69:
My phone is bricked, i can use EDL mode but computer recognize him as not previous (Qualcomm) but as QUSB_Bulk. What I should do?

---------- Post added at 02:57 PM ---------- Previous post was at 02:43 PM ----------

I can use TWRP & phone is unlocked but I cannot use any Stock firmware (md5 errors)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] 2CanSan:
QUSB_Bulk is correct

Just follow the instructions and it will be fixed unless the memory is bad

If MiFlash sees it ( Refresh) you are good to go.

If you do not get flash (Success) reset EDL mode, reconnect to pc, refresh MiFlash - Flash
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] czeczek69:
Mi Flash didn't recognize phone
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juliantentori:
My Axon 7 is dying! :(

Hi, i have a massive problem with my Axon 7, i gave it to my dad like 6 months ago but now it's starting to fail, right now I'm stuck in the boot logo even though I haven't messed with the Bootloader or anything; everything in the phone is like when i bought it, i tried to flash with Miflash the 7.1.1 that doesn't have TWRP and i succeded but the phone is still stuck in the logo. How can I solve a problem like that?

Update 1:

I continued to turn down the phone and now I'm stuck in EDL mode :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ScaryBugThing:
Hey - I had to get a replacement Axon 7 for my GPS, and when trying to run this process again to unlock and roll back to B19 to root (ensuring Qualcomm drivers are installed, rebooting to EDL mode, and attempting to flash the UNLOCK file), I just receive the following when trying to run MiFlash:

[0.00 COM4]:[COM4]:start flash.

[2.01 COM4]:cannot receive hello packet,MiFlash is trying to reset status!

[4.52 COM4]:cannot receive hello packet,MiFlash is trying to reset status!

[7.02 COM4]:try to reset status.

[7.03 COM4]:Switch mode back

[7.03 COM4]:cannot receive hello packet,MiFlash is trying to reset status!

[7.04 COM4]: object reference not set to an instance of an object.

To confirm, my device shows up in MiFlash, and there's no error in the driver installation in Win10's Device Manager. I've extracted the UNLOCK file and selected only the subfolder when extracted. Both OEM Unlocking and USB Debug mode were enabled in the Android main system (if it matters). I've tried restarting EDL mode, tried reinstalling the driver, and tried every other USB port available. Same results.

Strangely, this happens only when I try to flash a second time after a restart. The first time, it always first gives me the error below, but then when I just hit Flash again, it gives me the error string above:

[0.01 COM4]:[COM4]:start flash.

[0.01 COM4]:received hello packet

[0.01 COM4]:donwload programmer D:\Sorted\Random\Axon\A2017U_FASTBOOT_UNLOCK_EDL\A2017U_FASTBOOT_UNLOCK_EDL\prog_ufs_firehose_8996_ddr.elf

[0.02 COM4]:sahara read end error with status:9

[0.02 COM4]:sahara read end error with status:9

If anyone has any suggestions how to resolve this, I'd be grateful.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sauerkraut17:
Use adb reebot edl command. You device seems to not be fully entering edl via the button press. I had a similar issue and using the reboot edl command was the only way I get my device in true edl mode. I posted this a page or so back
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ScaryBugThing:
Thanks! I went back and also learned this after trying and succeeding with the Axon 7 Toolkit, so confirmed this works. Did you ever find a button combination that would put it in EDL, or did only ADB commands only ever work? Just wondering if ZTE has changed the hardware-initiated EDL process.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DMTomas:
Geeez dude, thanks! saved me=) for anyone having problems like "21:06:50 COM3]:[COM3]:start flash.

[21:06:52 COM3]:cannot receive hello packet,MiFlash is trying to reset status!" - 2 things:

a) unzip the file first:)

2=) try googling miFlash download - and download newer version - for me, a MiFlash20161222 version did the work.

edit:

oh, and c) if you are on chinese phone - don't forget you will need to flash A2017_N_Modem.zip - else you'll not have cell reception
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kodram:
Still no chance of getting B19 working on CH A2017 ? B19 rom is working fine, but no cellular signal :/ , installed twrp/unlocked ,then trien with N_Modem, phone wont start:/ iam so sad
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WADE13x:
i can't flash oem unlock it says hello file can't be recieved
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jedruch:
Did it on chinese phone - don't have cellular signal

Hi,

I've seen couple people with similar issue but no response. So I flashed files from the first post, but none of my sim cards is recognised. Can I flash any drivers? or can I flash stock A2017 chinese system to revert this?

Thank you
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gidron79:
Axon 7 Toolkit

I have B32 and trying to unlock bootloader and install TWRP. I get success when using toolkit to unlock bootloader but my device state is showing locked. What steps do I need to try if any for unlocking bootloader and installing TWRP. I have the A2017U Axon 7 running 7.1.1 and want to root my phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jedruch:
works!

Managed to revert changes with EDL recovery package from Link below:

https://xdaforums.com/axon-7/development/axon7-official-firmware-version-b07-cn-t3551590/post71394233
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gcerkez:
Did you try running the no verity package over at https://xdaforums.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715

look at step 7. Do that and it may decide to boot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
ZTE has created an edl package for B32!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nsabir:
It seems as though us A2017G users are being deprived of most of the fun stuffs. Plus, still no solution to DFU bricks.

Still haven't been able to unbrick my G version. Hating ZTE for putting the G models in a different state than the QDLoader after brick (DFU).:(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shia786:
Can you John the hangouts group can probably be found in the lineage thread someone where, search hangouts

---------- Post added at 03:10 PM ---------- Previous post was at 03:10 PM ----------

We might have a fix for you managed to ubvrick someone elses as well
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Yes
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] psyfer5:
Please correct me if I'm wrong, but You have a way to go from b29 unlocked w/ TWRP to B15 unlocked with TWRP without downgrading or going directly to stock?

I have to ask because that's what got me in trouble the last time...;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Harmtan2:
You sir are amazing. I will get this done tonight!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KyJelly69:
umm, i was using my phone and checking out the software and click "other" - "Check sha256" and now it says it's flashing. What exactly is it flashing?

update:well when it reached the end the counter kept going so i stopped the application and rebooted. nothing seems to have happened. thank god
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Harmtan2:
So I did this with Nougat, got the bootloader unlocked, but I don't have TWRP. Can someone point me in the right direction to get twrp on the phone? I was on nougat B15 build and used that bootstack & items.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
if you ended up booting the OS (or at least almost booting it) then it will be replaced with stock recovery. You can flash it again with MiFlash after unlocking OR you can just go into fastboot and flash TWRP like normal. ex. fastboot flash recovery C:\path\to\A2017U_B15-NEW_TWRP_EDL\twrp-3.0.4-1-ailsa_ii.img

then navigate to recovery with volume buttons and select with power.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xDaDeevellopar:
When I tried to flash B15 from Lineage (and also tried with B29), I get stuck on the Linux Tux logo. Also, I tried flashing both B15 and Lineage's bootstack/loader. Help?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Harmtan2:
Oops haha I should have known that... Got it reflashed! Thanks for your help & your amazing tool! For some reason I couldn't get fastboot to push it, but whatever. I'm in.

---------- Post added at 02:29 AM ---------- Previous post was at 02:11 AM ----------

Ugh... Now my phone is stuck on encryption. I erased the data, art chache, internal storage & cache... It won't go away.... Any advice? I did that procedure before I flashed Lineage & I got it, but now I'm still getting it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcadduono:
[Format Data] button to remove encryption, NOT factory reset or advanced wipe data.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Harmtan2:
I've done that, it's in Wipe-> Format Data Correct where I have to type in YES to verify? This is my Log

Full SELinux support is present.
MTP Enabled
Formatting Data using mkfs.f2fs...
Done.
You may need to reboot recovery to be able to use / data again.
Updating partition details...
...done
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
Good primer on flash storage structure on newer androids: Link
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Harmtan2:
Can anyone point me to the B29 or B15 Nougat Image so I can rollback & try this again? I'm now in a EDL only mode & Recovery is not booting.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
Edit. What do you mean recovery is not booting? What do you get when you try to boot into recovery?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Catalana:
The order of steps listed is a bit confusing, as Altomugriento listed "step 2" twice, so were is your step 2.5 to be placed?

Here is the way I understand it:

1) Enable "OEM UNLOCKING" under Developer Options (still in stock Nougat 7.0)

then boot into EDL mode

2) After flashing with MiFlash,

3) a reboot will take me into TWRP recovery, not stock, correct?

4) I then reboot again into the bootloader from recovery (TWRP)?

5) I issue the 'fastboot oem unlock' command? I still have stock Nougat 7.0 on the phone, correct?

?) where am I now? Do I need to reboot again into TWRP?

6) I then wipe system in TWRP (your step 4), instead of rebooting to TWRP as in Altomugriento's step 4. Do you wipe Dalvik and cache as well?

7) I then flash LineageOS and Gapps, as in Altomugriento's step 5.

8) I then wipe the data partition ( [Format Data] button on wipe page of TWRP)

9) Restart

Sorry for being nitpicky, just need to clarify the order. So many details for a newbie. Anyway, this is game changer for the Axon 7.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Harmtan2:
It forces it back into EDL mode. I get boot screen & then crash.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
You flashed the appropriate package for your device?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Harmtan2:
Ya... I figured out my idiot move. I re-locked the bootloader using 'fastboot oem command'. I had already flashed Lineage so the stock ROM wasn't there to restore the stock recovery. I have a kid who needed attention, and I forgot where I was... Ugh... I think I just screwed myself. My only hope is to find a way to flash a factory image.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
Both the B29 and B15 packages come with the b20 fastboot. It's worth a shot trying the fastboot oem unlock again.

You could use tennear's tool to reflash the signed twrp. That should take even on a locked bootloader. Once twrp is in place, you could flash the stock system and unlock the BL.

If that fails, you could try flashing boot and system through fastboot (fastboot flash boot {kernel_filename.img}, and system - fastboot flash system {system_filename.img}. I'm not sure if the b20 fastboot will permit that or not.

You're not the first to relock their bootloader. This seems to be a common theme for some reason. IMO once unlocked it stays unlocked. There should be no reason to relock it ever.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
Really? Well hot darn that's surprising
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
And...it didn't work. MiFlash always froze at some point in the process. It also somehow locked the bootloader.

Guess ZTE didn't test it before they released it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
Thank you for taking the risk. I knew it was too good to be true
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Maybe it's not meant for MiFlash. The content is somewhat different from the packages in this thread. I'm trying QFIL now.

---------- Post added at 11:20 PM ---------- Previous post was at 11:18 PM ----------

Didn't work. I'll post about it on the ZTE forum.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
Update: The B32 package flashed! The bootloader has to be unlocked first.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
Awesome, thanks for the update my good sir
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] spotmaxdog:
I think I did a stupid thing with my phone and can't get it back up.

Here's what I did:

1. Relocked bootloader

2. Flashed B19

3. Rebooted to "enter password to start android"

4. Flashed B19 + TWRP and realized TWRP won't work on a locked bootloader

Crap.....

How would I extract myself from this mess? Can't get into fastboot to get to TWRP and can't get to TWRP without fastboot.

:crying:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DMTomas:
Is your phone booting? Or is it stuck on the blue zte axon window? If you can boot, no problem, you unlock bootloader etc. If it's stuck on the blue zte axon screen - there's a miflash app (check unbricking zte axon thread on xda) - you can resurrect your phone using that - follow the instructions all will be good (btw, if you get errors when trying to flash - try different versions of the app). Happy resurrection mate

Edit: crap, this is the thread for unbricking - so follow this one, sorry, a bit drunk, and lost =)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] spotmaxdog:
Haha. It's all good. Fixed it when MiFlash froze and corrupted the file system so the next time I flashed the full image it took and no longer requested my password on bootup.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cablespider:
Just remember to be 100% stock before relocking.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] J0nhy:
I downloaded b32 from here and it works just fine bro

https://xdaforums.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] foxtrotdragon:
Help, all I get is the screen saying device cant be check for corruption, and if I leave it alone nothing happens, or if I press the power button I get some stupid Penguin when I try to boot into the system now
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
Do we unzip these EDLs before flashing with Miflash?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dm-s:
Hello from a newbee,

I've got Axon 7 Mini, B2017G, I know it's different device. It seems all but recovery partitions missing/corrupted/deleted.

My question is - how is the set of files, like in your ZIPs, are created for specific phones. Let's say I get a hold of same model, is there a tool to create the full firmware set, in the likeness of B15-NEW_FULL_EDL.zip?

I am able to get the phone to connect on EDL, I can get to recovery menu, and I can flash boot and recovery partition with tuliptool, as in https://xdaforums.com/axon-7-mini/development/unlock-tuliptool-unlock-twrp-custom-boot-t3682781 thread, and I can connect to MiFlash with Qualcomm driver. But that's it.

Any help getting to know how to create EDL flash files highly appreciated.

Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
Thank you so much. This was the best info for the same issue I was having. Axon 7 is flashing and coming back alive!!!:good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ygb7:
EDL Mode - Wrong COM Device

Need help. I followed instructions & installed the Qualcomm QUSB_BULK drivers. My ZTE Axon 7 (A2017U) should show up in Windows 10 device manager as...

COM port called "Qualcomm HS-USB QDLoader 9008"

However, it shows up as..

COM port called "Handset Diagnostic Interface(DFU) (COM5)"

[IMG="Wrong COM Port"]https://pasteboard.co/GOsLckL.jpg[/IMG]

I already enabled OEM Unlock from settings menu on phone. Also enabled "USB Debugging" from Developers options menu. Rebooted phone in EDL mode.

This problem is preventing me from I can't use EDL method & MiFlash to flash unlocked bootloader & TWRP.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] newdev:
OKAY so I got the phone registered as the right COM port driver, but now people are saying I need to ADB reboot edl in order to get into a working EDL. But since its now reading as a com port I can't get ADB to connect. What should I do about this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blcistheking:
Also am confused on how to get edl working properly with Mi Flash. I keep getting suck at 5% with a "can not read from port 3" error,
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] awdrifter:
My phone is recognized as "Qualcomm HS-USB QDLoader 9008 (COM5)", but the MiFlash fails and I can't send the "adb reboot edl" command, it says no device found. Is this the end of the road?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lafester:
Only if you give up.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] awdrifter:
Looks like I'll have to do this?

https://xdaforums.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898

I'm not sure if I'll attempt it. I think this is probably bricked for good.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lafester:
Only if you are stick in dfu mode. Are you?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] awdrifter:
I'm not stuck in DFU mode, I need to get into DFU mode. I was trying to get into EDL mode, but it won't completely get into it (pressing vol up, vol down and power can't get it completely into EDL). In another thread it was mentioned that some Axon 7 might need the adb reboot edl command to actually get into EDL mode. However, adb can't find the device. So I'm pretty sure I'm in the same boat as that thread's OP. I will need to short that pin to force the phone into DFU mode so it'll accept a flash of the FW. But I'm giving up for now, I actually got a new phone (Samsung S8+, awesome phone) so this phone was going to some family members. Looks like they'll just have to use their older phones instead.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
No, you just don't understand DFU mode. Whatever leads you to think that you're halfway in EDL is not like that. You are on DFU, where you can simply do nothing unless you have the tools ZTE has. To get to EDL you need to:

a) get to a mode where there's adb (FTM mode has it, but very few people have been able to access it. It consists on draining the battery completely and then using power and volume down (presumably with the USB connected). If it works you'll see a box with 'FTM' inside. from there issue 'adb reboot edl' and you can use miflash

b) use the 4th category brick repair manual and fix it
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] awdrifter:
Yes, I need to get into DFU mode. I tried the vol up + down + power, it's recognized by my pc as 9008 in device manger, that's consistent with EDL mode. But I can't flash it with MiFlash because I can't send a reboot EDL command. So I need to get into DFU mode to force it to flash. But I'm not going to spend more time in this phone for now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Sphexi:
I flubbed TWRP so got to where I could only get into bootloader/recovery/EDL, so went through flashing the B19 image back onto the device. Worked fine, and I've since done the OTA upgrades back to B32, but issue is there's no IMEI at all on the device so it won't connect to mobile. Literally worked fine a few hours ago before I started messing around, but now those fields are all 0s in the status pages.

I'm assuming it's hardcoded somewhere and I just need to push a command to reset it or maybe flash the modem again, any ideas?

Edit:

So I found: https://www.gizdev.com/repair-imei-snapdragon-device/

But I can't get the phone to show up in Device Manager as a Qualcomm anything, and Driver Identifier is useless, didn't find a thing. I can ADB shell into the phone, set the property, but at that point I'm stuck. I just need to write the IMEI back into the phone and all should be good again.