Database Info

Can someone spell out what I need to do to unbrick my Transformer?

My Transformer informed me of an OTA update, which I tried to perform. It stuck on the boot screen and wouldn't go any further. I managed to wipe it and get it going again by switching off and pressing power and volume down, so I rebuilt it and it again wanted to do the update - with the same result.
I tried side-loading the update and again, it froze, so I downloaded and ran NVFLASHTF and now I can't get anything on the display whatsoever. All I can do is connect it to my PC and it makes the familiar connection sound and I can get to the SD card, but nothing else.
I need someone to show me what to do step-by-step as if I was completely stupid (which I obviously am!).
Please help if you can.
TIA

the nvflash sticky in the dev section includes a youtube video.
although the most likely reason your nvflash didn't work, is you extracted the files in the wrong place. make sure they are in the same place as the download.bat file.
Sent from my Transformer TF101 using Tapatalk

I have all the nvflash files in the same folder as extracted from the .zip file. I even have Prime 1.6 in the folder.
All I seem to be able to do is press the power button and either Up-vol or down-vol (or both) and the computer disconnects and immediately reconnects. When I run the download.bat file, it seems to run and complete the formatting and then download something and the dos box disappears at that stage. The tablet is showing the following...
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 027c100040a0b2d7
Click to expand...
Click to collapse
That is the only thing I can get to display - and, of course, it stays like this until I try to reboot again.

copy and paste what you get when you run the batch file into here...once it finishes
Pretty sure the tf should reboot on its own if done right.
Did you also check the md5sum of the downloaded files?
I followed these instructions..worked perfectly
http://tabletroms.com/forums/transf...ock-3-1-stock-3-2-recovery-roms.html#post9968

The Dos box disappears when it finishes so I can't paste it here and yes, I checked the files. In fact, I tried it on three different PCs (W7 64-bit, W7 32-bit and XP Pro 32-bit), all without success.

Have you plugged it straight to power and switch it on?

Yes - no difference.

I think you need nvflash experts help.
Only thing i can think of is the old adb way to transfer a blob file...
Or...
Open a command prompt and go to the directory with the batch file and then run it ..dont double click but just type it in the dos window.. once it finishes it shouldn't close the window and you can see what happens.

maybe try a different usb port, I have 4 ports on the front of my pc but for some reason only ONE port works when i try to nvflash,also have problems if I use a hub or extend the cable in any way

Malandro2011 said:
I think you need nvflash experts help.
Only thing i can think of is the old adb way to transfer a blob file...
Or...
Open a command prompt and go to the directory with the batch file and then run it ..dont double click but just type it in the dos window.. once it finishes it shouldn't close the window and you can see what happens.
Click to expand...
Click to collapse
Ok, the second option got me a little bit of info. Bootloader.bin is installing but it is telling me that the file 'recovery.img' is not found.

you can prevent the dos window from closing by starting the command via command line.
start > run > cmd (enter)
dir c:\where\nvflash\is\located (enter)
download.bat (enter)

OK, it's official - I'm an idiot!
I had downloaded the nvflash version of Prime 1.6 but hadn't extracted the files! I now have a working version of Prime 1.6 and am restoring the data as I type.
Thanks for all your help, especially the suggestion of running download from a dos prompt, which let me see where I was going wrong.

Excellent!
Glad it's all sorted

[Q] HELP HELP HELP Bricked

Ok here goes.. I have a ASUS TF101 and tryed to install Cyanogenmod 9 on it and to my amazment it worked but then it shut off after a min and now is stuck on the 1st boot screen (EEE Pad) I tryed to restore stock rom in recovery but nothing happened then I tryed using easyflasher and couldn't enter into apx mode the only thing I can do is enter recovery mode and see that its running ClockworkMod recovery 6.0.1.3
Please help me

