yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Theared:
Thanks for answer.

I should look to tuliptool folder, right? There is no new file.

Linux Debian, but I try too on Windows 7 32-bit.

If I have an unlock device I should can use "reboot to bootloader", and then use fastboot, right? Unlucky, like I said, I can't because my phone reboot to system. There is an another way to user fastboot or flash twrp?

---------- Post added at 08:11 PM ---------- Previous post was at 08:04 PM ----------

Damn, I forgot then i still flash TWRP with tuliptool. :) I tried and success. Thanks for advice.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
It looks like your problem is solved. However, just for completeness...

I also use Debian Linux as my main OS. This is where I test and use the tool most.

tuliptool writes to your current directory, wherever that is. So, for example, if you put tuliptool into /usr/local/bin and run it from $HOME, your file will be written to $HOME. This is the same for all versions of the tool.

Unfortunately, ZTE has disabled fastboot (*). You must write TWRP with tuliptool. After you ensure that TWRP works, you can flash the noverity boot image with either tuliptool or from TWRP (using dd). Or you can flash a custom ROM.

(*) The ZTE unlock package updates aboot to support fastboot. But it is for US devices only, and it also disables the EDL key combo. I don't use it or recommend it.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Theared:
I thought so. I had tuliptool at ~/Desktop and there I was checking. Anyway, I have now TWRP, so does not matter. :)

Yep, I was reading in specification of kernel, but I was thinking that fastboot is disable until bootload is lock. In particular, when I had 6.0.1 on my ZTE I can reboot in bootloader (from recovery) and then i can use "fastboot devices" and my device was recognized. Anothers commands were disable. Or maybe this is what You tell next to (*) ? :) Anyway, thanks for explain.

I did it, thank You for advise. :)
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MoeKyawThu991:
Hello, I downloaded this tuliptool.zip, but this do not work in my windows 10 32 bits. Please help me .

---------- Post added at 04:47 AM ---------- Previous post was at 04:39 AM ----------

Hello, I downloaded this tuliptool.zip, but this do not work in my windows 10 32 bits computer. Please send me a new tuliptool.zip link. Please help me. Thank you!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cb_123:
Hi to all, I'm new on this forum.

I've some problem with my Axon 7 mini, I'we executed the commands in the first post of the thread, but at the command "tuliptool-win64 lock unlock" I've received one error end now the device reboot contiuosly (every 3 seconds).

This is the result of the command:

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: Unknown error

Reset in 5 seconds ...

Reset in 4 seconds ...

Reset in 3 seconds ...

Reset in 2 seconds ...

Reset in 1 seconds ...

Failed: Unknown error

Now I've found a guide to build a cable to enter in DFU mode and I can send another command via tuliptool, I try "tuliptool-win64.exe write recovery tulip-twrp-7.1-r1.img" but receive another error:

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 ...

log: start 1181696, num 600

Write 307200 bytes, 600 sectors

Failed: Unknown error

Reset in 5 seconds ...

Reset in 4 seconds ...

Reset in 3 seconds ...

Reset in 2 seconds ...

Reset in 1 seconds ...

Failed: Unknown error

I don'know what to do now, can anyone help me?

The deivce is European version B2017G.

Thank you in advance a sorry for my bad english.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] MrWhite0429:
Is oem unlock selected in developer options? What version of android are you trying to flash from?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cb_123:
OEM unlock is selected, Android version is 7.1.1 B13 or maybe B14, I don't remember.

I trying to unlock device to install Lineage OS, but now I just need to restore original ROM.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
There seems to be a problem writing to the device. Try a different USB cable. Try a different PC. If you are using a USB hub, try connecting directly to the PC USB port.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] zzrylarg:
So i have a device brought in aus. Its currently running 6.0.1 1.0.0B01

how would i check if this device is compatible with either the us or eu Software. Im worried about things not working like cell radio or wifi.

Also i hear you need to do an update to 7.1.1 before flashing twrp7.1.1 will this matter if i intend on flashing a custom rom right after.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
You can't really check except by trying.

Yes you really need to be on 7.1.1 before installing any custom software. The boot stack should match the kernel and the vendor blobs. If it does not, strange issues can happen. Or it can even fail to boot.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] zzrylarg:
thats really dissapointing. This is my only android atm, if it wasnt id give us or eu a go.

im being more and more let down by this phone by the day.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cb_123:
I've tryed now with another cable and PC but the result is the same.

I can check the status via tuliptool:

tuliptool-win64.exe lock status

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

Device unlocked: no

Device tampered: no

Reset in 5 seconds ...

Reset in 4 seconds ...

Reset in 3 seconds ...

Reset in 2 seconds ...

