yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Try "list all devices" or similar.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] mentao:
Thanks for the quick response!

OK, I've got libusb-1_0-0-1.0.20-5.5, so I'll assume that's fine.

By "if it loads" you mean if it says something like

Sending programmer...

Yes, it does that.

The phone is plugged directly into the laptop and I've tried all three USB ports it's got. Currently, I don't have access to a PC with another OS but I'll try that as soon as I do (may be a while though). Tips on what linux distros work with tuliptool? (OpenSUSE doesn't have a plugdev group out of the box but I created it and added my user. Dunno if that affects anything else.)

Is there anything else I could try to debug the issue?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Ah so it's probably permissions. Try finding the proper user or just run as root.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] mentao:
No luck. Same problem when running as root.

# ./tuliptool-linux lock status
Sending programmer...Failed to send programmer: Connection timed out

I'll try and see later today if booting some Ubuntu live on the laptop improves matters.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] maestromony:
I have absolutely same problem (wrote about it few pages ago)... Still didn't found solution.

Tried also another linux and windows machines with no luck. I guess that is phone or cable issue.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] mentao:
I tried today with Ubuntu 16.04 and got different results :)

I installed ubuntu-16.04.2-desktop-amd64 from usb stick onto a usb stick (just a temporary installation).

During Ubuntu install, in order to not erase my normal laptop system, I had to select "Something else" and partition the second usb stick so that Ubuntu could be installed there.

Then I just installed adb and fastboot from universe

apt-get install android-tools-adb android-tools-fastboot

and installed the udev rule from the OP

cp 99-qcom.rules /etc/udev/rules.d
udevadm control --reload-rules && udevadm trigger

Then I could run tuliptool as root and got a (non-error) response :)

adb devices
adb reboot edl
./tuliptool-linux lock status

I then tried to unlock

./tuliptool-linux lock unlock
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
log: Finished sector address 0
*** WARNING ***
This is a dangerous operation. It may permanently and irreversibly
render your device non-functional. Proceed at your own risk.

In order to continue, you must agree to accept responsibility for any
possible damage to your device.

This procedure WILL ERASE ALL USER DATA.

If you agree, type "I AGREE"
I AGREE
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
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
Failed: Connection timed out

The unlock did something (erase the user data, as announced) but I'm a little worried about the "Connection timed out" messages (again).

Are those the kind of error messages that can be ignored?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] maestromony:
mentao, thanks!

Interesting why it doesn't work in gentoo and arch, but anyway in ubuntu 16.04 it works.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] mentao:
So it works for you, too, on Ubuntu? :)

Did you succeed in flashing TWRP on your device?

Regarding why it doesn't work: I've logged straces for tuliptool lock status on both ubuntu and suse (but currently I'm none the wiser). If anyone is interested let me know, I could send the logs.

Regarding the

Failed: Connection timed out

when I unlocked - is that harmless?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] maestromony:
Yes, flashed.

BTW, you don't need to unlock bootloader. It is factory unlocked (just switch it in the settings).
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Diomorgan:
no matter whan I do, wich usb port I use, I try 3 Pc and even the first one with one which one I was (uckyly randomly, probably due to qualcomm drivers from a lenovo tablet) I alway got th "device not found".I Didn't need Zad the time I flashed the TWRP, by the way Zad never see my phone, NEVER. I even installed the drivers from PC and the Qualcomm one in a clean PC, but nothing solved...I'm not into linux, I followed the instrutction in the op, I try 2 cables too...I'm stuck I cant let tulip see my phone to flash patched boot.ini from magisk.The sto recovery has an adb voice, do you think I can use that option? Will google, but if someone found that there is just a little stupid error that an human can do following the instruction (USB debug on/og oemon/off....dunno) please let us know :(

Thank you a lot, will keep trying and let you know.

