yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Meme Queen:
first! it's nice to see someone working on the lesser-known devices for once, thanks love!

okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Perhaps try running it as administrator? I'm heading home from work and then I'll be taking a shot at this myself.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
I just tried on a Windows 10 virtual machine and it works perfectly.

This is a commandline program so you open a command prompt and type eg:

tuliptool-win64.exe lock status
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Meme Queen:
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:

Sending programmer...Connecting to programmer...log: logbuf@0x08067EB8 fh@0x08064D20

log: logbuf@0x08067EB8 fh@0x08064D20

log: Finished sector address 0

log: Finished sector address 0

log: Finished sector address 0

Writing recovery ...

terminate called after throwing an instance of 'std::runtime_error'

what(): No error

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
I guess im stuck waiting for the update.zip because Zadig is refusing to install drivers. no matter what i do it will not install drivers. it keeps telling me "Remote Source Not Allocated: Driver install Aborted"
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Hmm, looks like something strange is going on there. I'll take a look tomorrow.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Meme Queen:
thanks! if there's any information you want me to provide, just let me know.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] pxzei:
I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] rombdeta:
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.

You may need to have admin privileges to talk to USB devices, I'm not sure.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Device Shows connected and drivers installed under device manager.

Command prompt is being run as so:

Start --> type cmd ---> Right click on Command prompt ---> Run as Administrator

cd C:\users\admin\desktop\tuliptool

C:\users\admin\desktop\tuliptool> tuliptool-win64.exe lock status

Device Not Detected

---------- Post added at 03:59 AM ---------- Previous post was at 03:38 AM ----------

UPDATE:

I found that I had to use a USB 3.0 hub in order to get the phone to be detected.

Once detected I ran commands as followed.

tuliptool-win64.exe lock unlock

(The unlocking procedure said it failed, phone bootlooped three times, then it showed as unlocked when I ran the Lock status command)

tuliptool-win64.exe read boot

(This created the backup-boot.bin file in the directory)

Tuliptool-win64.exe read recovery

(This created a backup-recovery file in the directory)

tuliptool-win64.exe write boot

Its at this point here I get a Runtime Error as well. The entire process comes to a halt.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] pxzei:
Thsnks, tried that, but no luck. It's still stuck on the splash screen.

Update: The device is running B09 7.1.1, The charger seems to be ZTE authentic. Single sim variant. If you need more info, let me know.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] fallen00sniper:
Awesome you got the tool out, I think I am going to wait for the 'Official' tool so if I ever need to send it in for repair in the next 2 years I can say 'well I used your tool' lol

Can't wait to see the roms [MENTION=4126377]tdm[/MENTION], keep it up and I think the mini is going to get a lot more interesting.

I'd like to get a bloat removed(if any) and more lightweight faster rom on mine, maybe try the latest cyanogenmod or w/e they call it now and AOKP, etc.

New roms without MiFavor would be awesome too and ones that improve performance! :)
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] CRAFTER0302002:
ZTE

[MENTION=4126377]tdm[/MENTION], do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.:)
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] saymonek:
First post:

"This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device."
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.

[MENTION=8597130]Meme Queen[/MENTION] and [MENTION=7636441]MrWhite0429[/MENTION] please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.

I can modify the tool to take a filename as a parameter if that helps with the confusion.

Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
as in rename to recovery.bin?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Yes, that.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Some version of ZTE stock software will over-write recovery. some will not.

You only need noverity boot image if you are going to modify /system. This includes any manipulation of the /system partition. For example, mounting /system read-write in TWRP even one time will destroy verity integrity. Doing a backup and restore of /system in TWRP will also destroy verity integrity.

I have only posted the Spanish noverity boot image (I named it EU, because I thought there was only one EU version... but I was wrong). If you put your boot image on gdrive and send me a link, I can make a noverity version for you.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Newtomini7:
Hello. I hate to bother. Is there a youtube directions for this root. I have tried to fallow along. But I'm confused. I've a few phones before. Unfortunately I for me I'm at a loss on this mini 7. It's might be information over load. Since there is so information to read and I'm better as a visual learner. Thank you. Sorry I can't add to this amazing project. It clearly is massive so few. However the results all beyond what most would of expected. Thank you again.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Alvin4500:
Is there a way to go back to stock
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] ygb7:
What type of Axon 7 Mini do you own. Is it the North American model?

