Database Info

SPV-Services

Today I'll try to flash another rom that I have but when I run SPV-Services It doesnt found a page in the internet!!- connection to the internet is normal

check your firewall, turn it off if you can

I doesn't use it!

Open Microsoft Active Sync, click File -> Connection Settings -> where it says this computer is conected to: usaully is automatic change to internet

I make so ,and I downloaded new one from karhoe's website but the same problem!! Can you try to run SPV-services?? or can your send me your one by the ICQ??? I make SuperCID when I flash previous rom but now I can't!

Oh....when I try http://www.spv-developers.com it also doesn't work!! Maybe trouble in this?

If I SuperCID my phone when I flash the previous rom, can I skip this step for the next roms?

spv-developers is not always online...

Hey recently happened to me the same with svp however If you SuperCID your phone before you'll be able to skip this step but to be sure that your phone have SuperCID check it with TeraTermPro, I guess you know the steps if not they are:
1.Disable usb connection of the ActiveSync(Uncheck allow usb connections).
2.Unplug usb cable.
3.Turn your phone off.
4.Press the camera button and plug the usb cable(You'll see thw white screen and seconds later the three color screen.
5.Run TeraTermPro.
6.Select Serial and in port: USB then ok
7.Type: info 2
and if in the end of the list you see supercid htc or something like that it's done!!
Close TeraTermPro and just run any ROM you want and voilaa!!
Hope this be useful for you.
However if you don't see your phone superCID tell me and I'll tell you how to do it without svp services. By the way if you dont see you supercid your phone to get back to the phone OS just remove the battery and turn it on.
See ya from Mexico!

Hey check my post http://forum.xda-developers.com/showthread.php?t=412139 Hope you reach SuperCID your phone!!
See ya from Mexico

Tera Term says:GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
***** user area size = 0x3B880000 Bytes
HTCSSuperCID ' HTCE
as I know it means that device already SuperCIDed!?

Please help!
First SPVServices cannot connect to the remote site.
Then, I tried the alternative using Unlock_SuperCID_Your_SPV_C500_550_600.rar. Followed every step exactly. When I run Lokiwiz.bat, here is the output from the MSDOS window:
....
--------------------
U. Unlock
L. Lock
C. CID Unlock (SuperCID)
Q. Quit
--------------------
Type the letter and press Enter: C
CID unlocking mobile... DO NOT DISCONNECT UNTIL THE PHONE REBOOTS!
ERROR: Unable to open WinCE file '\windows' - Returned by WSARecv or WSARecvFrom
to indicate the remote party has initiated a graceful shutdown sequence.
opening: lock_backup.bin: No such file or directory
This exe file was created with the evaluation version of Perl2Exe.
For more information visit http://www.indigostar.com
(The full version does not display this message with a 2 second delay.)
...
Then, I just try invoking pdocread manually, regardless of what command line argument I put, or no argument at all, the response is always the same " ERROR: Unable to open WinCE file '\windows' - Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence."
From ActiveSync, I do see \windows, but as a directory, not a file. Anyone got any inside or suggestions?
PLease, please help! Thank you so much!!!
/dan

[SOLVED] Infuse wont connect to Ubuntu....

UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.

weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.

Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.

Linux driver should be perfect, before connects to PC the mass storage mode should be selected.

dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/

well I see you fixed it. did you get adb going?

Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk

are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.

Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone

unbrick commands problem

hi everyone i've found another thread about this problem but no one answered to me so i decided to start a new thread.
I'm trying to unbrick my one s but I'm blocked at the second command of the tutorial when I've to enter the command ls dev/sd* etc..
I'm trying in the right way: when 'qualcomm inc. ecc ' disappear I do the command in the second window of the terminal (I alredy tried faster and faster) but I always had back the same yellow line without sd*4 and 12 that i need...
can you help me??? sorry for my bad english!

Try to unplug and replug the USB cable. I have the same problem and after unplug and replug usb cable that work. Maybe you must hold power down on your phone for about 10 seconds after replug
If that does not work, restart the computer

jac10000 said:
Try to unplug and replug the USB cable. I have the same problem and after unplug and replug usb cable that work. Maybe you must hold power down on your phone for about 10 seconds after replug
If that does not work, restart the computer
Click to expand...
Click to collapse
I've tried to unplug and replug and also to restart my pc,but I recive everytime the same line without what I need ..
I'm running ubuntu 12.10 fully installed on an external hdd..can this be a problem?

Have you really brick your phone with killp4 ?
You should talk about your problem in this thread beacause you would have more answers: http://forum.xda-developers.com/showthread.php?t=1990043

jac10000 said:
Have you really brick your phone with killp4 ?
You should talk about your problem in this thread beacause you would have more answers: http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
I've not bricked the phone with the guide,but after I flashed an RUU and tried to update OTA to JB..then,during the automatic process ,the phone stopped band gone bricked . so I can 't follow the guide from the start and the files that I need ha ve been passed to me by some people on another site.
PS.I can't write on that thread because I ve not 10 posts yet

UMBYDD said:
hi everyone i've found another thread about this problem but no one answered to me so i decided to start a new thread.
I'm trying to unbrick my one s but I'm blocked at the second command of the tutorial when I've to enter the command ls dev/sd* etc..
I'm trying in the right way: when 'qualcomm inc. ecc ' disappear I do the command in the second window of the terminal (I alredy tried faster and faster) but I always had back the same yellow line without sd*4 and 12 that i need...
can you help me??? sorry for my bad english!
Click to expand...
Click to collapse
Notes:
I did this procedure yesterday - I cry once or twice! - but it will 100% work. Relax!
It can be very,very hard the 'working time' is only seconds - I was not quick enough to do a ls in the other window. I suspect this is your problem.
On my TMobile HTC One S, I had to hold the power button for 15 seconds then release ( not ten nor thirty ). I suspect this could be your problem too.
On some linux distro's the kernel module qcserial will block the emmc_recover program ( not your problem )
On some linux distro's udev will be too slow and the procedure cannot work => Debian based distro's seem to work better. ubuntu should be fine
On some linux distro's /dev/ttyUSB0 is taken by other devices - this is hard coded in emmc_recover. Often this is used by USB to serial devices or internal modems in laptops ( also not your problem )
The 'new' drive letter is always one more. i.e. One a two disk rig ( sda & sdb ) the phone will be sdc
=> My suggestion to all is: Recover mmcblk0p4 ( bakp4 ) first as it's only one write - this is step 12. If this works and the phone is okay (and you are okay!), brick it again then do the full procedure.
This may give you better visual:
1) Run a shell script or enter in a linux shell:
while true
do
ls -al /dev/sd*
echo =========
sleep 0.2
done
2) While above running, connect the phone and do the 15 second power button push then release. Remember to verify with the suggested command ( watch -n 1 lsusb )
With reference and much thanks to the software and forum authors for http://forum.xda-developers.com/showthread.php?t=1990043. I cannot post their either as I am new user too.
Hope this helps, good luck