UPDATE: FINALLY i just casually discover that I have to connect the phone to pc in "driver install mode" and reboot in edl via adb! Then tuliptool worked (as said before all the drivers where already installed, so I was really wondering why the device wasn't found) Just rember that connect with two volume pressed and get stuck on ZTE splash screen doesn't mean you are in EDL, only the total BLACK screen is EDL, I didn't remember that so everythime i plug the off phone keeping the volumes pushed for 3 second andI got the ZTE splash, but the phonedidn't boot, that made me think I was in EDL :(

My fault.

Thank you all!

P.S.:anyhow if I write the boot.img patched with magisk the phone ask for password then, due to encription, it ask to format... :(
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] julesism:
I just picked up two of these (B2017G) at a decent price for my parents :)

I'm in the same boat as Shockling on page 10. I kept reading and saw where SurrealScene was in the same boat on pg 18.

I tell the tool to write twrp recovery, but when i boot device into recovery via adb or vol-up+power, i get stock recovery. Looks like I just need to follow tdm's 6 steps but I kept reading...

After more reading, it looks like I should update to 7.x.x. Both devices came with 6.0.1 B14 (B2017G_USAV1.0.0B14_MR2).

Should I let them update OTA to a certain point or can I push a specific boot.img using the tool? OTA says it will pull B2017G_USAV1.0.0B21 next which looks like it's still 6.x

Looks like I just need to use tuliptool and write one of the US imgs from the topic below to boot, then I can write twrp to recovery?:

https://xdaforums.com/axon-7-mini/development/stock-boot-images-verity-removed-t3685697

Thanks in advance.

I was able to unlock BL using the tool but it looks like that is a wash.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Diomorgan:
Sorry if I'm dumb, but you mean tulip write twrp with no problem, but you still get the old recovery? ?Which cou try version do you have? (and how much is "decent price, hehehe, just because I finally cloned my main g5 phone on a7m and wold like to buy another one for my mother?)
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] julesism:
hello. yep, the log said success but no twrp. I paid $99 for each phone.

*EDIT*

I updated both phones OTA to 7.1.1 B14 and was able to flash TWRP using this tool. I've got LoS 14 running on both devices :)
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Diomorgan:
Ok, that's so weird that only [MENTION=4126377]tdm[/MENTION] can help you ^_^'

Wich version is your phone (locked bootloader to brandization?).$99 from usa or a chinese international store? sorry for the little OT, but for $99 it's a very nice phone (even I never tested really the battery!)
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] julesism:
eBay USA seller. I usually buy/sell on swappa but decided to take a chance.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] czarsuperstar@gmail.com:
For me the process was easy. I flashed this in recovery https://xdaforums.com/axon-7-mini/development/unlock-official-bootloader-unlock-t3690496 then after enabling developer setting (please don't forget to enable). Than in fastboot mode I fastboot OEM unlock than fastboot flash recovery recovery.img(after renaming the image to recovery) and I was successful in rooting and flashing a custom ROM. Thanks [MENTION=4126377]tdm[/MENTION]
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
hi, I have spent my last few days trying to root this phone with no luck.

flashing axon_mini_unlock.zip. via stock (android 6) recovery doesn't work. I removed the assert command and it fails on the file signature.

I have a B2016G, with android 6. I do not intend to upgrade right yet to 7, I just wanted root and twrp.

I have managed to apparently unlock the bootloader, and the status says unlocked.

I successfully install the recovery using

tuliptool-win64.exe write recovery tulip-twrp-7.1-r1.img

but after every reboot it goes back to stock.

I then install TWRP again, then disconnect the phone before it restart.

Then went I try to reboot into recovery, pressing vol+power, it shoes the log, but adb devices say I'm connect in recovery mode.

So I end up with no workable twrp, but my adb works fine, accepts any command (push, pull, adb reboot recovery, etc).

I apparently even have root access! adb shell goes ahead and gives me the symbols.....

No commands in fastboot work, I can reboot to it but the commands fail.

Is there any chances I can simply push the recovery to the recovery partition? does anyone know the exact partition location where to push this recovery, the one on the tupip method page?

I can't get my head around the reason why my axon 7 mini seems to be unrootable? I bought it unlock from any carriers, and the OS is pretty clean.

Thanks in advance
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
All of your problems are due to you running android 6.0. You need to be running android 7.1 to use these tools.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
i cannot update. axon 7 mini, as it came on my phone is

ZTE B2017G UK V1.0.0B01_MR

just downloaded the

P852A12V1.2.0B12_RM_data.zip from the zteUSA but installation aborts at about 25 %.

My hope is to push twrp via adb......then push the boot.img too

any ideas?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Sorry I don't have any experience with the UK model.

Perhaps someone else here can help? Or perhaps ZTE support? There must be a way to upgrade to 7.1, many others are running it.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
thanks anyway.

I'll keep thinking and if I find a way I'll post it.

I cannot believe it can be more difficult than the older axon mini (not the 7 mini) was.

EDIT. updating to android 7 now, instructions from here

https://xdaforums.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933

it is working and I'm on step 3. after I get it booted into android 7, i'll try rooting it if your tool. thanks a lot.

EDIT2: yes all good. android 7.1.1, rooted but no xposed yet.

Just a very loooong process, having to install 3 long whole systems each time (2Gb each file), then tulip tool works fine.

I must note I had bootloops until i flashed supersu2.78, then it booted. 2.65 and 2.82 didn't work.

having to find this out also took me a while....