I am not aware of anyone creating a YouTube video for using Tuliptool. However, the instructions on the opening page 1 are very complete. I followed those instructions and successfully unlocked, flashed TWRP & rooted my North American model Axon 7 Mini easily on the first try.

If you have rooted or flashed a custom recovery or custom ROM on any android phone before, then the steps on the opening page should be very simple to follow. On a scale of difficult of 1 (Easy) to 10 (Difficult), the Tuliptool procedures are very easy. I rank 2 or 3 (easy) in level of difficulty.

However, if you are uncomfortable or unsure of your abilities to follow the instructions. Or, not comfortable with the risk of bricking your phone & knowledgeable about how to recover a bricked phone. I would just not do it.

If you do decide to proceed, read the instructions carefully, download all of the required tools first. Practice the procedure in mind first to make sure you understand each step thoroughly. Post your questions to this forum. Someone will help you out.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Newtomini7:
I have USA model. I'll give the root a try from page one directions as suggested. If anything bi really want my hotspot back. I like this phone. But the hotspot being dead kills alot of my production time. Thanks
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] ygb7:
Good Luck & Best Wishes,

We both have the same USA model of the Axon 7 Mini. You can read my steps in Post#145 on page 15.

Please post back to the forum to let us know if you were successful.

YGB7
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] lchichiarelli:
Restore from scratch

Hi,

I kinda of briked my Mini 7 in the process of rooting it.

Everything went smooth (TWRP etc) until I've installed SuperSu 2.82.

Now I've installed the stock bootimage, and the only option that I have is to boot in standard recovery and use ADB sideload.

I've tried to install the Axon Mini Unlock from

hxxp://code.nwwn.com/files/android/axon7mini/axon_mini_unlock.zip

but I receive the error as you can see in the image:

hxxps://imgur.com/9WpX6Aa

ZTE/P852A11/tulip

7.1.1/NMF26V/20170828.120949

sorry for the fake links, but as a new user I cannot post links right now.

Please can someone help me sending me a working boot image to use with my device with adb sideload command?

thanks a lot
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Xsillion:
Is there any chance this would work for the international gold version? I'm kind of peeved because Axon support didn't let me know that the US version and Int version don't run the same firmware. Apparently the int version will not be getting a software update and I'm stuck on security patch Jan 1, 2017 and android 6.0.1. Welp...140 bucks down the drain. Well, do you guys think I should try it? Maybe change the ro.product.name in prop.editor to match the SD card package on ZTE's support site?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Many international users have reported success.

I don't know why you would be stuck on 6.0.1. ZTE has published 7.1.1 for many different international models. If you do not get the OTA notification, you can download the package from their support site.

NOTE ... always flash official vendor packages with stock recovery, not TWRP.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Xsillion:
Hi, thanks for the reply. I've been contact with ZTE support for a couple days, they tell me there is no update for my model. The gold version is apparently different from the silver version. I tried to update with the SD package from the site and it does not work. My phones ro.product.name is different from the one specified in the SD package.

My is P852A11

The SD package is P852A12

The official word from development team was that I will not be getting a software update. Meh, might as well try tulip, cant hurt at this point. Gonna have to get another phone anyway.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
P852A11 is the international model. P852A12 is the US model.

You can try downloading and installing any of the international OTA packages. For example, the one on my server is for P852A11 and it should work.

http://code.nwwn.com/files/android/axon7mini/B2017G-EU-v1.2.0-b12-ota-full.zip
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Xsillion:
Ok, thanks. I'll give it a shot. I'll let you know how it goes.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Xsillion:
The SD package you provided updated successfully. I suppose the next step is to use this tool to unlock and apply a custom rom. Thanks for your help.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] k500zm:
[MENTION=7283211]Xsillion[/MENTION] - So are you now updated to Nougat 7.1 using the sd card method ?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Xsillion:
Hi. Well...yes. But here's the thing. I bought the Gold Version of the Axon Mini 7 (which is apparently the international version), and it is incompatible with the SD card package provided via ZTE support website. The gentleman above provided me with the EU SD card package that held the same "ro.product.name" as my device. I honestly don't understand why the ZTE engineers claimed my device was not update-able in my corresponded with them. It's been a pain, but it seems that my INT version is able to run the EU version of the software, at least from my understanding.

