• 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.
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- symlinking tmp directory
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- enabling emulator hack
/system/bin/sh: can't create /data/local.prop: Permission denied
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
failed to copy 'files\busybox' to '/data/local/tmp/./busybox': Permission denied

--- correcting permissions
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
/system/bin/sh: /data/local/tmp/busybox: not found
--- checking free space on /system
failed to copy 'files\makespace' to '/data/local/tmp/./makespace': Permission de
nied
Unable to chmod /data/local/tmp/makespace: No such file or directory
/system/bin/sh: ./data/local/tmp/makespace: not found
--- copying busybox to /system/xbin/
/data/local/tmp/busybox: cannot open for read: No such file or directory
--- correcting ownership
Unable to chown /system/xbin/busybox: No such file or directory
--- 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
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chown /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for /data/local.prop, No such file or directory
--- rebooting
ALL DONE!!!
Press any key to continue . . .


I have tried putting it in charge only, media, and pc software, disabled and re-enabled debugging mode over and over. Keep getting the same errors. HELP PLEASE!!!!

EDIT: I have also made sure abd is installed, trying factory reset on my phone now to see if that does anything.
 
If you are on b11, this script won't work to root your phone anymore. If you are on b09, try running the following command in cmd.exe
Code: 
adb remount
If you don't get an error after typing that and pressing enter, run the script again
 
teKnoh said:
Dang, I'm on b11 :\ Any ideas on when a new script will be out? Hate not having a rooted phone
Click to expand...
download junkies aio tool, use the fastboot method to flash cwm and then flash the root.zip. There are instructions all over this forum if you need more help than that
 
SuperR said:
download junkies aio tool, use the fastboot method to flash cwm and then flash the root.zip. There are instructions all over this forum if you need more help than that
Click to expand...

Alright thank you very much for your help, the world needs more people like you :)
 
sigh
I've been trying everything and still no root.
I had a ZTE warp sequent rooted previously with no problem using junkie's AIO Root tool:
http://androidforums.com/warp-seque...ot-unroot-recovery-installer-gui-edition.html
on that phone it only took a couple minutes.

Now on this new phone it appears that whenever I try to flash CWM recovery it hangs on a boot loop, I also tried flashing CWM zip through stock recovery without success.
Using Junkie's AIO tool I manage to get the "Your phone should be rooted" comment box, but no root.
Im thinking theres got to be something with the firmware that is not allowing CWM to install.
Any hints?



***EDIT***
I got b11 :(
 
You need to flash CWM with the fastboot method and the root process on the AIO is no longer working on the new B11 update so you need to flash the root zip after getting CWM on your phone
 
its not working
I tried earlier and even left the phone plugged in for 15 min, the whole time the screen was hanged on the green android guy with the red LED on (meaning there is an error or boot loop I guess).
Are there any other options at this point?
 
seediqbale said:
its not working
I tried earlier and even left the phone plugged in for 15 min, the whole time the screen was hanged on the green android guy with the red LED on (meaning there is an error or boot loop I guess).
Are there any other options at this point?
Click to expand...


It didnt work because you dont have fastboot drivers installed properly. theres ways to get it working if you read around the forums or you can try this [TOOL] Warp2 CWM Recovery Flasher
 
seediqbale said:
Drivers and adb all in order.
I ran the fastboot installer for cwm, and got the succesfully installed message. But when I go into recovery mode the stock recovery is still in place.
Im at the point of giving up...I guess I'll take a break and try again later.

Thanks for the help.
Click to expand...

[TOOL] Warp2 CWM Recovery Flasher << try that its a live linux that will do the work for you basicly. all you need is a spare usb drive to make it bootable. read the instructions and you should be up and running in no time
 
SuperR said:
You don't even need a usb drive, although i prefer them. You can burn it to a cd and boot to that instead ;)
Click to expand...

Yep I did that, burned the CD and ran the whole thing.
I must be doing something wrong, 'cause I cant get CWM recovery on it.
I suck :(
 
seediqbale said:
Yep I did that, burned the CD and ran the whole thing.
I must be doing something wrong, 'cause I cant get CWM recovery on it.
I suck :(
Click to expand...

it may be that you are using usb 1.1 or 3.0 ports, which may not work with fastboot. Try the cd on a different computer. May sound strange but it will likely work.
 
a gazzilion people trying to run doomlord, look at the date of the original post ?? this will not work on JB, and best of luck with the recovery flasher, some folks get lucky with it and fastboot, most of us, not so much. its a waiting game.
 
Freefromit2 said:
a gazzilion people trying to run doomlord, look at the date of the original post ?? this will not work on JB, and best of luck with the recovery flasher, some folks get lucky with it and fastboot, most of us, not so much. its a waiting game.
Click to expand...

Its not a waiting game. There are 2 diff methods for JB to get CWM on the phone and we have a root.zip file that can be flashed from cwm (once its installed) so you can have root again. Just take the time to read the posts in this and many other threads and you can do it
 
Ok. First off which version of my tool were you using? Only the java and c++ versions have fastboot capability. And you have to go straight back into cwm after installing it, then apon hitting reboot select yes when it asks to disable recovery flashing. When the stock rom boots it deletes cwm unless you disable that feature in cwm
 
i a trying to root my warp sequent and it is not working. it is updates to jb 4.1.2 i tried doomlords script and al i get is this::

CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- symlinking tmp directory
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- enabling emulator hack
/system/bin/sh: can't create /data/local.prop: Permission denied
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
failed to copy 'files\busybox' to '/data/local/tmp/./busybox': Permission denied

--- correcting permissions
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
/system/bin/sh: /data/local/tmp/busybox: not found
--- checking free space on /system
failed to copy 'files\makespace' to '/data/local/tmp/./makespace': Permission de
nied
Unable to chmod /data/local/tmp/makespace: No such file or directory
/system/bin/sh: ./data/local/tmp/makespace: not found
--- copying busybox to /system/xbin/
/data/local/tmp/busybox: cannot open for read: No such file or directory
--- correcting ownership
Unable to chown /system/xbin/busybox: No such file or directory
--- 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
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chown /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for /data/local.prop, No such file or directory
--- rebooting
ALL DONE!!!
Press any key to continue . . .
 
This root method does not work for 4.1.2 b11 update. You will need to install cwm and flash root.zip or install cwm and flash a rooted rom. Instructions for both are posted many times on here.
 
SuperR said:
This root method does not work for 4.1.2 b11 update. You will need to install cwm and flash root.zip or install cwm and flash a rooted rom. Instructions for both are posted many times on here.
Click to expand...


ok is that easy to do?? can u reference me a post with good instructions. bricked wifes phone before and this is her phone and i dont want to screw up another one for her :( also if i do successfully root it, what is the easiest way to backup all apps and data for the apps so she dont lose progress in then when i try to flash a new rom on it??
 
videokid14 said:
ok is that easy to do?? can u reference me a post with good instructions. bricked wifes phone before and this is her phone and i dont want to screw up another one for her :( also if i do successfully root it, what is the easiest way to backup all apps and data for the apps so she dont lose progress in then when i try to flash a new rom on it??
Click to expand...

You can use junkies aio tool or my warp2 cwm recovery installer to get cwm.

If you choose junkies tool, use fastboot method. You need fastboot drivers setup for this and you are on your own since i don't use windows.

If you choose warp2 cwm flasher, you will need a blank cd or an empty usb flash drive.
 
Status
Not open for further replies.
Back
Top Bottom