bluebenno said:
Notes:
I did this procedure yesterday - I cry once or twice! - but it will 100% work. Relax!
It can be very,very hard the 'working time' is only seconds - I was not quick enough to do a ls in the other window. I suspect this is your problem.
On my TMobile HTC One S, I had to hold the power button for 15 seconds then release ( not ten nor thirty ). I suspect this could be your problem too.
On some linux distro's the kernel module qcserial will block the emmc_recover program ( not your problem )
On some linux distro's udev will be too slow and the procedure cannot work => Debian based distro's seem to work better. ubuntu should be fine
On some linux distro's /dev/ttyUSB0 is taken by other devices - this is hard coded in emmc_recover. Often this is used by USB to serial devices or internal modems in laptops ( also not your problem )
The 'new' drive letter is always one more. i.e. One a two disk rig ( sda & sdb ) the phone will be sdc
=> My suggestion to all is: Recover mmcblk0p4 ( bakp4 ) first as it's only one write - this is step 12. If this works and the phone is okay (and you are okay!), brick it again then do the full procedure.
This may give you better visual:
1) Run a shell script or enter in a linux shell:
while true
do
ls -al /dev/sd*
echo =========
sleep 0.2
done
2) While above running, connect the phone and do the 15 second power button push then release. Remember to verify with the suggested command ( watch -n 1 lsusb )
With reference and much thanks to the software and forum authors for http://forum.xda-developers.com/showthread.php?t=1990043. I cannot post their either as I am new user too.
Hope this helps, good luck
Click to expand...
Click to collapse
well..first of all this is not a problem of speed.. I'm really really quick! then the 10 seconds procedure works well for me..after 10 sec the qualcomm. inc. etc disappear.
I have the bakp4 because I take it from another friend on the forum.
now I've not comprise so well your procedure ..can you explain me better the 2 steps? thank you!
ps.I've tried to do the step 12 but it tells me COMMAND NOT FOUND

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire

The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk

Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S

USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.

It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S

I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.

maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.

No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance

dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...

dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance

Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help

jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.

windows 8 have a issue with ville fastboot... please make you sure you have a fix

zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic

..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...

Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!

Thank you very much bro. HTC One V good working.

[UNLOCK] Tuliptool: unlock, TWRP, and custom boot

