• 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.
Adb reboot disemmcwp
Then kingroot should root your device easily..


It does not work. I would've rooted ages ago. I just tried it again 'cause why not. King root doesn't root it. I have never gotten temp root on this phone using kingroot and I have on other zte devices before disabling right protection. Etc
 
<br> It does not work. I would've rooted ages ago. I just tried it again 'cause why not. King root doesn't root it. I have never gotten temp root on this phone using kingroot and I have on other zte devices before disabling right protection. Etc
Could be that their servers are down. From what others are reporting it had tried before but not today.
Can you post a pic that includes your build number please.
 
Could be that their servers are down. From what others are reporting it had tried before but not today.
Can you post a pic that includes your build number please.

Once they update the model as non rootable on newer apks then it skips root and goes to request root.

You have to download an older kingroot to test it or try srsroot or even any one click root that has been updated.

They all usually hold the same exploits but kingroot has a apk version which is easier.
 
Once they update the model as non rootable on newer apks then it skips root and goes to request root.

<br>

<br> You have to download an older kingroot to test it or try srsroot or even any one click root that has been updated.

<br>

<br> They all usually hold the same exploits but kingroot has a apk version which is easier.
SRS is useless. Many times they have claimed that they rooted a certain phone model, but on 3 different occasions with 3 separate phones/tablets, it only rebooted the phone. King/Kingo are the best options at the moment as at least they are proven to root certain phones.
 
Once they update the model as non rootable on newer apks then it skips root and goes to request root.

<br>

<br> You have to download an older kingroot to test it or try srsroot or even any one click root that has been updated.

<br>

<br> They all usually hold the same exploits but kingroot has a apk version which is easier.
Never had to use them. But I do remember reading that in some cases the PC versions of KingRoot & others like it might be better or more robust ?
 
Never had to use them. But I do remember reading that in some cases the PC versions of KingRoot & others like it might be better or more robust ?
Ehhhhh. The only thing the desktop versions of these apps have over the actual apps is ADB access. Even then, it's not much more useful.
 
SRS is useless. Many times they have claimed that they rooted a certain phone model, but on 3 different occasions with 3 separate phones/tablets, it only rebooted the phone. King/Kingo are the best options at the moment as at least they are proven to root certain phones.
Srsroot actually piggybacks kingroot.. they use the kingroot apk api to connect to there database to use the exploits available via kingroot.

Ever notice purity and etc install after srs
 
Ehhhhh. The only thing the desktop versions of these apps have over the actual apps is ADB access. Even then, it's not much more useful.
It was what was recommended on a few specific instances on FireTV's.
It's great we know of so many possible vulnerabilities. But have yet to find a workable implementation.
 
Srsroot actually piggybacks kingroot.. they use the kingroot apk api to connect to there database to use the exploits available via kingroot.

<br>

<br> Ever notice purity and etc install after srs
Never actually seen that. All SRS does is reboot the device afterwards. Nothing gets installed.
 
Bigcountry should know how to extract the kernel and mod it. Then flash it over as a Dev signed update package. Maybe get some keys tonight!
You need the keys to sign a package. Unless I missed something, we don't have ZTE keys, and the kernel has already been released publically.
 
hey everyone i have been a bit busy i need someone to find me the recovery.img twrp made for us or if someone can make a new one I was able to load phone and pair in QSPT i want to try to flash recovery through there.
Any luck?
 
Testing my AVC exploit on some VMs now. Right now I am solely testing for module crash, not injection. The VMs:

Android 7.1 ST
Ryzen 1700 single thread @4ghz
8gb of DDR4 RAM
128mb of video ram
Stock android, rooted by default

Android 7.1 MT
Ryzen 1700 8 thread @4ghz
8gb of DDR4 RAM
128mb of video ram

Android 7.1 MT
Ryzen 1700 16 thread @4ghz
16gb of DDR4 RAM
128mb of video ram

Android 6.0.1 ST
Ryzen 1700 single thread @4ghz
8gb of DDR4 RAM
128mb of video ram

Android 6.0.1 MT
Ryzen 1700 8 thread @4ghz
8gb of DDR4 RAM
128mb of video ram

Android 6.0.1 MT
Ryzen 1700 16 thread @4ghz
16gb of DDR4 RAM
128mb of video ram

Once I get a reliable crash on ST mode, I will move up to crash MT at 8, and MT at 16.
RAM is acting strange, and only allocating 3.7gb, even though it's a 64 bit kernel, with a 64 bit host, and AMD-VI/ IOMMU enabled. (Yes, I know it says x86, but the kernel is confirmed x86-64 with LAA enabled)
 

Attachments

  • VirtualBox_Android 7.1 RC1_07_09_2017_18_58_44.png
    VirtualBox_Android 7.1 RC1_07_09_2017_18_58_44.png
    52.2 KB · Views: 215
So when we test exploits and it turns out that the 'exploit' only works on a certain FW version like let's say FW B20 would we have to find a way to downgrade our firmware if we are on FW B21.
That won't be much of an issue I think. Once any version gets rooted, OTA survival should be rather easy, then we will have root on that particular version, and can begin dissecting it for downgrade options and exploits.
 
Sounds good, keep us updated. If you need someone to test your exploit on a physical device I'll be willing to.
I have B08 and B14 available for testing. I could use more people once I get it solidified though. I'm also tentative to have physical devices test it as @GarnetSunset had a total SoC failure while running it, so I can't 100% rule out that it can't cause physical damage.
 
Not yet... Have to do a back up of all the partitions separately. Making sure I can load them one by one... Don't know where it security key would popup the error. Im actually backing up and flashing same partitions one at a time 😉
Wait, you are actually able to pull partitions? We need full logs of this. Just having the partitions available to us is a massive step forward.
Things you should include:
Driver name and version

Qfil/miflash etc exact version

Cable type (C to C, C to USB 3/2, C to micro b etc)

Operating system and bit

Phone build
 
i need to find a way to convert .IMG to MBn
Im working on it U can use QSPT connect through FTM mode so it can read fone
 
Last edited:
Status
Not open for further replies.
Back
Top Bottom