• 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.
So having an unlocked bootloader would be of zero assistance in trying to gain root? I thought that would give an additional angle of attack, like from trying to flash su through a custom recovery or something.
 
I wonder if we can use dfu mode somehow... or make a program that is basically a tethered custom recovery, I have seen and used this kind of program before and I will try to contact the creator or remember how it worked and see if it can be used for our device
 
UndacoverBrother said:
KingRoot update
13,793 ppl and now says accelerating research..
Crossing fingers
KingRoot 4.1.0.25.apk
Click to expand...
That is an outdated unsupported version of kingroot. I just opened up kingroot 4.9.5 and here is what it says.
8c210aec01e62c3939110b4372735fc4.jpg
If I know anything about the kingroot devs they aren't going to look into finding an exploit for this phone until the number of requests is in the thousands.
e1e22efc68c02d42fe7e2206c0033a05.jpg
 
Last edited:
Yeah it seems they might be starting to pay some attention to the zmax pro. When I first got the phone kingroot would attempt to root. Then after a few days it stopped working altogether and there was just a request research button. Now after 4 or 5 hundred requests it is trying again. Even if it still doesn't get all the way to 100% it is a step in the right direction.
 
I don't think so and I.honestly would but im far too scared to do so. i cant afford another device any time soon
 
I hope to be a help to the android community regarding this device. i am wondering if the Bootloader is unlocked as the ZMAXcame unlocked. could the same files be used to gain root access if they are modified? any thoughts?
 
Dre Antonio said:
I hope to be a help to the android community regarding this device. i am wondering if the Bootloader is unlocked as the ZMAXcame unlocked. could the same files be used to gain root access if they are modified? any thoughts?
Click to expand...
No because the zmax was kitkat, we have marshmallow and different hardware
 
Sorry guys I'm kinda new to this whole rooting thing, but you guys are talking about unlocking the bootloader when in developer settings it says OEM bootloader - allows the bootloader to be unlocked. Is that not the same thing?
 
yes it is the same thing. the issue is the files needed to be changed in order to gain root access.
--- does ZTE have devs similar to LG (like the lg STYLO) who know how to use DLL and mods to push root through ADB terminal??
 
spades said:
How much longer before someone resurrects GameTheory ?
Click to expand...
I can almost guarantee that he will be working on the new stylo. He tends to heavily favor lg devices

I should rephrase. I can't make any guarantee of what device he will work on next or when but it is likely that the next device will be an lg device. If you look on his website he has worked on 8 devices. Seven of them were lg and one was huawei.
 
Last edited:
I did the reboot disemcwwp command then was able to change the screen density through adb shell, set density. Doesn't work for long though before the screen starts flashing the MetroPCS logo and I have to plug back in to the computer and set the screen density back to 480.
 
Jimmy Dixx said:
I did the reboot disemcwwp command then was able to change the screen density through adb shell, set density. Doesn't work for long though before the screen starts flashing the MetroPCS logo and I have to plug back in to the computer and set the screen density back to 480.
Click to expand...
That's just because it couldn't display the dpi. Did you try like 330?
 
Jimmy Dixx said:
I did the reboot disemcwwp command then was able to change the screen density through adb shell, set density. Doesn't work for long though before the screen starts flashing the MetroPCS logo and I have to plug back in to the computer and set the screen density back to 480.
Click to expand...
The reboot disemmcwp command doesn't affect your ability to change the DPI.

IF the reboot disemmcwp command works (and that's a big IF) what it actually does is allow you to remount the system partition as read/write (r/w) instead of being read only (ro). This doesn't even come into play until you root the phone.

Changing the DPI via adb commands modifies a file that is generated on the userdata partition (the partition where all your downloaded apps and your internal storage are located) and doesn't require root or system rw.
 
Status
Not open for further replies.
Back
Top Bottom