well....at least is done so thank you so much for sharing your tool!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] czarsuperstar@gmail.com:
I use magisk. SuperSU was fine but due to a lot of mods using magisk. I think its the best root solution but that is just my opinion.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
just realised I lost my imei. can magisk fix it?

anyone could have a way to recover them?

thank
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] czarsuperstar@gmail.com:
What did you do? I have the USA version and I just followed the directions until I fastboot OEM unlock than issued the commands to flash the recovery on to the device.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
I have the UK version, and I had to follow the 3 step installation found specifically for the UK version owners.

flash the Spanish version, then another android m, then finally the android 7. all via stock recovery, hence I could not backup anything.

then I installed twrp tulip. all good and I played with the phone for a while with no SIM, thinking it was fine. then I lost the IMEI.

trying to fix it, I bricked it by re-flash the step 1 (Spanish).

finally recovery the phone by ADB commands to push the aboot files back and flashing them using the DD commands. all good.

after a lot of thinking before messing up again, and using my experience with the old axon mini, not the 7 mini, I flashed the aboot 6 planning to reboot to twrp before going back to the stock Spanish, which I prepared and removed the recovery-resorce to avoid loosing twrp.

reboot recovery.......and...... finally.......totally, absolutely KILLED the phone.

I have ordered the edl cable now, but to be honest I paid £99 pound on this phone and I'm ready to smash it with a hammer and throu it in the bin.......

even after, or if, I manage to revive with this funny cable (no clue yet how to do it) I know I won't have the IMEI yet.

basically I have spend way more time researching it, that i would earn enough to buy at least 10 phones like this, or 1 iPhone! (for comparison as I hate aple crap anyway)

I'm not desperate. I still use my older axon mini, it works fine still.

thanks
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] czarsuperstar@gmail.com:
https://xdaforums.com/showpost.php?p=71348392&postcount=5

Try this.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
thanks for trying to help.

the link is broken........but the phone is dead anyway and I'm starting to strongly believe I won't be able to revive it because I have already tried to make a deepflash cable but it didn't work. I'll wait until the proper cable arrives, and if it still doesn't work I'll sell the phone for spares (screen battery etc) if someone is interested. it is absolutely brand new, used for les than 24 hours!

Thanks

EDIT

_______________

Ok, I have 2 axon 7 mini, the first one is permanently dead. I dug into what I've done and I, very stupidly, copied and pasted dd command too many times trying to get out of the brick, that I ended up pushing the emmc into the boot partition...…..this literally killed it. no deepflash cable, no buttons response with any combination...….dead.

the only sign of life is a tiny dash at the lower right corner of the screen when charging/usb, and if I hold all 3 buttons at the same time it stops. deepflash cable doesn't work at all in 2 different pcs, and on a 3rd pc windows sound after the connection but recognizes a corrupt driver. lets forget about this one and leave for spare parts when/if I brake the screen of my second phone.

Now we are on the second phone.

I have done exactly the same, very carefully now, also bricked it but I'm now an "expert" in debricking it from any situation, except the case above (flashing wrong partitions).

I'm up and running, installed Spanish android 6, then the next android 6, then finally the tulip rom......I'm now on lineage....etc....the phone is fine.

But again I lost the email.

However this time I did managed to re-write it with the above tool. the imei is there, but still no signal.

I only tried the lineage ROM (which by the way is MUCH better than the stock) initially because I read another post (can't find the link) the typing the code *#*#4636#*#* takes me to the radio menu where I can change the radio band to "automatic" (something the tulip ROM doesn't offer), and this fixed someone's phone.

However, this guy had an US phone trying to operate in Iraqi.

My case is different, I have a UK phone and the trick didn't work at all. I'm pretty sure my phone is supposed to have a single SIM.

but when I go to about....imei info I get:

IMEI (slot1) = xxxx my correct imei xxx

IMEI SV (slot 1) = 02

MIN (Slot2) = unknown

PRL version (slot2) = 1

MEID (slot2) = 00000000000000

Is there a KIND SOUL who could help solving this puzzle? I cannot understand how/why the US ROM or hardware wouldn't work in the UK?

I cannot believe an American person that comes to visit the UK wouldn't be able to just use their phone as usual?

Is my imei re-flashing somehow a bit faulty or incomplete?

Any ideas like flashing any particular modem or partition?

I'd really appreciate any kind of help as I have spent 100 hours on this phone I'm starting to hate it now.

Thanks in advance.

.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
--------duplicated post -------
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] daniu:
Hi,

