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

Root [Closed] Permanent root

Status
Not open for further replies.
master odysues

master odysues

Android Enthusiast
Last edited:
Not quite there yet. Unless you are very knowledgeable in Java, you have a chance of bricking your phone as some already have.

Let the Devs work it out and compile their work into an .apk, otherwise, a lot of people will be rushing over to XDA not knowing what they are doing and ending up with a bricked device.

Patience...It's almost here.
 
PHP87 said:
Not quite there yet. Unless you are very knowledgeable in Java, you have a chance of bricking your phone as some already have.

Let the Devs work it out and compile their work into an .apk, otherwise, a lot of people will be rushing over to XDA not knowing what they are doing and ending up with a bricked device.

Patience...It's almost here.
Click to expand...

That's not completely true. All you have to do is:
1. Run KingRoot as many times as it takes to get root.
2. Install the nice TWRP apk package that Roar has provided
3. Boot to TWRP and install SuperUser

It's that easy. Now doing it that way won't give you system r/w privileges but if you didn't know how to use cmd to adb into the phone already, you probably won't need those privileges anyways.

I literally have no knowledge of Java.
 
Shady545 said:
That's not completely true. All you have to do is:
1. Run KingRoot as many times as it takes to get root.
2. Install the nice TWRP apk package that Roar has provided
3. Boot to TWRP and install SuperUser

It's that easy. Now doing it that way won't give you system r/w privileges but if you didn't know how to use cmd to adb into the phone already, you probably won't need those privileges anyways.

I literally have no knowledge of Java.
Click to expand...

Yet if you have read the entire thread, you'll see that people with Java experience have indeed bricked their phones.

Use caution. Personally, I can wait for a compiled .apk and I have Java experience but not on the level as these Devs.
 
PHP87 said:
Yet if you have read the entire thread, you'll see that people with Java experience have indeed bricked their phones.

Use caution. Personally, I can wait for a compiled .apk and I have Java experience but not on the level as these Devs.
Click to expand...

I did read the entire thread. I seen the people who bricked their phones and all of them had no idea what they were doing in cmd.

Again, you don't need any of that to achieve perm root. Run KingRoot apk then run TWRP apk. It's that simple.
 
I doubt the posters here are as technically adept as those at XDA and some of them have managed to brick their devices.

All I'm saying is "proceed with caution" - if you're not 100% comfortable with the rooting instructions, better off waiting for an .apk to be compiled.
 
Also, if you Root, do NOT install any updates from MPCS (or TMo) and before rooting, be sure to install the last update (B06) from MPCS

This Root is still unstable and can brick your device if you don't know exactly what you are doing, and there is no working recovery.

I strongly suggest that people be patient and wait until Root for the ZTE ZMax is perfected and hopefully, compiled into an .apk.

Be patient, the Devs at XDA are very close. ETA is end of month. Hang in there.

I would hate to see someone brick their ZMax due to lack of knowledge or impatience.

I really don't care if we get Root or not -- the ZMax has minimal bloatware, and with Nova Launcher I can customize the UI along with using various Icon packs.

I'm quite happy with my ZMax with Nova Launcher and "Sense Glass" Icons, along with HD Widgets.

2pyt546.jpg
 
Last edited:
Yeah I don't know what @PHP87 is talking about. In his last post he states " there is no working recovery." when I already had twrp installed long before that post. Shoot, roar had posted the recovery a full day before in this very forum.
 
Well I think that advising caution in favor of automation is never a bad idea.

And I think that everything sort of exploded here all at once - victory after victory, win after win in a really short time frame.

With huge thanks to the devs and their helpers, absolutely.

I also think that we're getting some confusion in thread names and whatnot, so we're maybe going to want to pull together and get a clear resources thread that helps sort this all out.
 
EarlyMon said:
Well I think that advising caution in favor of automation is never a bad idea.
Click to expand...
Delete this post and let someone who is wrote make a new post with all appropriate links
And I think that everything sort of exploded here all at once - victory after victory, win after win in a really short time frame.

With huge thanks to the devs and their helpers, absolutely.

I also think that we're getting some confusion in thread names and whatnot, so we're maybe going to want to pull together and get a clear resources thread that helps sort this all out.
Click to expand...
 
Last edited by a moderator:
master odysues said:
Delete this post and let someone who is wrote make a new post with all appropriate links
Click to expand...
Really?

It looks like you're already doing a good job of getting that going in the first post. (You probably edited it before I noticed.)

We can copy your first post to a new thread and lock this one - sort of a reset.

And rename the locked threads to provide more focus on the new ones.

Probably a good idea to sticky the three for good measure.

Yes? No?
 
EarlyMon said:
Really?

It looks like you're already doing a good job of getting that going in the first post. (You probably edited it before I noticed.)

We can copy your first post to a new thread and lock this one - sort of a reset.

And rename the locked threads to provide more focus on the new ones.

Probably a good idea to sticky the three for good measure.

Yes? No?
Click to expand...
Sounds good
 
Status
Not open for further replies.
Back
Top Bottom