Meat6911 said:
Ok here goes.. I have a ASUS TF101 and tryed to install Cyanogenmod 9 on it and to my amazment it worked but then it shut off after a min and now is stuck on the 1st boot screen (EEE Pad) I tryed to restore stock rom in recovery but nothing happened then I tryed using easyflasher and couldn't enter into apx mode the only thing I can do is enter recovery mode and see that its running ClockworkMod recovery 6.0.1.3
Please help me
Click to expand...
Click to collapse
How did you install CWM 6.0.1.3? Did you use ROM Manager? If so, that is your problem.
You need to get a working recovery installed.
Are you sure you could not get into APX Mode? It is a black screen and the only indication is that your computer detects new hardware.
If you cannot get into APX to use EasyFlasher or NVFlash, is your tablet recognized as an ADB device in CWM? If so you can push a new recovery using the dd command. I would recommend checking out TWRP.
To install TWRP via ADB, download the latest TWRP from here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save it as TWRP.blob in an easy to find place (like c:\TWRP.blob)
Connect your tablet to your PC and update the driver and use the Universal Naked Drivers
Put the adb.exe file in the c:\ folder as well (in the EasyFlasher Tools folder)
Open a command prompt (WIN+R, type CMD and click OK)
Code:
adb devices
(if connected, should show a device connected)
adb push c:\TWRP.blob /sdcard/
adb shell
cd /sdcard/
ls -a -l
(check for TWRP.blob)
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Do not try to enter recovery until after it reboots past the Eee Pad logo (and shows the progress indicator). This is when it acutally updates the recovery.
Once you see it get past the Eee Pad screen hold VOL DOWN and POWER for about 12-15 seconds and then press VOL UP once you see the small text and it should boot to TWRP recovery.​
Here are the ADB commands to run:

When I connect to PC it makes the connection sound but doesn't show as a removable drive so I can't use Easyflash or any program like that also like I said APX mode wont work it makes the sound that it detects the tablet but then makes the remove sound right away. and this happened when I installed the Cyangenmod 9. I found someone who says he may be able to fix it for $50 using Odin but I am worried that he wont be able to and its an hour drive to take it to him... At this point I just want it back to stock ...

erm... ODIN won't work with a transformer, it's only for samsung devices.
Alright, you probably used ROM manager judging by your Recovery version.
You need to just NvFlash the device back to stock:
Download your region's Stock ROM from here: (WW if outside of US, US if inside.) Stock Rom
Download Wheelie NvFlash tool from here: Wheelie
Unzip the stock rom .zip first, into it's own folder. Then unzip the wheelie tar.bz2 into the folder you just made by unzipping the stock rom. Overwrite any files with the wheelie files.
Next find out your Sbk variant, Look at the serial number on the sticker on the bottom of your tablet.
If it says B70, or a higher number like B80 or any C, then you are Sbkv2
If the number is B60 or lower, you are Sbkv1.
Remember this for the next step.
Make sure the tablet is off totally, Then hold the Volume-UP key and Then press power, keep holding volume up. It will enter APX mode.
Plug it into your computer, the screen will stay blank.
It should be detected, if it says unknown device or similar, use the windows device manager to select the 'asus bootloader interface' or 'Unknown device' or similar, with Nvidia ASUS or APX or Bootloader, something along those lines, to update the driver, right click this and navigate to the 'usbpcdriver' folder in the folder you unzipped earlier. It will install and detect.
Then run the .bat file that says Reflash_(Your Sbk version).bat while the tab is connected in apx mode.
It will return to stock, give it time, DO NOT UNPLUG IT.
The screen may flash, and the tablet may/will reboot.
When done you will be on Stock latest from ASUS.
If you want safe root / recovery, download and run my PERI tool, link in signature.
good luck.

ok I am trying that now but I wish I had someone to walk me through everything in real time...

OMG you are the best Thing O Doom I bow down to your all mighty knowledge lol thank you

Meat6911 said:
OMG you are the best Thing O Doom I bow down to your all mighty knowledge lol thank you
Click to expand...
Click to collapse
erm, I guess it worked?
The best thing you can do for someone on xda is hit the 'thanks' or donate buttons, and thanks is free!
Any other questions, I'm guessing it worked alright?

