• 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 modified the last ota update .up file to flash the twrp recovery , send it to a friend to test , will post here if it worked.
U the man Messi.. I've been at it all night and got nowhere.. i was mostly trying to extract the .IMG.p to see how it differs from .IMG..
 
It is a fake root, it doesn't give me any root access. I tried supersume and it doesn't work.
 

Attachments

  • Screenshot_20161201-161812.png
    Screenshot_20161201-161812.png
    83.9 KB · Views: 105
It is a fake root, it doesn't give me any root access. I tried supersume and it doesn't work.

If it is working it's being undone instantly. I think it's just a bug in KingRoot. My phone has never reset, and I can't use any root privileges through a terminal.
 
I think that just gives it control of the lock screen. That might be a different permission though. It will take over your phone if you let it do everything. I tried the PC version once and it really did a number on it. Had to do a reset to get rid of all of the crap it installed.
 
Awesome! Looks like progress! Just kinda curious, is everyone attempting to root disabling write protection before during or after reboots? Iv taken the update, I haven't noticed any slowing, but the phone did randomly reboot and bootlooped endlessly about a day after taking it, no change in apps or use, had to factory wipe/reset to fix. But no problems otherwise. Also this devise is shooting up through kingroots root requests faster than any other device iv ever had.
 
Awesome! Looks like progress! Just kinda curious, is everyone attempting to root disabling write protection before during or after reboots? Iv taken the update, I haven't noticed any slowing, but the phone did randomly reboot and bootlooped endlessly about a day after taking it, no change in apps or use, had to factory wipe/reset to fix. But no problems otherwise. Also this devise is shooting up through kingroots root requests faster than any other device iv ever had.

I haven't tried it. That's something new to try. KingRoot hasn't actually forced a reboot yet when it reached 100% for me. I don't think they have a real solution for it yet.

I had to do a reset after the update too. It started acting weird the morning after I installed it.
 
Am I the only on with this KingRoot notified me of root auth error. Then I tried "fix root option" I clicked it. Said "no root method available" I checked here and noticed someone mentioned a service KingRoot has. I thought it would stop KingRoot charging screen. But here's what I got.
Screenshot_20161202-040001.png

What is that root service!?
Edit:added another question.
 
We got package signature verification failed error on both updated and not updated zmax
Can we extract SuperSU zip and manually place files in their appropriate location in the OTA? Is it possible we can get away with flashing via SD card and everything work the same but with root?
 
Can we extract SuperSU zip and manually place files in their appropriate location in the OTA? Is it possible we can get away with flashing via SD card and everything work the same but with root?


That's what I tried, but it didn't pass verification when I tried to flash it. Something else in the file needs to be tweaked to make it look like the original. I just don't know what. That's assuming that any file can pass the verification.

Did anyone install the update through recovery?
 
I've seen for the Axon 7 in order to begin the root process you need to use "adb reboot edl" can someone see if this works on the ZMAX
 
Last edited by a moderator:
Can we extract SuperSU zip and manually place files in their appropriate location in the OTA? Is it possible we can get away with flashing via SD card and everything work the same but with root?
Looks like every file in this ota package is signed or only the update packagd I'm not sure, once u modify any file that breaks it's sign and system refuse to flash it , unfortunately this may also mean that the bootloader is locked as i faced this case on a samsung verizon note 5 before where every file was signed....
 
I'm pretty sure that every OTA sent out for Android devices are signed...there are SHA1 digests for each file inside the OTA fileset as well as the signing certificate, all contained in the META-INF folder structure.

The signing serves two purposes:

1. Allows for verification that the file actually came from the purported "official" source

2. Provides a way to guarantee that the file (.zip) and the individual files contained therein, are whole an uncorrupted

Devices with unlocked bootloaders also do have signed OTA files--its just that an unlocked bootloader will not enforce the signature checking when trying to flash/boot/install a file (amongst other things)--i.e., caveat emptor for those that unlock their device.
 
I got this out of the blue! I was not even running KingRoot. Im at work and suddenly get a notification with this . Any input?
 

Attachments

  • Screenshot_20161202-152801.png
    Screenshot_20161202-152801.png
    129.5 KB · Views: 152
Status
Not open for further replies.
Back
Top Bottom