• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Tutorial] How to root the ZTE Warp Sequent. USE AT YOUR OWN RISK

Status
Not open for further replies.
Just a quick note to those that have never rooted a phone before, when you connect your USB to your PC, do NOT "Turn on USB storage". All you need is the drivers and if the phone is recognized by your PC then you probably do have them. If your PC doesn't recognize the drivers you've installed, a good trick is to download the PDAnet app because its driver is easily recognized by Windows. Hope this helps. :D
 
just figured something out: if you are running android 4.0.4 you will not be able to root with this script, atleast that is what it seems like, is there anyway to downgrade while unrooted?
 
much thanks to yaggermr!

fyi- i used PdaNet to load drivers for my warp, and the driver worked fine when using DoomLORD on my sequent, which was nib running android 4.0.4
 
i attempted uninstalling my drivers, and re-installing with pda net but i still cant get the script to work :(.
 
You are awesome!!! I've been trying for 2+ hours to root, installed this PDAnet app, and bam rooting in less then 10 seconds. THANK YOU!!!
 
Below is what I am getting when I run "runme.bat"

adb server is out of date. killing...
* daemon started successfully *

then nothing happens beyond that? USB Debugging is checked, unknown sources is checked...Which USB options should be used "Media Transfer" or "PC Software"? My computer seems to only recognize my phone when I use the "Media Transfer" USB option.
 
Below is what I am getting when I run "runme.bat"

adb server is out of date. killing...
* daemon started successfully *

then nothing happens beyond that? USB Debugging is checked, unknown sources is checked...Which USB options should be used "Media Transfer" or "PC Software"? My computer seems to only recognize my phone when I use the "Media Transfer" USB option.

adb drivers may not be installed correctly for it. put it in charge only, then go to your device manager by right clicking "my computer" and going to manage

then on your left there will be something that says "device manager"
if there is a device on that list that says "android" or "unknowndevice" with a yellow sign and exclamation point the drivers arent installed properly.
if they are installed properly there will be an expandable section at the top called android above the word computer and it wont be expanded to where you can see everything
if it has those error signs then you will have to manually install the drivers as i did. right click the device in question on that list and press "update driver software"
tell it to let you pick,
then a windows will pop up with a big list of categories or a list of "compatable" drivers, if there is a button that says "have disk" near the bottom right corner press that, if not hit next and itll be on the next page

then in the browse box that pops up go to the place where you installed the zte drivers which is either
c:\program files\ZTE 3GPhone USB Driver\Drivers\32bit
or
C:\Program Files(x86)\ZTE 3GPhone USB Driver\Drivers\64bit

if its in program files(x86) you have to use the 64bit drivers, if not then you have to use the 32 bit, and if you even have an (x86) folder you will already know you need 64 bit, 32bit windows doesnt have that folder

then just go into whatever folder from there that matches your os, windows 7 for me, and there will be working drivers in there you just have to make sure you pick the composite adb interface, and if that one doesnt work for you go through again and try a different driver, keep trying till it works or you run out of choices basically but it should work
 
In device manager "Android Phone" is recognized with no yellow exclamation sign and it expands to "ZTE Composite ADB Interface".
My laptop is 64 bit but for some reason the "ZTE_Handset_USB_Driver" folder is in program files and not in program files (x86) folder? Should I copy and paste the folder over into the Program Files (x86) folder?
 
no go to the device manager, click properties, update driver, and navigate to that folder. the system should then install the correct driver.

nevermind i red that wrong, thought there was a yellow triangle

if it aint broke dont fix it
 
Hello everyone!

Please dont cut me head off, but I use a Mac. I am kind of lost on how to really get this done. I have downloaded the SKD, and the DoomLoRd script. Anyone really know what I do next?
 
Hello everyone!

Please dont cut me head off, but I use a Mac. I am kind of lost on how to really get this done. I have downloaded the SKD, and the DoomLoRd script. Anyone really know what I do next?

ok the next step is to install windows on your mac lol
just messin with you, alright i guess since you asked nicely i will convert the script for mac. gimme a few
 
Thanks so much, you be the MAN.

Only problem, was fixed by Titanium pro, the SU Binary, showed as possibly going to be an issue. But the Sequent is now rooted. I needed to uninstall the drivers, that had loaded into Win-XP when I first had Windows detect the phone. They were the "latest" version 5.and role back to PadNets earlier, drivers 4 something, and also manually recheck the settings/developer options/debugging, that had come undone, probably during a re-boot. Thanks again.
 
i rooted my zte warp sequent with the root guide and my device now reboots after hitting the volume button while device is on and has trouble connecting to the boost mobile network and the phone app won le me display dial pad.

I have managed to root my phone using this script but unfortunatly I am having the same problem as groncki32. When I press the volume button my phone reboots. Furthermore, I can no longer access the sound settings under system settings. Does anyone have any ideas how I can fix this? Thanks
 
https://www.dropbox.com/s/1asljgo7o26p8zy/linux_mac_and_windows_rooter.zip
those SHOULD be properly converted scripts for linux and mac, if not let me know ill see what i can do
remember to chmod a+x or find another way to make them executable

and i cannot take credit for this code, nor will i take responsibility if something goes wrong, i merely changed the format

I appreciate this more than you know!! Ill give this a try and let you know ASAP!! You are awesome my man!
 
and if that doesnt work try a different usb port, i dunno about mac but in windows it forces a driver reload
 
HAving a problem with this, drivers are up to date. I tried updating the ADB and that didnt change anything. I keep getting connecting to device. then occasionally it pops up with Daemon started. then just stops. Any suggestions?
 
that is strange that each phone would be different, but what ever works i guess :)
 
well yea i guess its not necessarily the phone, im not sure the exact factor that makes one thing work over the other but it varies, might be the computer, might be a bug linked to the internal clock for all we know so if you flashed between certain hours you gotta use a different mode lol
its a laughable assumption it really is but it is technically possible
 
Status
Not open for further replies.
Back
Top Bottom