frederuco said:
How did you install CWM 6.0.1.3? Did you use ROM Manager? If so, that is your problem.
You need to get a working recovery installed.
Are you sure you could not get into APX Mode? It is a black screen and the only indication is that your computer detects new hardware.
If you cannot get into APX to use EasyFlasher or NVFlash, is your tablet recognized as an ADB device in CWM? If so you can push a new recovery using the dd command. I would recommend checking out TWRP.
To install TWRP via ADB, download the latest TWRP from here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save it as TWRP.blob in an easy to find place (like c:\TWRP.blob)
Connect your tablet to your PC and update the driver and use the Universal Naked Drivers
Put the adb.exe file in the c:\ folder as well (in the EasyFlasher Tools folder)
Open a command prompt (WIN+R, type CMD and click OK)
Code:
adb devices
(if connected, should show a device connected)
adb push c:\TWRP.blob /sdcard/
adb shell
cd /sdcard/
ls -a -l
(check for TWRP.blob)
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
reboot
Do not try to enter recovery until after it reboots past the Eee Pad logo (and shows the progress indicator). This is when it acutally updates the recovery.
Once you see it get past the Eee Pad screen hold VOL DOWN and POWER for about 12-15 seconds and then press VOL UP once you see the small text and it should boot to TWRP recovery.​
Here are the ADB commands to run:
Click to expand...
Click to collapse
I had similiar problem when I tried to downgrade and go back to stock. After flashing stock from asus, I did it wrong by unzipping (stock_ics_kernel_9.2.1.24US-secure) first then flash the file under the downloaded zip files. Now I am also stuck at Eee Pad, can't get into recovery because it probably wiped out everything. Hopefully this can recover my Eee Pad!!!! I got my fingers cross. This may be my only hope for my asus pad .

Ok so off topic question how can I watch videos online from like 1channel or other streaming sites and what is the best ad blocker and antivirus to use

Meat6911 said:
Ok so off topic question how can I watch videos online from like 1channel or other streaming sites and what is the best ad blocker and antivirus to use
Click to expand...
Click to collapse
You should be able to with Dolphin HD browser and Flash installed, make sure flash is integrated into the Dolphin. That or the sites should just work..
I use Adaway.

HTC ONE S is dead - how to save data?

hello everyone.. i have a htc one s ..
3 days ago it just went off with enough battery for no reason and it is not possible to switch it back on.. also power und volume buttons dont work and the screen always stays black .. i charged it for over a day and still completely dad..
when i connect it to the pc, i hear the sound of a new connection, but i think that it is just charging.. i see qhsusb_dload in the device manager the phone was never rooted or anything like that .. i just want to get my data back .. especially the photos on it.. would it also be possible to open the phone and get the sd card out or isn't there such a card? is there any chance to get the data out .. i already bought a new phone but i really would love to get all the photos back which havent been backed up for a year
thank you all in advance!

Try this http://unlimited.io/qhsusbdload.htm to relive your phone

Thank you for your fast reply.. but sorry, i have no idea how to install and boot to ubuntu
may someone please explain it to me step by step?

You can download from www.ubuntu.com and try to make a live usb with unetbootin. After that start up your pc from usb and run ubuntu. then download http://unlimited.io/qhsusbdload.htm and try

okay .. it is downloading and what to do next? just put the file on a usb stick? and how to boot from the stick?
sorry for being such a noob

Oh Men... Hahaha. Its very difficult explain here ... You can search how to make a ubuntu liveusb. And how to try ubuntu with out installed... Then when you Boot on ubuntu follow the instrucctions http://unlimited.io/qhsusbdload.htm

okay.. i created the usb stick and booted to ubuntu.. i downloaded the file and opened the terminal
then i connected the phone via usb and entered the commands.. still the phone stays black .. no matter how long i press the power button .. any ideas?
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ unzip PblClear.zip
Archive: PblClear.zip
inflating: PblClear
[email protected]:~/Downloads$ chmod 755 PblClear
[email protected]:~/Downloads$ sudo modprobe qcserial
[email protected]:~/Downloads$ sudo ./PblClear
============= PblClear 0.1 =============
(c) Copyright 2012 Unlimited.IO
This program may not be redistributed in
nor included in other works works without
the express permission of team Unlimited.
Starting pblreset...
Press ENTER to start
QDL reset