So, yes.

After successful (unofficial) SD upgrade, my phone details are:

Model: ZTE B2017G

Android Version: 7.1.1

Security Patch: Sept 1, 2017

Build Number: ZTE B2017GV1.2.0B12

---------- Post added at 09:34 PM ---------- Previous post was at 09:30 PM ----------

I honestly want to flash a custom ROM now, but I have a feeling I'm going to create more trouble for myself. Best be thankful that I was able to update a woefully out of date device, with some help.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] k500zm:
[MENTION=7283211]Xsillion[/MENTION] Thanks for the detailed response - did you get yours from Gearbest ? I am waiting for mine from them - it should arrive soon - gold like yours. I have spent the time waiting for it studying this sub forum meticulously in wait so I wont have any problems

It seems the golden rules are

1 - Backup partitions individualy to start with

2 - never flash both boot and recovery at the same time. If you always ensure that you can

boot into TWRP before flashing boot, and you can boot into Android before flashing recovery you will be in a

recoverable state.

I just bought an Axon 7 proper for £180 so I will have to wait a few weeks for that to arrive also.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Xsillion:
Yeah, Gearbest as well. I got it via promo for 119. The price was far too good to pass up. I honestly just want to root my device. Is a custom recovery necessary for flashing supersu or magisk?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] k500zm:
Seeing as I haven't received my phone I think it would be better if the expert answer that ;)
[MENTION=4126377]tdm[/MENTION] ?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Yes a custom recovery is required to flash 3rd party Zips. You can unlock, flash TWRP and flash either

SuperSU 2.79

Or

Magisk 14.0

To obtain root. For some reason any version higher or lower than 2.79 with SuperSU will cause the phone to bootloop. You can flash either of these packages with TWRP and still remain on the stock rom. So here are the steps I'd take.

Unlock Device

Make backup of stock boot and recovery using tulip tool

Flash Noverity boot file

Flash Twrp

Flash the root method of your choice.

At this point you can either remain stock or flash a custom rom. Please note that once a form of root is flashed such as SuperSU, the device may bootloop a few times then continue as normal. Be sure to make a copy of boot and recovery. So you can return to stock status if something fails.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] k500zm:
Nice Advice Thanks [MENTION=7636441]MrWhite0429[/MENTION] - quick question - once you are on custom rom how much SOT do you get per full charge - and with little use how many days or hours! will the phone last on standby approx?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
This was taken on the resurrection rom.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] k500zm:
[MENTION=7636441]MrWhite0429[/MENTION] - Thanks, very enlightening.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] stevegtrlmk:
Hi did you put in root of your SD card and just flash also on gold version 6.01
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] ocalderon:
Having error of "Failed to send programmer"

I've tried to use this tool. I used Zadig to install WinUSB drivers and everything goes fine.

But then, when i run the command to install something i get this:

>tuliptool-win64.exe write recovery jasmine-twrp-7.1-r3.img

Sending programmer...Failed to send programmer: Unknown error

Does somebody know what could be happening?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] lchichiarelli:
I've exposed the mainboard of my device and now if I circuit the pin as image (as suggested by [MENTION=7998530]nten2[/MENTION] and [MENTION=4126377]tdm[/MENTION] ) my computer recognize the device as "Android" in the device manager and ZADIG lists the device as usb id 05c6 f006

If I execute fastboot device, adb device or tuliptool status it says no device....

https://ibb.co/cuLOWb

Any ideas?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] jc44627:
I would like to root my phone while remaining stock. I have enabled OEM unlocking in the developer options as well as used tulip to unlock the device. I also have the non verity boot installed. This was after I returned from stock after TWRP, AOKP/Lineage. I tried to install the SuperSU zip from the stock android recovery with no luck. I have also tried installing TWRP, then installing the stock firmware. That was resulted in boot loops. I am currently back on stock with verity removed.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] marvelljones:
I never got SuperSU to work with "stock", but I honestly didn't try that hard. The Axon 7 Mini is my backup phone, not my daily driver. I got Magisk to work via TWRP on the first try. You might want to try that route unless you absolutely need SuperSU for some reason.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] anti-user:
Hi,