Reset in 1 seconds ...

but if I write the twrp, it fail:

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

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 ...

log: start 1181696, num 600

Write 307200 bytes, 600 sectors

Failed: Unknown error

Reset in 5 seconds ...

Reset in 4 seconds ...

Reset in 3 seconds ...

Reset in 2 seconds ...

Reset in 1 seconds ...

Failed: Unknown error

Can I try to write the original ROM via tooliptool? If I can, what is the command? I have the file update.zip from ZTE site.

Or can I use axon7tool?

https://xdaforums.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
That is definitely strange. I don't know of anyone else that has had this particular problem. Looking over your initial pasted output, it seems that the data wipe did succeed:

Unlocking device ...

log: start 11404304, num 2048

Write 1048576 bytes, 2048 sectors

log: Finished sector address 11406352

That means tuliptool is functioning properly. However, every attempt you made to write data to anywhere else has failed. The only thing I can think is that there may be a hardware level write lock on the device. But I've never seen that on any other axon7mini (the axon7 does have a write lock, but not the axon7mini).

Next question, I guess, is can you still boot into stock recovery by holding vol-up + power? If so, perhaps a full factory reset will get you functional.

In regards to your other questions... no, tuliptool cannot flash a full update zip, and axon7tool cannot work on the axon7mini.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cb_123:
Unfortunately holding vol-up + power don't have any effect.

When I switch on the phone, it show the logo ZTE for one or two seconds and then reboot, continuously.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
I'm interested to see what the problem could be. Feel free to PM me and I'm sure we can get it fixed.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] cb_123:
After many hours of test and searching online finally I found the solution, it was here all along, simply I've execute the write command with 32 bit tuliptool instead of 64 bit.

Thanks for your help.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] disChapo:
Just used this. Worked like a charm. Took a bit of troubleshooting and I had to end up using the 32 bit windows one. Backup my data now and going to install lineage.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Sithu Htun:
I see no TWRP interface, but white screen. But there's no problem. I can flash zips via adb.

Finally, succeeded! Thanks! Nice tutorial!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Are you on android 6.0 or 7.1? I think the white screen is caused by the 6.0 boot stack.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Sithu Htun:
Sure, it is 6.0.1, bro.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] dangergolf:
FYI.

New to all this. I have the Canadian version (verdandi ). I tried to get TWRP installed first from my Linux desktop and then from my Windows laptop. In both cases, I can't get to EDL by using the buttons so I had to use adb reboot edl. Once there I tried the tulip command (lock status, read recovery, read boot): on Linux I had a "Failed to send programmer: Communication time out" (not sure about the right terms anymore) and on Windows I had a "Failed to send programmer: Unknown error".

I thought I'd share my results. Thanks for your work, it was very interesting
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
The Canadian version has a different signing key, so it rejects the programmer. Sorry, I can't do anything about it.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] dadme:
It's possible to use this tool to unlock Axon 7 Mini B2017G Dual SIM TD-LTE european version. If yes, it's possible to relock bootloder again, to avoid losing the guarantee? After bootloader unlock, on boot is any message showing that bootloader was unlocked?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
The boot loader is NOT locked on any axon7mini versions.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] RebeccaSugar:
6.0.1 boot.img

Would anyone here have it? I overlooked the "7.1.1" message and used TWRP anyways, THEN used the 7.1.1 boot img which threw me into a bootloop, I can boot into EDL just fine, sideload doesn't work with me, so I see obtaining my original B2017G US boot.img and reflashing it with tulip as the best option to get back on track! Hope someone is able to help :laugh:
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] :
That's odd, considering that it has to remind me that my bootloader's unlocked every time I start up. Maybe it's just because I used the unlock zip instead of tuliptool...
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Yes it's because you flashed the unlock zip. That contains a more standard qcom aboot which supports fastboot and also has their standard warning screen. The stock aboot is modified to disable fastboot and the warning screen.

As I've said, there isn't really any reason to flash the unlock zip unless you really want to use fastboot.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] maestromony:
I have an issue.

Trying to use tuliptool, but everytime i get error message:

~/tuliptool $ ./tuliptool-linux read boot boot-1.2.0-b12-eu.img
Sending programmer...Failed to send programmer: Connection timed out

Also tried to use tuliptool with root privileges.

System info: Gentoo Linux (systemd) 64bit (Also tried Arch), 4.15.2 kernel, 99-qcom.rules created.

Dmesg output:

[ 1433.479294] usb 3-1: new high-speed USB device number 9 using xhci_hcd

[ 1433.606209] usb 3-1: New USB device found, idVendor=05c6, idProduct=9008

[ 1433.606216] usb 3-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0