Lisa1991 said:
okay.. i created the usb stick and booted to ubuntu.. i downloaded the file and opened the terminal
then i connected the phone via usb and entered the commands.. still the phone stays black .. no matter how long i press the power button .. any ideas?
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ unzip PblClear.zip
Archive: PblClear.zip
inflating: PblClear
[email protected]:~/Downloads$ chmod 755 PblClear
[email protected]:~/Downloads$ sudo modprobe qcserial
[email protected]:~/Downloads$ sudo ./PblClear
============= PblClear 0.1 =============
(c) Copyright 2012 Unlimited.IO
This program may not be redistributed in
nor included in other works works without
the express permission of team Unlimited.
Starting pblreset...
Press ENTER to start
QDL reset
Click to expand...
Click to collapse
that its just a idea... maybe work maybe not . you follow the instructions very carefully?

Yes. I did it just like the instructions and at the end it said qdl reset
but it is still not possible to bring the device back to life ..
is it somehow possible to save the data? i read about opening the HOS and unplug the battery.. would you think that this could help? or is there any other chance?

Lisa1991 said:
Yes. I did it just like the instructions and at the end it said qdl reset
but it is still not possible to bring the device back to life ..
is it somehow possible to save the data? i read about opening the HOS and unplug the battery.. would you think that this could help? or is there any other chance?
Click to expand...
Click to collapse
Really i dont know my friend . I dont think the one s have a sd internal.. so i dont know how to save data... The only way is turning on the phone

anyone else?
when i connect it to the pc it is shown in the device manager as "unknown device" .. so it really looks like it has left the qhsusb_dload mode.. but still no chance to get access to the data or to switch it back on

Lisa1991 said:
anyone else?
when i connect it to the pc it is shown in the device manager as "unknown device" .. so it really looks like it has left the qhsusb_dload mode.. but still no chance to get access to the data or to switch it back on
Click to expand...
Click to collapse
You have installed lasted HTC drivers?

yes ... deinstalled them and installed them again .. also the phone doesn#t start without using the pc

Lisa1991 said:
yes ... deinstalled them and installed them again .. also the phone doesn#t start without using the pc
Click to expand...
Click to collapse
Dont start without using pc? Did you mean with pc turn on?

that is what i did .. and it seems like the phone got out od the dload mode... but still i cant switch the phone on
and if i connect it to the pc, it only starts charging but i dont get access to the data, because it is still switched off...

Lisa1991 said:
that is what i did .. and it seems like the phone got out od the dload mode... but still i cant switch the phone on
and if i connect it to the pc, it only starts charging but i dont get access to the data, because it is still switched off...
Click to expand...
Click to collapse
Are you try connect to pc and press power+volDown for a Long time?

more than two minutes.. no result..

Moderator Information,
Thread cleaned. Keep posts on topic.

Need Serious help Rooting the K1 Nvidia Shield Tablet on Linux MInt 18

(first, If im on the wrong thread can you help with asking a moderator to move it to the correct place, or how ever that would work? Thanks!!)
Im on Linux Mint 18 Sarah Cinnamon 64 bit
I'm trying to root my Nvidia K1 shield tablet. no idea what im doing and the more I research this the more confusing it gets. Seems like If you ran windows theres "Clear Cut & Right to the Point" instructions about how to do this on about 14 hundred pages of great info including great you tube videos which heavily explain it, in great easy to understand detail.
What Ive done so far.
installed ADB and BootLoader (but ive no idea how to actually use these programs yet, still figuring that one out)
I have sucessfully Unlocked the Device
Now im trying to flash the .img I hit this command (from terminal) and get this result
$ fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.658s]
writing 'recovery'...
OKAY [ 0.651s]
finished. total time: 1.309s
Now following these steps at this website http://developer.download.nvidia.co.../0_0_0_Factory/HowTo-Flash-Recovery-Image.txt
im on the:
$ fastboot flash boot boot.img
error: cannot load 'boot.img'
Now ive no idea what to do, how to fix this ,or even if im following the right directions. what I need is (im going to throw a nice Trump statement here)
Can someone explain how you root a Nvidia shield K1 tablet, start to finish, ON LINUX, and every step simplified along the way explained, PERIOD!!!!
Everyone starts to tell you how to do this, then they jump on a windows PC throwing me all off...
now my .img file is from this website https://www.androidfilehost.com/?fid=24269982087005399
its in my downloads folder if that matters??? Not sure but i think it does. If i need to move this .img file somewhere please explain how to do it, don't just say "oh your problem is you need to move it to /usb/local/ or something," and just leave it there. remember i need help, so if I need to move things and use commands please help me with that. thank you
You know I got my MCSE, MCSA, A+ SERVER+ NET+ NOVEL and I can write python Programs and im getting into Julia. I know DOS, & I feel im a power User on Andriod, and ive been using personal computers since the 1970's. But when it comes to linux, I cant even google my way out of anything, even if the problem is very minor and simple, still, I cant google my way out of anything on linux its crazy. I keep having to write on forums on threads to find the answer. Someone with my Creds, granted most were aquired in 2002, shouldnt struggle like I do with linux, the support is terrible, and I dont mean updates for software and hardware, im sure thats fine. But when it comes to user support and the documentation for instruction, you get pages of results that have more links then answers on the page to other peoples help pages, that link more to other pages. You cant just goto 1 page, get the answer, done finished your allset, NOPE LINUX does not work that way and its to bad, I see why most of the world doesn't use it.
Good analogy right here, if someone in your neighborhood is giving out free gold to anyone, you know ya whole villiage or town is going to be there getting free gold, ya well, if Linux was that good, the whole world would be using it, and there not, and its free just like the gold. So does that tell you anything?