i need your help!

My Device:Android 7.1.1

B2017GV1.2.0B13

PC: Windows10 pro

I can't get adb access,i installed adb&fastboot 1.3,1.3.1 and 1.4.3 but nothing works.OEM-Unlock&Debugging i activated.

Do i need special-Drivers?

How do i get in EDL-Mode,with the "key-combo" it only shows the blue ZTE-Logo and nothing happens??

I rooted all my HTC's without Problems(actually my U11)but this Phone get's me crazy.

What's the Problem? I,the Phone or my PC?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
The EDL key combo only works on US devices. You need to run adb reboot edl.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] jc44627:
I do not need to go with SuperSU, thank you for the heads up about other alternatives.

Did you install TWRP first onto the stock bootloader and then Magisk? Afterwards, did you flash back stock?

---------- Post added at 10:21 PM ---------- Previous post was at 09:59 PM ----------

Just to document steps that I am taking...

Downloaded Magisk.apk onto my device.

Installed Magisk, then ran it and patched my b14-boot-noverity.img. File got stored to /storage/emulated/0/MagiskManager/patched_boot.img.

Tried installing the patched_boot.img via tuliptool. Unsuccessful.

Fortunately did not brick phone. Held power down for 10 seconds to hard shut down, then restarted phone. Phone appears to be ok.

Going to try creating images without "Preserve force encryption" checked
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] anti-user:
[MENTION=4126377]tdm[/MENTION]

That's right,but that's the Problem i wrote,i didn't get adb-access!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Enable developer settings. Go to advanced -> developer options. Enable adb. When you plug into the PC, the screen will ask which mode you want. Select mtp. Then you should see the adb host key dialog. Accept it.

That should be everything you need to get adb working from the phone side. I don't use Windows so someone else will need to help with the PC side.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] anti-user:
I changed to English-Language to set it right but there is no adb-option only "Select USB Configuration",i set it to mtp.

I hope that's right and i will test it.

Edit:

After reading the hole Thread i found the right comands to get all working!

I only have a Problem to install a Custom-Rom,Error7 "Can't install this package on top of incompatible data.Please try another package or run factory reset"

Factory Reset ends in the same result!

Edit: Problem solved,i forget the full wipe before installation!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
It seems like your going about installing a long way. Just download the magisk install zip file and flash in TWRP. You shouldn't have to flash boot img or any of that mess. Tulip tool is designed to unlock and flash TWRP that's it. It's not meant to be used as a main source of flashing.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] jc44627:
In the past when I tried to flash TWRP using tuliptool, it resulted in boot loops. However, I tried again and to my surprise was successful. I wonder if that is because I had a no-verity boot image. I was finally able to install Magisk via the zip.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] juanantofb:
Hi, sorry for my English, only speak Spanish.

In 3 days, i receive my Axon 7 Mini.

I only want flash TWRP and Magisk.

What is the best metod?

Is this the correct TWRP: tulip-twrp-7.1-r1.img

If my phone have a rom uper B9, i can use tulip-eu-7.1.1-b09-boot-noverity.img?

Thanks.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Theared:
It's something wrong with this tool or with my device. I check "lock status" and I see that I have unlock ("Device unlocked: yes"). So I try flash twrp. First backup ("tuliptool read recovery recovery.img") and i have one hunder "log: Finished sector address 0" and in the end "Success!", but in folder I dont see new file. Maybe I havent unlock bootloader? I want to check, so in recovery I choose "reboot to bootloader" and my device boot into system. So i try "lock unlock" and there:

Unlocking device ...
log: start 11404304, num 2048
Write 1048576 bytes, 2048 sectors
log: Finished sector address 11406352
log: start 1312768, num 8
Write 4096 bytes, 8 sectors
Failed: Connection timed out

I have no idea what going on. Anyone have some proposition? Thanks.

My ZTE is global device, P852A11, B2017GV1.2.0B12, 7.1.1.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
I don't know why you do not see a new file when you read recovery. The tool should we working. Perhaps you are looking in the wrong directory? What operating system is your PC?

Note the device is not locked from the factory, as stated in the OP. The lock functions do not do anything useful.