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

Root ZTE ZMAX Pro (Z981) root discussion

Status
Not open for further replies.
I'm sorry I didn't post the whole chat. I have no reason to give false hopes.
 

Attachments

  • Screenshot_20160924-000810.png
    Screenshot_20160924-000810.png
    181.2 KB · Views: 232
anubis2048 said:
Only works on Android 5.0.1 and below, it bricks 5.1 and up. Be careful before posting stuff like this, you could really get people into trouble.
Click to expand...
i gave it a try.. I can't resist. Didn't work as you said. It worked up until the final step. Final step hangs..
 
I've taken to uninstalling KR between root attempts. After I updated to the latest release of the current version, it started hitting me with extra ads and kept trying to take over my lock screen, same kind of BS app behaviors that make me want root in the first place.
 
5318008 said:
I've taken to uninstalling KR between root attempts. After I updated to the latest release of the current version, it started hitting me with extra ads and kept trying to take over my lock screen, same kind of BS app behaviors that make me want root in the first place.
Click to expand...
Same! It even bypasses the fingerprint lock and allows users to swipe up to unlock the screen! Total horse shit!
 
For those of you who are adamant about using KingRoot:

Be advised.... I've used it on quite a few phones. With every update they release, they not only get closer, if not successful with achieving root, but they also get further ahead of blocking the method that uses a script to remove it before it can remove the root access. If you don't go through it thoroughly and remove it in one shot, KR moves it's files to multiple locations throughout your system folder.

The last time I used it, the script didn't work, using the same method as I've always used. I had to go in spend hours cleaning up the mess it left. It buries files and apparently it leaves backup files in case you do find them, changing permissions and blocking you. You grant KR these permissions when you allow it to be installed, so just be cautious. It's a nightmare scraping these files out of your device...

My advice would be, if the script for running the MRW folder contents fails, uninstall KingRoot immediately, and try reinstalling it, run script again. It picked up on me trying to run that script three times, and then kindly warned me that it had relocated itself in my system.

Take it, dismiss it, but you're also potentially opening up a guided map to your personal information and BRICKING. I would also strongly advise running king(o)root with a freshly wiped system and not signed in.

Oh and final EDIT:

If KingRoot fails, power cycle your phone. Some instances, doing so will allow it to reach the same fail (70% etc) instead of reaching only 10% next attempt.... Don't think it really does anything, just wanted to point it out. Good luck....

~spec
 
Last edited:
Proud new owner of the ZMAX Pro. I went 2 full years on the ZTE Boost Max (Iconic) so I'm happy with ZTE just not happy with development.

SuperR was one of the main devs that got us root on KitKat when we received the update. If he is still in the forums I would beg him to help us.

I'm not down for KingRoot at all. I had all kinds of weird files installed. Files everywhere but this was back in 4.1 days. I'm new to this phone so I don't have much input right now
 
MustangLife said:
Proud new owner of the ZMAX Pro. I went 2 full years on the ZTE Boost Max (Iconic) so I'm happy with ZTE just not happy with development.

SuperR was one of the main devs that got us root on KitKat when we received the update. If he is still in the forums I would beg him to help us.

I'm not down for KingRoot at all. I had all kinds of weird files installed. Files everywhere but this was back in 4.1 days. I'm new to this phone so I don't have much input right now
Click to expand...
@SuperR is now currently neck deep in the Biggest & Baddest Android Kitchen ever created.. It goes beyond anything dsixda or ArchiKitchen could do, by far. Check it out here:
The SuperR Kitchen! http://forum.xda-developers.com/showthread.php?p=62845957

He can't help much right now for a few reasons:
- need Root first to do anything anyways.
- bootloader & recoveries are now signed..
- he's SuperR busy! [emoji41]
 
Spec2nirvash said:
For those of you who are adamant about using KingRoot:

Be advised.... I've used it on quite a few phones. With every update they release, they not only get closer, if not successful with achieving root, but they also get further ahead of blocking the method that uses a script to remove it before it can remove the root access. If you don't go through it thoroughly and remove it in one shot, KR moves it's files to multiple locations throughout your system folder.