[ 1433.606257] usb 3-1: Product: QHSUSB__BULK

[ 1433.607275] qcserial 3-1:1.0: Qualcomm USB modem converter detected

[ 1433.607924] usb 3-1: Qualcomm USB modem converter now attached to ttyUSB0

Tried different usb-ports (3.0, 2.0) with no luck.

It looks like:

but device directly connected.

Anyone know what's wrong?

Upd: Tried Win-32 version of tuliptool. Got same error message.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] vincent1967:
I have also an issue but on a Mac OS environment :(

I'd like to flash TWRP with the Mac version tool you provide but unfortunately it doesn't work, it always ends up in an "Operation timed out" message.

My Axon 7 mini is an European version ZTE B2017GV1.2.0B13 up to date.

First step is fine, i use the "adb reboot edl" command to get into the edl mode. But the next step goes wrong : if i key the command "tuliptool-darwin write recovery" in the Mac Mini terminal, i always get this answer :

Same result with any other command like "tuliptool-darwin lock status". I don't know what to do. Maybe i should try on a Windows system ? Do you have any idea ?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
I don't remember if I actually tested the darwin version. I can do that tomorrow. But please do try the windows version if you can.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] vincent1967:
I gave a quick try on a computer running windows 10 OS but it didn't work for other reason, despite my Axon is in EDL mode, device 05c6:9008 is not detected at all. But i had to give up :( no time to figure out why, cause this computer was not mine, it belongs to my parents. My own is a Mac Mini.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Diomorgan:
throught #110 post I wasn't able to check, but my Model from Gearbest that should the EU (due to the plug of the charger) B2017G on 7.1.1 build ZTE B2017GV1.2.0B13 can reboot in EDL via adb, but PC doesn't find it and so Zadig too...I try several USB port, just one time I heard the "plug in sound" but immediately win 10x64 told it was not able to recognize the device and device manager didn't show the 05c6:9008.In option->list all device there was an "unknown USB device" but I obiviously didn't go ahead...

Some EU user where able to install TWRP in nougat, so maybe it's a problem of buil, so maybe I need to downgrade to first nougat firmware (*09 or somethin like it..) but a lot of people says that this 0B13 fixes a lot of bugs...

Actually I need root just for Advertising and to make the storag adoptable...:(

Someone was able to use this tool with 0B13 build?

Thank you
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] vincent1967:
Same here : Windows 10, European version, same firmware, reboot EDL ok using ADB but "unknown USB device" remains what ever i do. And i can't match any driver ( Qualcomm ) with that.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] maestromony:
I guess no. I tried eu 7.1 B09, B12, B13. Same result.

By the way, one of the previous version (without 3rd command-line parameter) worked fine before.

As for me - it seems to be phone issue or cable, though device works fine using stock firmware.

Tdm, if you have old tuliptool version - can you send it to me for testing please?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] moyses:
Hello just get an Tulip phone with B2017G V1.0.0B12 version

Tried every things to install twrp and root but failed

Tried with tuliptool but failed to, when i db click on tuliptool it doesn't open(I'm on last Windows 10), so tried with axon_mini_unlock and the same(i tried it from internal memory, no sdcard yet)

I'm very suprising by the difficulties issued with that phone( Generally qcom devices are not complicated as Mediatek) i'm an owner of OnePlus devices(that fonctions are child's play)

So please if some one can advise
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
I don't have the older version sorry. But it's the same code.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
Please read the OP again. You missed some information.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] moyses:
Please how to run tuliptool, i'm a junior on cmd and linux
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Diomorgan:
Previous version of firmware or ZADIG?

I try 2 different cables and 4 USB port 2x3.0 2x2.0

I have try installing Qualcomm drivers and the phone firmware drivers (the one you can install pluggind and choosing "install drivers") I have different reaction, but NEVER the right one, item not found...:(
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] maestromony:
Tuliptool.

But as said tdm it cannot be reason.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] vincent1967:
Good news, finally i successfuly flashed twrp ! :good: ( with a windows 10 32bits system )

In fact i had a lot of trouble and i wasted a lot of time with Zadig but it was all my fault cause i thought that the Axon, once plugged, will show up right away in the tool but that wasn't the case. By chance i clicked on "The all devices" list, and "05c6:9008" was right here, just under my nose. Next step, i installed the winUSB driver and went on to flash TWRP with Tuliptool. The last step, Lineage OS flashing was a piece of cake ;)

So my European Axon 7 Mini is now running Lineage on board, and let me tell you that i'm really happy !

Special thanks to tdm who makes it possible, i'll make you a donation to support your effort, you deserve it :good:
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] ataruz73:
TWRP not written

Dear all,

I just got my 7 mini.

The official recovery says:

zte/p852a11/msm8952_64

6.0.1/mmb29m/20170315.140125

the build number is: ZTE B2017G V1.0.0B12

I followed the xda guide and was able to unlock the bootloader:

>tuliptool-win64.exe lock status

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

Device unlocked: yes

Device tampered: no

Reset in 5 seconds ...

Reset in 4 seconds ...

Reset in 3 seconds ...

Reset in 2 seconds ...

Reset in 1 seconds ...

When I try to install the twrp recovery I get this:

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

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 ...

log: start 1181696, num 49152

Write 25165824 bytes, 49152 sectors

log: Finished sector address 1230848

Success!

Reset in 5 seconds ...

Reset in 4 seconds ...

Reset in 3 seconds ...

Reset in 2 seconds ...

Reset in 1 seconds ...

The problem is that twrp is not written and I still have the original recovery. Any idea what's going on?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
You need to update to 7.1.

6.0 probably over writes recovery at boot. But note twrp won't boot on 6.0 firmware anyway.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] ataruz73:
Thank you very much TDM, I solved my issue exactly as you suggested.

I spent 1 day on this bu t finally lineageos is running! :D
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Diomorgan:
Finally yesterday I installed the drivers to follow this thread: https://xdaforums.com/android/development/lenovo-p8-tb-8703f-wifi-how-to-flash-t3720621, actually I don't remember if the tablet installed the drivers itself or it was one of the packages, but even if Zadig did'nt recognize the phone when i setted in EDL mode via ADB, tuliptool worked very well, I flashed the TWRP and magisk! So now I have the 64GB adoptable storage, adaway and I can restore with My Backup Pro all my primary phone apps with settings.As soon as Lineage will be 100% working I will install it, maybe lineage can move the apps to the SD, since the stock firmware doesn't allow to move to external memory.I have only one regret with this phone: I can't use 2 sims+SD, I know is common now to make you choose, but I think that is a BIG down, you waste a cool feature.Only a few chinaphone and Samsung J5 duos allows 2 sims and an SD card.If only Axon 7 mini had 64GB....Thank you again for your post!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] k500zm:
[MENTION=4168480]Diomorgan[/MENTION] - Titanium Pro can move apps to the sd card

2 sims and an SD card https://xdaforums.com/axon-7-mini/how-to/2-sims-sd-card-problem-t3757389
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Diomorgan:
I know, but it uses a personal method that is not thats table.There is Link2SD solution that can link and, as titanium, move the apps, but when you do it they say you should pay attention...

Anyhow something wnt wrong, because I was restoring from MyBackup Pro and says "not enaught" space...

I adopted with the app Root essential, but before rooting I was able to adopt via ADB with the same trick used for Samsung S7 and it appears to work better...

Will do some try tomorrow, now that we have a recovery <3 we can made a lot of experiments!
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] giggls:
How to do stock 7.1 update

How did you manage to upgrade to 7.1? When using the update function inside Android the phone is telling me "Your software is up to date" :(
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] pita:
Giggls look this

Look at this thread and I hope it helps:

https://xdaforums.com/showpost.php?p=75847574&postcount=110

I got the file for 7.1 for the version I had here:

https://xdaforums.com/showpost.php?p=73257562&postcount=13

pita
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] Perul:
What exactly should I to do, to start the phone in EDL mode?

I entered "adb reboot edl" and a black screen appeared on the phone, but zadig doesn't detect any device, to install the driver.

I then pressed the power button for 3 seconds and the result was the same - not detect any device (screen was black).

Next time i tryed to press both volume buttons, but not result (screen was black too).

After turn by adb to this mode, I had to press the power button for more than 10 seconds (reset) to start phone.
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] mentao:
Hi,

I'm trying to use tuliptool but I'm having issues getting at the unlock status.

The phone (purchased from a German shop) is on ZTE B2017GV1.2.0B13 from the ztemobile.de support page (sorry, can't post link).

My laptop is on OpenSUSE 42.3, udev rule installed, user member of plugdev.

After rebooting into EDL with adb, 05c6:9008 shows up in lsusb but running tuliptool gives an error:

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

The timeout comes pretty fast:

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

real	0m0.506s
user	0m0.000s
sys	0m0.006s

Any hints on how to get tuliptool working? The goal would be to flash TWRP.

Do I need a specific version of libusb or something?
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] k500zm:
Try a different PC Laptop or use a dfferent usb port
[ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other] tdm:
I tried to build the tool to be as compatible as possible. The tool is compiled against libusb-1.0. If it loads, it should be okay.

Make sure your device is connected directly, not through a port expander or anything. And perhaps try a different port.