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

Root ZTE Zmax Pro Official Root Discussion

Status
Not open for further replies.
TheOddTaco said:
u cant move it because the /system directory is read-only and you need to have the su binary to be already installed to change it from read-only to read-write so you can move the files to the phone's root directory.
Click to expand...

unless someone finds a way/script to somehow let us move files in the root directory
 
I posted a possibility when we were tinkering with the OTA.. the tool extract the system.dat you place su file where needed. This is the part I don't think has been tried. For the final step in the video when he told the tool to repack the system.dat he specified the file size to match the original cause it gives the option.. I think he match the size to trick the stock recovery into thinking it's flashing the untampered OTA.. when our devs tampered with the OTA I think that detail got overlooked and the mod OTA fail.. I can try to relocate the tool if our Linux rooters want to try and use it to get the su binary to where it need to go.. the catch is it's a Windows tool.
 
lambo352 said:
I posted a possibility when we were tinkering with the OTA.. the tool extract the system.dat you place su file where needed. This is the part I don't think has been tried. For the final step in the video when he told the tool to repack the system.dat he specified the file size to match the original cause it gives the option.. I think he match the size to trick the stock recovery into thinking it's flashing the untampered OTA.. when our devs tampered with the OTA I think that detail got overlooked and the mod OTA fail.. I can try to relocate the tool if our Linux rooters want to try and use it to get the su binary to where it need to go.. the catch is it's a Windows tool.
Click to expand...
This is a wonderful theory. I remember on the fierce xl using a similar tool to try and trick root in there. We could never get it the exact same size though. Eventually we gave up because kingroot figured it out.
 
iancc86 said:
This is a wonderful theory. I remember on the fierce xl using a similar tool to try and trick root in there. We could never get it the exact same size though. Eventually we gave up because kingroot figured it out.
Click to expand...
Yes the tool I'm referring to ask to enter the size in bytes to make the size a perfect match. In the video the guy open up the properties of the original, it read some 9 digit number like ***,***,***bytes. He entered the number exactly the same, double check the size before putting the new system.dat in the OTA and it flashed via stock recovery..
 
lambo352 said:
iancc86This is a wonderful theory. I remember on the fierce xl using a similar tool to try and trick root in there. We could never get it the exact same size though. Eventually we gave up because kingroot figured it out.
Click to expand...
Yes the tool I'm referring to ask to enter the size in bytes to make the size a perfect match. In the video the guy open up the properties of the original, it read some 9 digit number like ***,***,***bytes. He entered the number exactly the same, double check the size before putting the new system.dat in the OTA and it flashed via stock recovery..
Click to expand...

Anyone willing to try?
 
lambo352 said:
Yes the tool I'm referring to ask to enter the size in bytes to make the size a perfect match. In the video the guy open up the properties of the original, it read some 9 digit number like ***,***,***bytes. He entered the number exactly the same, double check the size before putting the new system.dat in the OTA and it flashed via stock recovery..
Click to expand...
I can't find said tool... I can create it and post it if you can help me find the tool.
 
Yes.. brb.. I have to go through a lengthy video history on YouTube to find it.. it'll take just as long to find where in the thread I posted it..
 
I just attempted the XDA universal root method. File pushed normally, but on execute it failed at mmap(). Method is a failure, and later on a developer called him out on it. If anyone has any methods, I have 2 ZTE ZMAX PRO (z981)'s available to toy with. I'm perfectly fine bricking my spare one.
 
SapphireEx said:
I just attempted the XDA universal root method. File pushed normally, but on execute it failed at mmap(). Method is a failure, and later on a developer called him out on it. If anyone has any methods, I have 2 ZTE ZMAX PRO (z981)'s available to toy with. I'm perfectly fine bricking my spare one.
Click to expand...
You tried the above method in the video?
 
Just to give a KingRoot request update. But other than that. Is there anything I can do. I have been updating the mixer file and other configurations for better performance and volume but unable to currently test
 

Attachments

  • Screenshot_20170301-100019.png
    Screenshot_20170301-100019.png
    103.4 KB · Views: 220
As soon as my hours pick back up at work, I will probably be buying a new phone myself, at which point I will not be concerned about bricking either.
 
Status
Not open for further replies.
Back
Top Bottom