The last time I used it, the script didn't work, using the same method as I've always used. I had to go in spend hours cleaning up the mess it left. It buries files and apparently it leaves backup files in case you do find them, changing permissions and blocking you. You grant KR these permissions when you allow it to be installed, so just be cautious. It's a nightmare scraping these files out of your device...

My advice would be, if the script for running the MRW folder contents fails, uninstall KingRoot immediately, and try reinstalling it, run script again. It picked up on me trying to run that script three times, and then kindly warned me that it had relocated itself in my system.

Take it, dismiss it, but you're also potentially opening up a guided map to your personal information and BRICKING. I would also strongly advise running king(o)root with a freshly wiped system and not signed in.

Oh and final EDIT:

If KingRoot fails, power cycle your phone. Some instances, doing so will allow it to reach the same fail (70% etc) instead of reaching only 10% next attempt.... Don't think it really does anything, just wanted to point it out. Good luck....

~spec
Click to expand...

That's why ZTE system write protection can sometimes be a good thing. Hopefully it'll only be temp root when it does come along so we can dump the partition images and make a 100% factory stock ROM.
 
Vyrus69 said:
When it comes to Kingroot, with the old Zmax you had to overload the RAM on the phone while running it, so try and run multiple apps at the same time, open many windows of chrome as well and then try to run kingroot.

The ZTE phones have an exploit that it moves its RAM use from system apps to user apps if there isn't enough memory, when you do that is when Kingroot is able to get in the back door. IF that works, then we would be able to create a TWRP and have root.
Click to expand...

I achieved the overloading by running Antutu benchmark while trying Kingroot on my old zmax. It was much easier than the multiple chrome tabs way.
 
Good idea. I am about to try doin multi tabs in Firefox all running video, antutu, and YouTube, and KingRoot here myself.
 
Meh, it won't let me attempt root right now. Not sure exactly what the formula is for when it lets you, it seems kind of random. Maybe I'll try uninstalling and reinstalling.
 
Jimmy Dixx said:
Meh, it won't let me attempt root right now. Not sure exactly what the formula is for when it lets you, it seems kind of random. Maybe I'll try uninstalling and reinstalling.
Click to expand...

Now it won't let me try root so they must have something new up their sleeves. Hopefully next time it says try root we atleast get temp root.. I try at least 3 times a day. I also clear kr data in app info prior to trying root. If I don't it jumps straight to request queue.
 
Jimmy Dixx said:
Meh, it won't let me attempt root right now. Not sure exactly what the formula is for when it lets you, it seems kind of random. Maybe I'll try uninstalling and reinstalling.
Click to expand...

I think they come up with new methods and then let people try it and after so many fails, they disable it so you can't use it anymore.
It probably reports every failure so after like 300 failures in a row, they would automatically pull it.(Just thinking out loud)
 
anubis2048 said:
I think they come up with new methods and then let people try it and after so many fails, they disable it so you can't use it anymore.
It probably reports every failure so after like 300 failures in a row, they would automatically pull it.(Just thinking out loud)
Click to expand...
That seems like the logical explanation. I remember when the original ZMAX first got rooted it would sometimes require dozens of times trying kingroot before it would eventually work. They allow each exploit they use to be tried many times before they move on to find another angle of attack.
 
bcrichster said:
@SuperR is now currently neck deep in the Biggest & Baddest Android Kitchen ever created.. It goes beyond anything dsixda or ArchiKitchen could do, by far. Check it out here:
The SuperR Kitchen! http://forum.xda-developers.com/showthread.php?p=62845957

He can't help much right now for a few reasons:
- need Root first to do anything anyways.
- bootloader & recoveries are now signed..
- he's SuperR busy! [emoji41]
Click to expand...

That is awesome. I used to speak with him from time to time about a year and half ago. Great guy and his android intelligence is that of no other. It amazes me, glad hes on to bigger and better things
 
Status
Not open for further replies.
Back
Top Bottom