First let's get the warnings out of the way:
This is a dangerous tool. It can render your device permanently unusable.
If you use it, your warranty will likely be void.
You accept all responsibility for the consequences.
This is not an official ZTE unlock tool. The official ZTE unlock tool is in another thread.
Acknowledgments
Special thanks to @rombdeta for providing the OEM programmer binary. This would not be possible without his help.
What is tuliptool?
This tool allows you to:
Check status of your boot loader
Unlock your boot loader
Lock your boot loader
Install a custom recovery
Install a custom boot image
NOTE WELL
The first rule of intelligent tinkering is to save all the parts.
Always backup your partitions before writing new contents, so that you can get back to where you started.
Never write both boot and recovery in one session. Always make sure that you can boot into the other partition in case something fails.
Locking and unlocking will erase all user data. Make sure you backup first!
The zip includes:
tuliptool for Linux
tuliptool for Win64
tuliptool for Win32
tuliptool for MacOS
Preparation
1. Extract the package.
You will find the binary files listed above. Note: This is a command line utility, so you must open a command prompt to run it.
2a. Setup for Linux
Create a file named /etc/udev/rules.d/99-qcom.rules with this content exactly as shown:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
Ensure your login user is in the plugdev group.
2b. Setup for Win32/Win64
Download zadig.
Connect your device in EDL mode (see below).
Windows will want to install the Qualcomm USB driver. We won't be using it so you can cancel if you wish, but it won't hurt anything.
Run zadig. Find device 05c6:9008 and install the WinUSB driver for it.
Disconnect the device.
2c. Setup for MacOS
No setup should be necessary.
3. Download boot and/or recovery files to flash.
You will find these in other threads in this section.
Connecting in EDL mode
Via adb
This should work for all models, but you need adb access.
adb reboot edl
Via key combo
If you have a US model device (or the aboot from a US model device) you may use the key combo:
Power off and unplug the device.
Hold both volume buttons.
Plug device into your PC.
Wait about 3 seconds and release the buttons.
Note: There will be no feedback on the device -- no lights, no vibration, nothing. The only way to verify that the device is in EDL mode is that device 05c6:9008 is visible on the PC.
Usage: (un)locking
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, unlocking seems to be completely unnecessary. This section is mostly provided for completeness.
tuliptool lock status
tuliptool lock unlock
tuliptool lock lock
Usage: reading boot/recovery
Note command line options have changed
tuliptool read boot
tuliptool read recovery
Usage: writing boot/recovery
Note command line options have changed
tuliptool write boot <filename>/I]
tuliptool write recovery <filename>
So, for example, to write a TWRP image, run:
tuliptool write recovery tulip-twrp-7.1-r1.img.
Multiple operations
This is a "one shot" tool. After performing an operation, it will reset the device with a 5 second countdown. If you wish do perform multiple operations (eg. backup, unlock, flash), simply hold down the volume buttons while the device resets and it should go back to EDL mode.
Download
tuliptool.zip
md5=58f34850005510b51a832d27a6bce607
Common problems
Device not found: first enter EDL mode, then run the tool.
Device is visible in device manager or lspci but cannot be found by the tool: connect directly to the PC, not through a hub.
Windows says bad file descriptor: the WinUSB driver is not installed.
Linux says permission denied: your login user is not in the plugdev group.
Why call it tuliptool?
Tulip is the device "code name" for the Axon 7 Mini (at least the US version).

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:

Perhaps try running it as administrator? I'm heading home from work and then I'll be taking a shot at this myself.

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
Meme Queen said:
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:
Click to expand...
Click to collapse

tdm said:
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
Click to expand...
Click to collapse
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: [email protected] [email protected]
log: [email protected] [email protected]
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.

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"

Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Meme Queen said:
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: [email protected] [email protected]
log: [email protected] [email protected]
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.
Click to expand...
Click to collapse

tdm said:
Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Click to expand...
Click to collapse
thanks! if there's any information you want me to provide, just let me know.

I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?

pxzei said:
I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?
Click to expand...
Click to collapse
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

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?

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.
MrWhite0429 said:
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?
Click to expand...
Click to collapse

tdm said:
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.
Click to expand...
Click to collapse
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.

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.
rombdeta said:
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
Click to expand...
Click to collapse

tdm said:
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.
[/B][/COLOR]
Click to expand...
Click to collapse
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 @tdm, 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
@tdm, 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.

CRAFTER0302002 said:
@tdm, 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.
Click to expand...
Click to collapse
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."

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.
@Meme Queen and @MrWhite0429 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.

tdm said:
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.
@Meme Queen and @MrWhite0429 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.
Click to expand...
Click to collapse
as in rename to recovery.bin?

Yes, that.
MrWhite0429 said:
as in rename to recovery.bin?
Click to expand...
Click to collapse