Root re: re-rooting a ZTE Warp 4g n9510

[reble]

I had to dump my ZTE Warp 4g n9510 cell phone back to factory default because a hacker got into it (everything on the phone, games, contacts list and so on is backed up on on a windows cd-disk, before the hacker hit it. I learned that lesson the hard way). On the advice from Boost Mobile I did a "##786# then it asked for a MSL password. The phone is back to the way it was when I got it brand spanking new. I found the instructions for Framaroot at http://androidforums.com/threads/rooting-the-boostmobile-zte-warp-4g-lte-model-n9510.783379/ I followed the instructions and when I click on "Aragorn" or "Gandalf" I get the following error messages bellow.

Aragorn
Failed :-(...try another exploit if available (error #6)

Gandalf
Failed :-(...try another exploit if available (error #5)

What gives? I followed the instructions. What does the error numbers mean? I can't find any reference to error numbers 5 and 6. I can do a screen capture and past if need be. I must be doing something wrong or out of sequence. I could use some help please.


Steve

 

[reble]

I think I know why Framaroot isn't working. I can't get into "developer options" to turn on the USB debugging mode. There is a YouTube video How to enable usb debugging that says how to do this. The video says to tap 10 times on the build button, click on this Dropbox link screen capture.jpg you can see the build button. Now click on my screen capture.jpg from my phone screen. There is no build button there. Why? There supposed to be the same phone. Buy the way before the last system software update. The developer options button was available.

Update I figured out the "developer options" problem on my own without any help. In this phone the build button is marked "sw version". But getting the "developer options" showing has not solved the Framaroot problem.

Steve

 

[bcrichster]

Needs to be JB 4.1.2 - NOT KK 4.4.2 For Framaroot to function. And correct Framaroot version (1.4.1?) Cuz there are many available

 

[reble]

The phone simply says "android version 4.4.2. How do I change the android version back to the older version? All my problems started after the last auto system update. And how do I stop the auto system update? There is no way that I can get ride of the update icon on the top left of the phone (when it shows up) without installing it.

Steve

 

[bcrichster]

Honestly? I kept hitting Cancel when it tried to auto update on me (replaced my phone last WK due to my own mishap) (downloaded EVERYTHING needed first!) and immediately rooted w/Framaroot then used flashify to install the recovery then booted to recovery to install partition update and B12 Deodexed ROM - thanks to SuperR. Problem solved. If you are already on KK 4.4.2, SuperR posted a thread on how to achieve Root.. but Rooting while still on JB first is easiest...

 

[reble]

I looked at every thread that SuperR made and I still don't know which thread it is. Can you please tell me what thread it is?

Steve

SuperR posted a thread on how to achieve Root.. but Rooting while still on JB first is easiest...

 

[SuperR]

I looked at every thread that SuperR made and I still don't know which thread it is. Can you please tell me what thread it is?

Steve

http://androidforums.com/threads/ro...xed-and-unmodified.878797/page-9#post-6796902

 

[reble]

I read the instructions. I am not sure I understand about the part "Flash SuperSU.zip like a normal ROM on your device". The last time (and 1st time I rooted this phone) I ran the script file and the script file did everything. I didn't have to worry flashing any rom's. Do I put the supersu.zip file on the sd card in the phone?

Steve

http://androidforums.com/threads/ro...xed-and-unmodified.878797/page-9#post-6796902

 

[SuperR]

I read the instructions. I am not sure I understand about the part "Flash SuperSU.zip like a normal ROM on your device". The last time (and 1st time I rooted this phone) I ran the script file and the script file did everything. I didn't have to worry flashing any rom's. Do I put the supersu.zip file on the sd card in the phone?

Steve

Yes, as the second line of the instructions say, "Download SuperSU.zip and put it on the sdcard of your device"

 

[reble]

I booted up the Imgburn that I put on the cd. the os booted up fine. I opened the terminal prog and tried to type in "cd /home/tux/ZTE_Unbrick_Tool/partitions" and I got "dir couldn't be found". I did 1 dir at a time and got as far as the "ZTE_Unbrick_Tool" dir. The terminal prog will not see the dir's partitions and devices. I found and was able to get into both dir's by using the folder icon on the taskbar to look at the dir's. I am assuming this is a Linux os that was burned to the cd? I am an advanced level windows tech. I have to admit to the fact that I am not very good at Linux anything.

Steve

 

[SuperR]

I booted up the Imgburn that I put on the cd. the os booted up fine. I opened the terminal prog and tried to type in "cd /home/tux/ZTE_Unbrick_Tool/partitions" and I got "dir couldn't be found". I did 1 dir at a time and got as far as the "ZTE_Unbrick_Tool" dir. The terminal prog will not see the dir's partitions and devices. I found and was able to get into both dir's by using the folder icon on the taskbar to look at the dir's. I am assuming this is a Linux os that was burned to the cd? I am an advanced level windows tech. I have to admit to the fact that I am not very good at Linux anything.

Steve

Yes, it is a Linux distro. You can open a terminal in the /home/tux/ZTE_Unbrick_Tool/partitions directory from the file manager. I can't remember exactly how to do it, but you can find it in the menu of the file manager somewhere. Once the terminal is open in the directory, continue with the instructions to get rooted.

 

[reble]

In the zte_unbrick_tool dir the shell script "zteunbrick" doesn't work. I start the script and the little circle goes around then stops and nothing happens. Also shell script's "tester_unbrick" and "warplit-unbrick" do the same thing. The little circle goes around and nothing happens. In the Sakura terminal prog the sub dir's "partitions" and "devices" are not seen by the Sakura terminal. What gives"

Steve

 

[SuperR]

In the zte_unbrick_tool dir the shell script "zteunbrick" doesn't work. I start the script and the little circle goes around then stops and nothing happens. Also shell script's "tester_unbrick" and "warplit-unbrick" do the same thing. The little circle goes around and nothing happens. In the Sakura terminal prog the sub dir's "partitions" and "devices" are not seen by the Sakura terminal. What gives"

Steve

I am not sure why you are trying to run scripts, that is not in the root instructions I posted

If you open the file manager to the /home/tux/ZTE_Unbrick_Tool/partitions directory, there is a way to open terminal in that directory somewhere in the menu of the file manager. Once you get that accomplished, continue with the root instructions starting after "cd /home/tux/ZTE_Unbrick_Tool/partitions".

 

[reble]

When I get to the partitions directory. The only thing in that directory is "warplte_mcblkop16_recovery.img" and that does nothing. There is no terminal prog that I can see in that directory to open, unless it is marked as a hidden file. The rest I was just exploring since it wasn't working the way it is supposed to anyways.

I am not sure why you are trying to run scripts, that is not in the root instructions I posted

If you open the file manager to the /home/tux/ZTE_Unbrick_Tool/partitions directory, there is a way to open terminal in that directory somewhere in the menu of the file manager. Once you get that accomplished, continue with the root instructions starting after "cd /home/tux/ZTE_Unbrick_Tool/partitions".

 

[SuperR]

When I get to the partitions directory. The only thing in that directory is "warplte_mcblkop16_recovery.img" and that does nothing. There is no terminal prog that I can see in that directory to open, unless it is marked as a hidden file. The rest I was just exploring since it wasn't working the way it is supposed to anyways.

I have revised the instructions to make it easier. Please follow them exactly from the beginning.

http://androidforums.com/threads/ro...xed-and-unmodified.878797/page-9#post-6796902

 

[reble]

I followed the new instructions to the letter. The following (bellow) was on the screen for about a half hour solid, just sitting that way doing nothing. And nothing was happening on the phone. The phone was plugged in.
------
TUX@slitaz:~/ZTE_Unbrick_Tool/partitions$ fast boot warplte_mmcblk0p16_recovery.img
<waiting for device>
------
I don't know if this is connected with the problem. But in the sub directory "connect to PC" in my phone the following line is missing "charge only: charge your phone via usb". See attached picture

Steve

I have revised the instructions to make it easier. Please follow them exactly from the beginning.

http://androidforums.com/threads/ro...xed-and-unmodified.878797/page-9#post-6796902

 

[bcrichster]

Me too.. Huh. Have you tried all USB settings?

 

[reble]

In the phone?

Me too.. Huh. Have you tried all USB settings?

 

[bcrichster]

I meant to say that I too am without a charge only option in my Warp 4G and recommended trying the Root/unbrick tool in all the USB choices, because I had a similar issue in the Sequent N861 (no charge only option) and had to use "Connect as a Media Device" instead to work..

 

[SuperR]

I followed the new instructions to the letter. The following (bellow) was on the screen for about a half hour solid, just sitting that way doing nothing. And nothing was happening on the phone. The phone was plugged in.
------
TUX@slitaz:~/ZTE_Unbrick_Tool/partitions$ fast boot warplte_mmcblk0p16_recovery.img
<waiting for device>
------
I don't know if this is connected with the problem. But in the sub directory "connect to PC" in my phone the following line is missing "charge only: charge your phone via usb". See attached picture

Steve

the command should be

fastboot boot warplte_mmcblk0p16_recovery.img

 

[reble]

I did the command just like you had it bellow "fastboot boot warplte_mmcblk0p16_recovery.img" and it still just sits there with the "<waiting for device>" on the screen. The phone does not reboot into PhilZ recovery mode. See the screen snap shot I attached of my phones desktop. That's the way the phone sits. What I understand from your instructions after I type "fastboot boot warplte_mmcblk0p16_recovery.img" then hit enter this prog is suppose to reboot the phone into recovery mode. The phone just sits like u see in the picture bellow. What gives? I must have a setting set wrong somewere.

 

[SuperR]

You forget the command

adb reboot bootloader

Make sure you have usb debugging turned on before running that command.

Once the device has rebooted to the bootloader, then issue the fastboot command

 

[reble]

IT IS DONE The root checker app reports "status: rooted". Thanks SuperR for been patient with me.

Steve

 

[reble]

Ps, I always save all instructions files, like the one you gave me, for further use. I have a thick folder in my file box were I keep print outs.

Steve