[Tutorial] How to root the ZTE Warp Sequent. USE AT YOUR OWN RISK
Warning It's your phone if you break it blame yourself. I can't help you if this script bricks your phone. I have used and it worked great.
After a successful root it is recommended to Flash a Recovery and make a nandroid backup. BE CAREFUL. REALLY.
You will need the proper adb drivers for this to work .
How to root
1. Put your device in usb debug mode from developer options setting menu. (try different usb modes at least once, generally "charge only" mode is what is recommended but each person gets different resuslts)recommended by Junkie2100
2. Download DoomLord Script and extract it to a folder. DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su.zip
3. Connect your phone via usb and make sure you have adb drivers already installed.
4. Open the extracted folder run the runme.bat
5.Click any key to start the script the device will reboot be patient can take a couple minutes.
6. After script completes hit any key script should close you now have root.
(Helpful links for Clockwork mod and Rom)
Thanks to the Guys helping develop for the Warp Sequent
Junkie 2100 chrisjv3393 shinru2004 playfulgod superr if I missed you sorry
peasarecool found this method so many thanks and DoomLord is just awesome. I have used his work before thanks.
Didn't work for me either. Can you post a detailed how-to along with a link to the correct adb drivers? It would be greatly appreciated.
Without any details about what happened when you ran the script it is difficult to help. High percent chance that adb drivers are not installed or not installed correctly Youtube or xda developers have tutorials on installing adb drivers. I installed adb drivers about two years ao and don't remember the process. Also might help to put display timeout to thirty minutes and make sure allow install from unknown sources in security settings. Added adb drivers help link in the tutorial at the top of this page.
Last edited by yaggermr; October 6th, 2012 at 08:40 PM.
Is there something like Clockworkmod as a ROM manager and installer I can use? The stock ROM manager won't let me browse my entire directory. :-( If so, how do i go about installing it?
Is there something like Clockworkmod as a ROM manager and installer I can use? The stock ROM manager won't let me browse my entire directory. :-( If so, how do i go about installing it?
No currently there is no working cwm or a way to flash a rom or make a nandroid backup. I have tried a little to get cwm working but no results. There are currently no roms to flash.
1. Put your device in usb debug mode from developer options setting menu.
2. Download DoomLord Script and extract it to a folder. DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su.zip
3. Connect your phone via usb and make sure you have adb drivers already installed.
4. Open the extracted folder run the runme.bat
5.Click any key to start the script the device will reboot be patient can take a couple minutes.
6. After script completes hit any key script should close you now have root.
peasarecool found this method so many thanks and DoomLord is just awsome. I have used his work before thanks.
GOT ROOT.....Now I lost my stock recovery and looking for a simple cwm or twrp recovery
ok I rooted my phone and was messing around with other recoveries and lost my stock recovery. Now when I press power and down button all i get is a black screen with an android guy on it. I lost the 3e recovery that the phone came with. Any suggestions or instructions to get this back ///
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.
so i tried to run the script and all it says is "waiting for device"
i disconnected/connected the phone. restarted the phone, restarted my computer, unplug/plugged phone and now i dont know why it wont work. anybody have any suggestions on how to get it to identify my device?
i already have the correct adb drivers installed too
Last edited by benjiu3; November 11th, 2012 at 07:27 PM.
Reason: note
Is there a way to use this method in Linux? Maybe convert the bat to sh using the same adb commands? I started converting the file but I am terrified to try it for fear of ruining my brand new phone.
i cant get it to work this is what i get
Press any key to continue . . .
# CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
The system cannot find the path specified
--- creating temporary directory
The system cannot find the path specified
--- cleaning
The system cannot find the path specified
--- symlinking tmp directory
The system cannot find the path specified
The system cannot find the path specified
--- Rebooting
The system cannot find the path specified
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long tim
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable
The system cannot find the path specified
--- DEVICE FOUND
--- enabling emulator hack
The system cannot find the path specified
The system cannot find the path specified
--- Rebooting
The system cannot find the path specified
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long tim
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable
The system cannot find the path specified
--- DEVICE FOUND
--- pushing busybox
The system cannot find the path specified
--- correcting permissions
The system cannot find the path specified
--- remounting /system
The system cannot find the path specified
--- checking free space on /system
The system cannot find the path specified
The system cannot find the path specified
The system cannot find the path specified
--- copying busybox to /system/xbin/
The system cannot find the path specified
--- correcting ownership
The system cannot find the path specified
--- correcting permissions
The system cannot find the path specified
--- installing busybox
The system cannot find the path specified
The system cannot find the path specified
--- pushing SU binary
The system cannot find the path specified
--- correcting ownership
The system cannot find the path specified
--- correcting permissions
The system cannot find the path specified
--- correcting symlinks
The system cannot find the path specified
The system cannot find the path specified
--- pushing Superuser app
The system cannot find the path specified
--- cleaning
The system cannot find the path specified
The system cannot find the path specified
The system cannot find the path specified
--- rebooting
The system cannot find the path specified
ALL DONE!!!
Press any key to continue . . .
On another note i already had the sdk installed but i went ahead and used the sdk manager to uninstall sdk tools -platform tools and google usb drivers and reinstalled them but im still have this path issue.
Device(s): stock s3,zte warp rooted runing cm10;) special thanks to all the warps developers
Carrier: T-mobile
Thanks: 66
Thanked 56 Times in 48 Posts
Quote:
Originally Posted by benjiu3
so i tried to run the script and all it says is "waiting for device"
i disconnected/connected the phone. restarted the phone, restarted my computer, unplug/plugged phone and now i dont know why it wont work. anybody have any suggestions on how to get it to identify my device?
i already have the correct adb drivers installed too
I have converted the runme.bat to runme.sh for Linux users. I have NOT tested this file to achieve root for this phone as I am scared of bricking. Could someone take a look at it and let me know if it should work? I don't have access to a windows box, so I am kinda screwed if I can't get it up and running in Linux. Thanks :-)
edit: here is the new file. I am fairly sure it will work and will test later and report back
Last edited by superr; November 25th, 2012 at 01:11 PM.
Reason: file edit
i have resolved my first problem but now im getting this
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local/tmp/busybox, No such file or directory
--- pushing SU binary
cannot stat 'files\su': No such file or directory
--- correcting ownership
Unable to chmod /system/bin/su: Read-only file system
--- correcting permissions
Unable to chmod /system/bin/su: Read-only file system
--- correcting symlinks
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
--- pushing Superuser app
cannot stat 'files\Superuser.apk': No such file or directory
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Last edited by gamikzone; November 25th, 2012 at 01:37 AM.
thank god for you sir. i have been looking for a way to root my phone some time and this did it in seconds.... thank you so much for the help and i hope more good updates come along, once again thanks for the help... worked for me and im happy
The Linux script does NOT work for me as is. It gives me read-only filesystem errors and will not push the files.
However, I got the phone rooted using the method in this post on a 32-bit Windows 7 box Thank you very much for the wonderful tutorial and download !
Observations: The Superuser.apk is an outdated version (according to Play Store) and I was notified of an update. I proceeded with the update and everything seemed to get slow. My wifi connection went from 8Mbps to 2, opening apps took 10 seconds, games were choppy, etc. Things seem back to normal after an uninstall and reboot. Anyone else have this happen?
Last edited by superr; November 25th, 2012 at 05:39 PM.
Observations: The Superuser.apk is an outdated version (according to Play Store) and I was notified of an update. I proceeded with the update and everything seemed to get slow. My wifi connection went from 8Mbps to 2, opening apps took 10 seconds, games were choppy, etc. Things seem back to normal after an uninstall and reboot. Anyone else have this happen?
After re-installing again it seems to be ok. I also updated the su binary through Superuser app with no problems so far
its still not detecting my device. i installed and reinstalled the adb drivers and still nothing. can someone make like a youtube video showing the entire process lol i need help
it still says "waiting for device" i even reinstalled the adb drivers but still nothing. can someone please help me
Is your phone in Media Transfer mode? Mine only connects to adb in this mode. Hope it helps
edit: also make sure you have installed the phone drivers. I used the ones on the phone by choosing PC Software mode, installed the drivers, changed to Media Transfer mode, adb connected
Last edited by superr; November 25th, 2012 at 09:04 PM.
Is your phone in Media Transfer mode? Mine only connects to adb in this mode. Hope it helps
edit: also make sure you have installed the phone drivers. I used the ones on the phone by choosing PC Software mode, installed the drivers, changed to Media Transfer mode, adb connected
i did exactly what you said, and it still says waiting for device.
i found out what the problem was. i didnt restart my pc for all the changes to take effect. now im rooted yay!! but now what. how do i remove all my bloatware
i found out what the problem was. i didnt restart my pc for all the changes to take effect. now im rooted yay!! but now what. how do i remove all my bloatware
I think we wait for deodex instructions to remove bloatware