• 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.
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
 
Upvote 0
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 . . .
 
  • Like
Reactions: BigRed_
Upvote 0
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
Try reinstalling device drivers
 
Upvote 0
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
 

Attachments

  • runme.sh.zip
    1.3 KB · Views: 172
Upvote 0
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 . . .
 
Upvote 0
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?
 
Upvote 0
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
 
Upvote 0
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
 
Upvote 0
Upvote 0
Status
Not open for further replies.

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones