-
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
- Thread starter anubis2048
- Start date
-
- Tags
- root zte zmax pro
- Status
S
SapphireEx
Guest
UID is 2000 it seems, permission level is R/O for most files, everything else is -/-
Have you tried some of the chinese root solutions? They may or may not be just a repackaged Kingoroot. I can do some research into it but I don't know which phone has the same specs as the zmax pro for the chinese market. As far as I know the zmax pro is exclusively for American markets...
Removed a few derailed posts.
Keep it on topic puh-leez
....oh, and respectful of course 
Keep it on topic puh-leez
....oh, and respectful of course Agreed! I Got behind...
Jimmy Dixx
Well-Known Member
Wait.. You guys just figured out BusyBox is installed? I had known that for months, just didnt think it would help without being able to use the basic root commands. So we need to change the permissions on BusyBox then?
Jimmy Dixx
Well-Known Member
I'm starting to think maybe they didn't lock it down much at all, that maybe they did it all a bit oddly so that we would think they did.
I noticed that from your logs too. The fact it's trying to root rather than just saying no means they have something in works.
This means we're trying to root a phone that's already rooted... WTF did ZTE do?!? They must have their own su installed that we can't access... Yet.
Any of you mind installing quadrooter scanner off play store and see if it finds any exploits we can use?
Tried both but nothing.
Ethorbit
Member
{
"buildInfo": {
"fingerprint": "ZTE\/P895T20_MPCS\/urd:6.0.1\/MMB29M\/20170105.004521:user\/release-keys",
"kernelVersion": "3.10.84-perf-gcdba782-00680-g7a43ba7",
"brand": "ZTE",
"manufacturer": "ZTE",
"model": "Z981",
"release": "6.0.1",
"sdk": "23",
"builddate": 1483549457000,
"id": "MMB29M",
"cpuABI": "armeabi-v7a",
"cpuABI2": "armeabi",
"supportedABIs": [
"arm64-v8a",
"armeabi-v7a",
"armeabi"
],
"versionCode": 13,
"versionName": "v.13"
},
"results": [
{
"name": "ZipBug 9950697",
"isVulnerable": false
},
{
"name": "CVE-2013-4787",
"isVulnerable": false
},
{
"name": "ZipBug 9695860",
"isVulnerable": false
},
{
"name": "CVE-2013-6282",
"isVulnerable": false
},
{
"name": "CVE-2014-3153",
"isVulnerable": false
},
{
"name": "CVE-2014-4943",
"isVulnerable": false
},
{
"name": "WeakSauce",
"isVulnerable": false
},
{
"name": "CVE-2015-1474",
"isVulnerable": false
},
{
"name": "CVE-2015-1538-1",
"isVulnerable": false
},
{
"name": "CVE-2015-1538-2",
"isVulnerable": false
},
{
"name": "CVE-2015-1538-3",
"isVulnerable": false
},
{
"name": "CVE-2015-1538-4",
"isVulnerable": false
},
{
"name": "CVE-2015-1539",
"isVulnerable": false
},
{
"name": "CVE-2015-3824",
"isVulnerable": false
},
{
"name": "CVE-2015-3828",
"isVulnerable": false
},
{
"name": "CVE-2015-3829",
"isVulnerable": false
},
{
"name": "CVE-2015-3864",
"isVulnerable": false
},
{
"name": "sf-itunes-poc",
"isVulnerable": false
},
{
"name": "CVE-2015-3825",
"isVulnerable": false
},
{
"name": "CVE-2015-3636",
"isVulnerable": false
},
{
"name": "CVE-2015-7888",
"isVulnerable": false
},
{
"name": "CVE-2015-6608",
"isVulnerable": false
},
{
"name": "CVE-2015-6616",
"isVulnerable": false
}
]
}
"buildInfo": {
"fingerprint": "ZTE\/P895T20_MPCS\/urd:6.0.1\/MMB29M\/20170105.004521:user\/release-keys",
"kernelVersion": "3.10.84-perf-gcdba782-00680-g7a43ba7",
"brand": "ZTE",
"manufacturer": "ZTE",
"model": "Z981",
"release": "6.0.1",
"sdk": "23",
"builddate": 1483549457000,
"id": "MMB29M",
"cpuABI": "armeabi-v7a",
"cpuABI2": "armeabi",
"supportedABIs": [
"arm64-v8a",
"armeabi-v7a",
"armeabi"
],
"versionCode": 13,
"versionName": "v.13"
},
"results": [
{
"name": "ZipBug 9950697",
"isVulnerable": false
},
{
"name": "CVE-2013-4787",
"isVulnerable": false
},
{
"name": "ZipBug 9695860",
"isVulnerable": false
},
{
"name": "CVE-2013-6282",
"isVulnerable": false
},
{
"name": "CVE-2014-3153",
"isVulnerable": false
},
{
"name": "CVE-2014-4943",
"isVulnerable": false
},
{
"name": "WeakSauce",
"isVulnerable": false
},
{
"name": "CVE-2015-1474",
"isVulnerable": false
},
{
"name": "CVE-2015-1538-1",
"isVulnerable": false
},
{
"name": "CVE-2015-1538-2",
"isVulnerable": false
},
{
"name": "CVE-2015-1538-3",
"isVulnerable": false
},
{
"name": "CVE-2015-1538-4",
"isVulnerable": false
},
{
"name": "CVE-2015-1539",
"isVulnerable": false
},
{
"name": "CVE-2015-3824",
"isVulnerable": false
},
{
"name": "CVE-2015-3828",
"isVulnerable": false
},
{
"name": "CVE-2015-3829",
"isVulnerable": false
},
{
"name": "CVE-2015-3864",
"isVulnerable": false
},
{
"name": "sf-itunes-poc",
"isVulnerable": false
},
{
"name": "CVE-2015-3825",
"isVulnerable": false
},
{
"name": "CVE-2015-3636",
"isVulnerable": false
},
{
"name": "CVE-2015-7888",
"isVulnerable": false
},
{
"name": "CVE-2015-6608",
"isVulnerable": false
},
{
"name": "CVE-2015-6616",
"isVulnerable": false
}
]
}
Ethorbit
Member
How come it says I'm vulnerable to it and you're not? More people should check and then share the results if different.
Can you screenshot your results?
What build are you on?
Ethorbit
Member
Attachments
PattyBear9210
Member
Dammit!!! Well... You're on b08, and I'm on b14. It seems the earlier builds are vulnerable to the cves. That means b08 can be exploited.
Ethorbit
Member
Attachments
PattyBear9210
Member
Now how do we go about that
Ethorbit
Member
We both just submitted the same images hahaha
- Status