yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
No, this is all proprietary stuff.

I know how to use EDL because I worked on EDL programming at cyngn as part of a project to make a factory flash/reset tool. Most every major OEM has some sort of similar tool -- Samsung has Odin, LG has LGNPST and LGUP, etc. Unfortunately, cyngn imploded before the tool was released. Pity, it was very nice and easy to use tool.

Qualcomm provides an API to talk to devices in EDL mode. Unfortunately, they only provide Windows libraries to link against. I am a die-hard Linux user, so I said no thanks and developed a cross-platform code base from the spec documents that runs on Linux, Mac, and Win64. (This is why my tool uses the WinUSB driver instead of the Qualcomm driver.)

I figured out the unlock by reading the aboot source code. It's publicly available:

https://source.codeaurora.org/quic/la/kernel/lk

In particular, look for read_device_info and is_unlocked in this file:

https://source.codeaurora.org/quic/la/kernel/lk/tree/app/aboot/aboot.c?h=LA.BR.1.3.6-04710-8976.0

Having said all that, it would be feasible to write a XML programmer document that you could feed to QFIL to do the unlock. After all, you only need to change one byte in the first sector of the devinfo partition...
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] elliwigy:
ok cool.. i have some reading to do lol.. we actually just successfully restored a few S8+ from hard bricks using edl.. We already have the prog_ufs_firehose_8998_ddr.elf (and lite).. not sure if youre interested but if u can hit me up on hangouts id like to see if u could help abit moreasit took me like 6 months just to figure out the xml to flash the BL partitions lmao

we also already have root so if its similar on our device might just be able to write the bit since we are rooted if its not secured/encrypted partition..

i also have rpmb fuse blowers, signers, boot debug, uefi debug, boot xbl core,splash img creators etc etc.

looking through the files a lot of the tools are backwards compatible to other QC chipsets and itappears they take original toolsand simply add support for newer chipsets.. so let me kno if interested in seein what we got :)

also, do you know what the "sti" and "toolsfv" partitionsare? i was messin around with some of the images in the package i recieved and those 2 partitions appeared and arent on others devices of the same device/variant? I also now am having trouble getting to edl haha, it just reboots normal.. so i am going to try a fresh start later today..

i will start reading up.. I believe theS8/S8+ are one of the first in awhile at least where asammy phone can actually adb reboot edl.. its looking like our only option considering they disable/remove fastboot for us..

however they were kind enough to leave oem unlock allowed = 1 as well as oem unlock supported as 1 just no way for usto run the commands
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] elliwigy:
is devinfo originally like the attached pic? lol
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] kurok154:
Is there the way to get European version to Edl before boot? In case it falls into bootloop?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Does the Euro version not respond to the key combination at boot? I don't know of any other way to force it into EDL mode.

You just need to be extra careful to make sure that you can always boot from either boot or recovery. That is, follow the advice in the OP. :)
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] eDooM85:
Reboot edl

Try this

adb reboot edl
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] fallen00sniper:
interesting, i have the us model and am still on 7.1.1B12 didn't know there was a B14.

B2017G_USAV1.2.0B14 is available to download... Would it hurt anything to update?

Currently using an iPhone I repaired until I can get it carrier unlocked and sell it... has to be used for 9 more months on the carrier lol, so not completely stressed over updating.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Should be fine to update. It's probably just minor fixes. I'm staying on b12 until the official unlock per zte request.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] kurok154:
It doesn't respond to the key combination, and always boots into logo. So if I have bootloop I can't go to the Edl. In axon 7 there is control spot, that you can short circuit in a board and get to Edl. Maybe someone could see or already knows if mini has this spot too?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
A control spot on the mother board? All phones have that. But it requires disassembling the phone, which is not easy.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Test
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] kurok154:
Lenovo zuk z2 reboots into Edl by short circuit data- in USB and connect it to charger. Maybe this phone have this feature too?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tprfd:
The one from Canada seems to be a bit different in name as well.

From Recovery:

Supported api is 3