I also have a Axon 7 mini and unfortunately it is pretty messed up. I had tried to flash TWRP which had seemed to work but the recovery does not work. I do not get any recovery anymore. Because of that it is not possible to turn off the device (or ... how does that work in this case? No recovery, no ROM). I somehow managed to get into EDL mode and flashed a TWRP recovery I found here: https://www.androidinfotech.com/2016/12/root-zte-axon-7-mini-marshmallow-twrp.html - unfortunately tuliptool gives me an errormessage after trying:

tuliptool-win64.exe -write recovery recovery.img

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

Most of the time now however I do not even manage to get into EDL mode

I would appreciate any hints:

*how to turn off the device under these circumstances?

*is the TWRP source I used not goot? What would be good?

*any other ideas what I might do?

regards
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
well, as long as you didn't loose the IMEI like me I think it is fixable.

go to edl again. flash the tulip recovery again. it is the only recovery that will work. I think you should not have let your system reboot after flashing it.

once you flash it, it will try to restart alone, but keep you finger on the power plus vol+ once the counting is about 4 (12345_then it restarts).

options

a) recovery works then you are fine

b) recovery is just a black screen. in this case go to the pc, ADB devices....you will see it says recovery. ADB will work.

now push every single file from the bootstack (I think they are about 7 or 8) into data/media.......

then use DD for writing each once into its partion. VERY careful not to flash anything into the wrong partion. I flashed emmc into boot and killed the phone for ever.

once you've done that, your recovery (already flashed) will magically appear......

remember, write all these commands into a notepad and carefully paste one by one into CMD. a total of 14 or 16 lines.....push to the phone first, then DD each one of then.

if what I'm saying sounds like Japanese to you, I can write a step by step later when I'm on my pc.

cheers
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] daniu:
Thanks a lot ...

Well ... Imei - I don't know. I only received the patient to cure it - was not the one who started the messing ... so I am not sure if that happened or not - at least I do not have a backup of it ...

Well - it does not sound like Japanese rather like Chinese - which I studied a while but probably not long enough ... therefore I'd highly appreciate some more details. Maybe I am able to finalize the mentioned command writeup and show it here for review?

Just one more thing: when I started the partitions where messed up - that made me want to install twrp. Partitions are still messed up. Would that be fixed in your procedure?

Background: the owner had a very old unrooted phone that got pretty slow. I had mentioned rooting and removing unnecessary plunder. Unfortunately he tried to do exactly that with the new phone in the very beginning and ended up with a messed up phone with partition problems.

Just those questions so far:

*is there no working twrp for this phone or why can't I just flash that?

*where do I get all those files - recovery, stock rom, bootstack?

*why should I not boot after flashing the recovery? It sounds a bit like lottery (count 1, 2, 3) to make the phone not boot into system - or can I push buttons at 1 already or does the phone show something like 1, 2, etc? If I understand correctly I can and should boot into recovery?

Regards
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] demenicis:
before anything,

- can you boot into edl (bootloader)?

- do you know what ADB is? if not please learn. adb and fastboot, phone drivet blabla

- bootstack is a bunch of partitions that can be extracted from any StockRom.zip. Basically a bunch of files. They include modem plus other (bootlogo etc,). you can find this .zip file posted in various rom versions (EU, US, UK) etc. you could make one yourself. I know for a fact that varying in between twrp and these versions I have lost my IMEI. This is important! and it means my phone until now is useless.

- tulip recovery works, a fact. but only with bootstack from 7.1.1 ROM, I suspect you have android 6 on yours.

- once twrp is flashed, the bootstack flashed and you manage to reboot straight into twrp, then it sticks (or new reboot would erase the recovery). try to reboot straight into twrp after the command of flashing twrp ends.

- I would not follow this https://xdaforums.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933 . lost of IMEI issue I had on 2 identical phones. SuperSU installation also one time made me lose both baseband and IMEI. (I killed my first phone trying to fix the IMEI problem in first place.)

- The safest way, just my own view, is to find the exact same stock rom you had before, and prepare it (remove recovery, alter script etc) then flash system from twrp without worrying to lose twrp every time. at the moment I'm struggling to find the android 6 UK stock rom so I can't say if the cell phone connection it would be re-establish yet.

all you have to do now is to boot into edl, flash recovery and reboot into a working twrp. YES?... end. NO? your recovery boots but on a black screen? then you can push the bootstack files to the phone via adb, write these files to each partition, then reboot into recovery. twrp will boot and you can flash a rom. any. the problem is that the new OS deletes twrp at boot.

To avoid that I flashed a special .zip I prepared (with WinRAR) which is the stock android 6 rom.zip with the recovery and all the bootstack deleted (almost leaving the system only in the zip) and modifying the script to delete everything but system). and the phone works perfectly.....humhum.....without the imei.

I can post the commands a bit later when back home.

cheers