settled that, smashed the tablet, going to mount it on my wall as a reminder for tech not to mess with me. and yes linux sucks balls!!!!

Maverick617 said:
settled that, smashed the tablet, going to mount it on my wall as a reminder for tech not to mess with me. and yes linux sucks balls!!!!
Click to expand...
Click to collapse
I suggest anger management and growing some sort of ability to wait periods of time before going all hulk smash... You waited all of 2 hours for someone to tell you you had already finished all you needed a pc for... After flashing the twrp recovery over adb all you needed to do was boot into it. you could have done so by shutting it off then holding vol down and power to get you to the fastboot menu then use the volume rockers to go to recovery the power button will be enter in this case and it should boot the recovery you just loaded.
From there you flash the super su binary you already downloaded and when you boot into the tablet after that you can load a apk from the google play store supersu is what i use then you are rooted...

mirrin said:
I suggest anger management and growing some sort of ability to wait periods of time before going all hulk smash... You waited all of 2 hours for someone to tell you you had already finished all you needed a pc for... After flashing the twrp recovery over adb all you needed to do was boot into it. you could have done so by shutting it off then holding vol down and power to get you to the fastboot menu then use the volume rockers to go to recovery the power button will be enter in this case and it should boot the recovery you just loaded.
From there you flash the super su binary you already downloaded and when you boot into the tablet after that you can load a apk from the google play store supersu is what i use then you are rooted...
Click to expand...
Click to collapse
Also just going to add the process is the same in mint/ubuntu as it is in windows. Getting fastboot/adb is the only difference, and it basically tells you how to do if you try using fastboot without it installed. Also make sure you are in the right directory and type the correct name or you get the cant load message.

Additionally as someone who had to learn linux cli on Red hat i would have to say vs ms dos about the same... if the op thinks mint is bad i have some old yellow dog and mandrake 7.0 disk i can send him. He does not know the pain of trying to find the drivers on repositories and such just to get the sound and Ethernet working... Had the issue of my realtek 10/100 card not working under linux but my 3com card would if i had preloaded the drivers...
I have tried unbuntu and mint both gave a very similar experience to installing windows. With the exception unlike windows i did not need to patch 1000 things before using it and everything just worked.
Also Android is linux...
SHIELD TABLET K1 RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method: (If you had done this after the part you loaded what ever recovery nvidia tried pushing on you it should have worked)
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
(I dont even know what this from nvidia is talking about)http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172 <--go to the xda first next time...
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
fastboot flash staging blob
(Better instructions that i found on this place)
https://twrp.me/devices/nvidiahshieldtablet.html
adb reboot bootloader
(https://dl.twrp.me/shieldtablet/) Download latest here rename the .img file twrp.img maesure the file is in the adb folder...
fastboot flash recovery twrp.img
fastboot reboot
After boot you can issue this command
adb rebooot recovery
or
shut off the tablet
hold vol down then hold power
then press vol down until recovery is highlighted then push power button...
Unlocking the Bootloader<you needed to do this first>
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
Click to expand...
Click to collapse

[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