ZTE/P852A15/verdandi

6.0.1/MMB29M/20161226.224110

[MENTION=4126377]tdm[/MENTION] I suppose this version is likely out of luck for unlock/custom ROM? 'Verdandi' rather than tulip as the name seems like it may be a showstopper. Correct?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Hmm, I'd start by requesting kernel source from ZTE.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tprfd:
So in other words... It is a showstopper.

I guess I will pick up the USA version and return this oddball one. Thank you for your help/work and quick reply.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Well I wouldn't put it that way. It's just a different device inside. It's likely that the same kernel could run on both variants, but I'd need to look at the kernel source.

It would be nice if you or someone else could do this, as I'm sure others also have this variant and it would be nice to support it.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] parawizard:
Looks like I have the same version! Will have to do some digging. Darn Canadian carriers :/
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tprfd:
I emailed tech.sp@zte.com.cn asking for source for the verdandi one. Not sure what else we can do.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] parawizard:
I just did the same. It may just be the same source different kernel options?

I downloaded the nougat and non nougat source for b2017g and will have a look at it.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Pete_Mitchell:
since works with qualcom cpu would be possible to adapt this tool to unlock g4 h818p variant?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
This tool requires the firehose binary to work ... someone found a leaked firehose binary for this device.

If you can find a leaked firehose, I can make a tool. Otherwise, no.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tprfd:
I found a website that listed 3 versions of the B2017G.

Tulip

Verdandi

msm8952_64

Would this bootloader unlock only apply to the tulip version of this particular device? Or should it in theory work for verdandi and msm8952_64 as well? Any canucks try the verdandi unlock?

I know the verdandi version is single sim, and lacks NFC (not sure if it is hardware or software disabled).

Also I have asked ZTE for the source of the verdandi marshmallow device. They have also confirmed separate versions and have said should get it in a couple of days.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
The unlock should work for all variants, I think. Give it a try.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] bromanbro:
I'm thinking of buying the pcmobile verdandi mini - any chance of that getting unlocked? How can I check if it's a carrier-locked bootloader? Thanks for your hard work so far guys.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tprfd:
PC Mobile Axon 7 Mini is the verdandi version. Please see the post right before yours. Not sure what verendas is if you mean something else.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] bromanbro:
Sorry let me be clearer...is there an unlocked verdandi version or is pcmobile's\virgin's the only one? I don't wanna buy it if it turns out the bootloader is carrier-locked. Thanks.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tprfd:
As far as I know, carrier-locked bootloaders just mean the carriers have made a deal with the manufacturer where the manufacturer is not allowed to release the unlock keys. I don't think there is anything different between a bootloader on a locked, "free market" USA model except that if ZTE has made a deal with PC Mobile, an 'official' bootloader unlock will never be released for verdandi, whereas ZTE could provide the keys for those free market versions at their own discretion, without answering to a carrier.

What this thread is stating is that the keys are not needed, TDM has developed a method to unlock the bootloader without any official means. An official unlock has not been released for any version (neither tulip or verdandi) BUT the tool has not been confirmed to work on verdandi, only tulip. I don't think anyone else outside Canada has said they have a verdandi version so unless you want to import a phone from the US, you're stuck with verdandi. I have not confirmed if this phone is unlocked from the store, but I highly doubt it.

You could buy the phone, try the unlock from the OP and then return it if it doesn't work. I think PC mobile has 15 day returns but you should verify that yourself and do it at your own risk.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tprfd:
I am shocked... Verdandi source posted quickly:

http://opensource.ztedevice.com/

ZTE B2017G Marshmallow(6.0.1) Kernel(3.10.84)

[MENTION=4126377]tdm[/MENTION] re: Lineage...awesome job!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] maestromony:
Btw:

I confirm this. It is usable for european version.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] bromanbro:
I'm thinking of picking up a Verdandi phone but it's stuck on Marshmellow...has anyone used this tool successfully with the Canadian PCMobile Verdandi version? Thanks.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Shockling:
I have been trying to flash twrp all night to no avail. I have the tuliptool running and am getting a success message when I flash but when I boot into recovery I still have stock miflavor. Any ideas what I could be doing wrong?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Are you booting straight into recovery by holding the volume up key? I think stock mifavor has a setting to over write recovery on startup, maybe that's the problem.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Please note the OP has been updated. Changes:

* Win32 version included.

* Read and write take a filename now.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] TheSSJ:
So, EU model user here...

I tried to unpack my current boot image and modifying the fstabs myself. Repacking worked also without problems, so I went on flashing as I read after your research, that the device doesn't seem to be locked. Unfortunately, after flashing my modified boot or even an untouched one I just unpacked and repacked, the device shows the ZTE logo, then reboots and loads TWRP. What I assume is, that the bootloader just checks for an untouched boot partition. It doesn't seem to check the recovery, but I think I need to check if unlocking the device helps booting a custom boot image.

Honestly I just want to root the device to transfer my app-data from my old device to the ZTE, but when I flash the superSU zip in just loops endlessly to the ZTE screen...

EDIT: Do not unlock the device with EU model and Nougat, I think I bricked it...

EDIT2: at least I managed to come into EDL mode (TWRP showed the device for a short moment in adb), there I flashed the stock boot and stock recovery image. It booted to recovery,showed an Erase message and it booted again...
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Regarding unlocking: if the device boots TWRP, it's pretty much guaranteed to be unlocked. It is theoretically possible that aboot would only verify boot but not recovery, but I cannot imagine any OEM doing that. So 99% chance that your repacked boot image is not correct in some other way. You could verify by flashing a functional TWRP image to the boot partition.

Regarding app data: you don't need root to transfer app data. adb has backup and restore commands that you can use for this. I'm sure a google search would turn up lots of information on how to use it, but it's basically like this:

1. Connect the old phone and run:

adb backup -f app.bu <package-name>

2. Connect the new phone and run:

adb restore app.bu

package-name will be something like com.company-name.app-name depending on the app.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] TheSSJ:
Thanks for the feedback, I used the newest mkbootimg from lineage, used every parameter I retrieved to place kernel, ramdisk, tags, etc. An untouched boot.img boots, but when I modify just the fstabs, the phone already ceases operation and boots to recovery afterwards.

2nd reason why I want to root it (and know how to pack boot images correctly) is that I want to write a custom kernel as I did for my previous phone model. I need to research some more to find out where the discrepancies happen

I unpack the image and have zImage, initrd.img and the boot configuration. Then I unpack initrd using gunzip and cpio -id, then modify something, run "find . | cpio --create --format='newc'", then gzip it and assemble the filed to have a new boot.img.

Anything wrong in this procedure? How do you modify existing images? Just by using unpackbootimg?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
You need to add "-R 0.0" to your cpio. Starting in M, Android requires rootfs files to be owned by root.root. Here is the command that I used to repack the tulip boot images:

(cd initrd; find . | cpio -H newc -R 0.0 -o | gzip > ../newboot.img-ramdisk.gz); mkbootimg --kernel boot.img-zImage --ramdisk newboot.img-ramdisk.gz --cmdline "$(cat boot.img-cmdline)" --base 0x80000000 --ramdisk_offset 0x01000000 --dt boot.img-dt -o newboot.img
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Just curious but if we have the boot images, no verity boot images, and other EU users are reporting success, why are you poking around in boot images and fstab and what not? I'm just curious lol
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] TheSSJ:
Thanks, I will try it out as soon as I can :)

EDIT: I finally seem to have done it, the only mistake I did was that I didn't include the -R 0.0 parameter, but I had to use the abootimg package as every mkbootimg I used produced an unbootable image...thanks for the help [MENTION=4126377]tdm[/MENTION] ! :good:

No problem :) I want to understand how to unpack/pack boot images myself for when I replace the stock kernel with my custom one, but also to get up to speed with current android image layouts, things change so rapidly...
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Gotcha. I'm not brave enough to start cracking open package files haha
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Aries2010:
Alright so I've read just about all the threads can't find anything on rooting, so can someone make a step by step on how to root the ZTE Axon 7 mini or post a link. I have the US version with B14. Please and thank you in advanced.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] TheSSJ:
I can only tell how i did it for my EU model:

Flash twrp (and make sure system will be mounted read only), download magisk (which also has a su binary included and flash it. It should automatically choose systemless...unfortunately systemless and forced system installation of supersu led to be stuck at boot for me

By the way, before flasing rooting binaries, i removed the verity checks from my boot partition. Also i modified tdm's twrp to be able to backup system as an image instead of backing up the files...i am too paranoid given the eu models being unable to enter edl via volume butoon press

That's it
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Once you flash twrp you have two options for root. Flash the SuperSU 2.79 package for root or flash one of the two custom ROMs. They both have root built in.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Lineage does not have root (su) built in. You need to download and flash their su package if you want it.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Whoops I thought it did haha. Well AOKP has it built in. Lol
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Aries2010:
Alright so I was attempting to root my device tonight I got as far as downloading tuliptool and I tried opening it and it opens but quickly closes. I have windows 10 64bit. At this point I'm not sure what to do.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
It's a console app. Open a cmd prompt and run it.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Aries2010:
I'm not exactly sure what you mean by that. But what I did was open command prompt as the admin then tried opening the tuliptool and nothing happens I even tried dragging and dropping it over and nothing. I've tried on two different PC's one running Windows 8 and the other 10. I have some experience with rooting but nothing like this I've mainly delt with programs like Odin.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
Console apps will not open if you try to run them directly. You have to use a command prompt in order to make use of them. So, you can either 'cd' to that folder in a cmd prompt to direct it to the location of tuliptool, or copy and place cmd.exe in that location so it'll be directed there automatically. Using that command prompt, you can use the command lines in the OP; 'tuliptool <command here>'. If you've ever used something like ADB, it's really similar.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Well, I was getting ready to post a stock boot/system zip so that folks could get back to 100% pure stock, but it seems I mounted the system image read/write on my PC so it's no good anymore.

Does anyone else have a pure stock system and can upload it for me? I'd hate to have to go back to stock just for this...

Edit: went ahead and did this myself. Should have stock zips for US model soon.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Aries2010:
Ok i ran the verity img then after that i installed twrp then backed my data with twrp after that got finshed, I installed supersu after that the phone rebooted. Now the phone keeps cutting off and on with the ZTE logo powered by android. its been doing it for 15minutes is that normal?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
What version of su did you install? Try flashing your boot image back. The only version I think works with our devices is 2.79
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Aries2010:
I installed Supersu 2.82 only i would make a simple mistake like that lol. I restored my backup and its still doing the same thing
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Hmm I've ran into that exact issue and I reflashed my boot.img and it was fine after that. Perhaps try flashing one of the no verity boot files and see what that does.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Aries2010:
Your were right sir that fixed the problem after restoring my system back up thanks! alright so after i install noverity.img i can enable my twrp to write? then i can install a working supersu?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
That is correct! Install superSU 2.79. It will bootloop once or twice then it should boot correctly.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Aries2010:
Thank you a lot! all of you have been a big help i really do appreciate it
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Okay, flashable stock packages are up for the US model. I was able to download both the full stock 1.2.0b12 and also capture the 1.2.0b14 OTA file, so I was able to determine exactly which firmware partitions are updated. I've also saved those two files just in case anyone ever has a need for them.

If you want firmware packages for a non-US model, I'll need someone to donate either the full stock zip file or a copy of their stock partitions. PM me for details if you are interested in providing these.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] ZTEMINI:
The latest spanish upgrade zip file is here:

http://zte.es/soporte/libre/Axon7mini/rom/ROM_AXON 7 MINI NOUGAT_SDCARD_SOFTWARE_V1.2.0B12.zip

It has September 1 security patch, so I think it's very close to b14 in USA:

https://xdaforums.com/showpost.php?p=74286484&postcount=2
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
I took a look at the upgrade zip. It does not seem to have anything that makes it specific to Spain except the PDF instruction file. So I assume this is the general EU firmware. It does indeed match the US 1.2.0 b14 quite closely.

I've added the files to the stock firmware thread. Thanks!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] h0m3us3r:
Need help (softbrick)!

What I did:

tuliptool backup boot and recovery

tuliptool unlock bootloader

tuliptool flash TWRP

booting in recovery got stock recovery (O_o) booting system nets bootloop.

tuliptool flash TWRP once again (no errors, as first time)

stock recovery again...

flash "official" zte bootloader unlock zip using stock recovery

reboot into fastboot

unlock bootloader through fastboot (even though I unlocked it using tuliptool, it still remained locked as shown in fastboot), only after this one I started to get "bootloader unlocked" message on every boot.

flash TWRP through fastboot

reboot recovery

get into bootloop (-_-)

Now no mater what I do, I get bootloop. EDL key combo gets me into fastboot. Fastboot flashing stock boot and recovery (tuliptool backups) changes nothing. Flashing recovery from stock firmware (from XDA) changes nothing. Relocking bootloader changes nothing.

How do I get to EDL mode now? Booting recovery - bootloop. EDL combo - fastboot.

UPDATE: tried "fastboot flash aboot emmc_appsboot.mbn".. now i get zte spash screen bootloop... Even bootloader is gone now... Guess ill have to look for edl test point now..

UPDATE: here is the EDL test-point:

[IMG="ZTE Axon 7 Mini EDL Test-Point"]https://lh3.googleusercontent.com/ueUSX5WHfBgUoRHJTVuOSig9eLKgXj60qXapHQTBNkx0w3ovbZ_wwAv6WLreAZwk0nB8QGjbd9TK2rqCkLRu8nSmHtvrA37HIP7NjQlZ7PWIs6I0kfsw-Y9DRgY5Dee7YS9XSIIEYswrVxG15sMmwT0DFWis95un-zgymcXwicLLACRTZ1g36YkO_l9nJp3aA8T3PiP9nITXgg5aHZrdm-FmIvHAQAoZPdhf4NFvcFI8_pUozvnfbXdaz1upHZI3of3J9nhrQYLwOiX67osYV04zEoZxXx7m7bnbJbRGzkCIDjiA5aAtvOj4WYoR35FuEHCep65WUxplyA4M8ydOGn_jPo_Pad9rAGkyNDcJ6H2SAIlQYIxvt3-rGEKf-Rp_aTY8TwUYraLdXTsHqpOhksZSI7OvHMItqYpCyvBdvOBP7e-oTCs8BCBukwyE3h1dGJNTs6K9Bx8Eb0-13Iwahc-D124iUITkTeQNxDmLyjKcwwgJ52kQadMdbStbr6AU8-O9PyOrmfLU92p9ABa8uuuJvO26-m62ccs6rhheNHLG2EBNfJ6y_qZM9YrHHCHa_SfmEBKrggCrTCct7CsNsYpVLiKMODIzhlKx7L7J4dFcIAxlHLyYQUuyyOxGwMkECu2LM3z-x8V-ASFWuObWm9m3wDA5EedMVdg=w1110-h899-no[/IMG]
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Sounds like you are familiar with this stuff? Or at least not afraid to dive in.

First thing to know is that the splash screen is drawn by aboot. So if you see that, SBL has accepted aboot and handed off control.

You didn't mention which model you had. But I've disassembled the US stock aboot and it checks for the volume keys right off. So this seems rather strange.

Also, note that I've never done the official unlock. I just flashed the unlock aboot, noted that I could boot custom stuff while locked, and left it at that.

I don't really know how else to help. You can, of course, feel free to open up any of the stock zips that I've created and flash the aboot/boot/recovery if that might help.

Finally, in my experience, all qcom boards do have EDL pads. But disassembling this device looks.... tricky.