• 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.
Yeah, well I just got good news regarding my credit,,, so come next due date, I'm switching over to T-Mobile from Metro, and I am getting a new phone. I am tired of waiting. I bought this phone on day 1, and we have gotten absolutely NOTHING from ZTE other than trouble. I wonder what kind of deals T-Mobile is offering for the S7 with a new contract..
 
anubis2048 said:
EDL and FTM without proper tools or documentation.... Yeah, all we need right? Might as well break your phone in half because using any tool on EDL or FTM could brick the phone. We have literally no clue what we are doing. ZTE locked us out and doesn't want us in.
Click to expand...
I'm perfectly fine bricking my phone in the name of progress. We already had a ZTE tool, made by a supposed ex ZTE worker that functions via EDL, and that is what rooted the Axon 7, another "unrootable" phone. We have many ideas about what we are doing, and what we are trying to do. Qualcomms 9008 communication protocal is being documented, and many people are discovering ways of creating firehoses and other utility based configurations. All it's going to take is an accident, and we have this phone blown open.
What's the point of your negativity? It does absolutely nothing for the scene at all.
 
Jimmy Dixx said:
Yeah, well I just got good news regarding my credit,,, so come next due date, I'm switching over to T-Mobile from Metro, and I am getting a new phone. I am tired of waiting. I bought this phone on day 1, and we have gotten absolutely NOTHING from ZTE other than trouble. I wonder what kind of deals T-Mobile is offering for the S7 with a new contract..
Click to expand...

Hey it was the same way when the first ZMAX came out too there just ****ing with us soon
 
Since root is looking like a dud (I accept that) is there anyone who can figure out how to boost the volume for music?
 
Last edited:
Be careful of updates just before or just after the release of the PRO 2. Sometimes companies "introduce" problems in an older model via an update to make upgrading to a new device more appealing.
 
To everyone going off topic to please try to stay on topic. There are many places you can go for volume boosting on an android phone. And please lets not just talk negative about rooting this device as we are here to make progress not tear down at it.
 
peekay19 said:
So Wikileaks just released some CIA Hacking Tools including Android Exploits. Hopefully the devs here can find something that will help in our cause. Here is the link:

https://wikileaks.org/ciav7p1/

Also included in the leaks are some Android Exploits and Hacking tools that are redacted at the moment, but could soon be published.

https://wikileaks.org/ciav7p1/cms/space_11763721.html

There is some stuff on privilege escalation in android. Maybe we could have some leads.
Click to expand...
The problem with this is with the release of these files and the information given to the public many companies have already put full effort into fixing the exploits and backdoors into the systems that these files affect. So if we were to have a chance of having any success with these we would have to work fast.
 
Here's a quick list of the tools I've used, what they did, and various other things.
One click root programs:
KingRoot: Failed
Kingoroot: Failed
SRSRoot: Claimed success, but failed.
Root Genius: Failed
iRoot: Failed
ZergRoot: Crashed the phone. I think this was unrelated to ZergRoot though.
Z4Root: Nothing.
Towel root: Custom and standard failed.

Tools:
Axon7Tools: Couldn't connect
DirtyC0w: Couldn't compile correctly
Metasploit: Used every exploit, and none returned a shell other than adb, which was still userland.
SELinux patching: Failed. Requires root access
ADB brutrforce: All directories are r/o other than /sdcard

Misc:
Various chrome exploits: Crashes chrome, doesn't elevate.
Kernel panic: Couldn't make it panic.
Fork bomb: Didn't know what I expected, just hung the phone.
EDL Python: Sent messages back and forth to me, seems to be looking for a specific file for me to send. Was only able to talk to it once. All others failed to connect. (If you want to try, EDL talks via python).
Wrong firehose: Couldn't connect
FTM: Basic shell access. Couldn't do a whole lot that I couldn't do in terminal emulator.
Pulling and attempting to install a modified system file: Couldn't install, file already installed.

Just for the hell of it:
Shell ASM injection: No magic bit. Couldn't make it elevate (emulator).
CPU hang: Overloaded with fork bomb, attempted to write to /system during. Was unable to write due to CPU not responding.

Possible things we could do:
Kernel panic write
 
SapphireEx said:
Here's a quick list of the tools I've used, what they did, and various other things.One click root programs:KingRoot: FailedKingoroot: FailedSRSRoot: Claimed success, but failed.Root Genius: FailediRoot: FailedZergRoot: Crashed the phone. I think this was unrelated to ZergRoot though. Z4Root: Nothing.Towel root: Custom and standard failed.Tools:Axon7Tools: Couldn't connectDirtyC0w: Couldn't compile correctlyMetasploit: Used every exploit, and none returned a shell other than adb, which was still userland.SELinux patching: Failed. Requires root accessADB brutrforce: All directories are r/o other than /sdcardMisc:Various chrome exploits: Crashes chrome, doesn't elevate.Kernel panic: Couldn't make it panic. Fork bomb: Didn't know what I expected, just hung the phone. EDL Python: Sent messages back and forth to me, seems to be looking for a specific file for me to send. Was only able to talk to it once. All others failed to connect. (If you want to try, EDL talks via python). Wrong firehose: Couldn't connectFTM: Basic shell access. Couldn't do a whole lot that I couldn't do in terminal emulator. Pulling and attempting to install a modified system file: Couldn't install, file already installed. Just for the hell of it:Shell ASM injection: No magic bit. Couldn't make it elevate (emulator).CPU hang: Overloaded with fork bomb, attempted to write to /system during. Was unable to write due to CPU not responding.Possible things we could do:Kernel panic write
Click to expand...

Today was the first time kingroot had some effect for me 53% rebooted phone
 
michaelchristian147 said:
Today was the first time kingroot had some effect for me 53% rebooted phone
Click to expand...
King is very misleading. Even at 100% it may not do anything, and rebooting is just a simple shell reboot command. Now if it booted into FTM, or EDL, that'd be better as it shows king is actively using specific commands. I'm going to catlog King and see what it does.
 
Look into recent public exploits they found for nougat version mediatek exploits.

I found one with android system level permission elevation that could work on the pro
 
SapphireEx said:
Here's a quick list of the tools I've used, what they did, and various other things.
One click root programs:
KingRoot: Failed
Kingoroot: Failed
SRSRoot: Claimed success, but failed.
Root Genius: Failed
iRoot: Failed
ZergRoot: Crashed the phone. I think this was unrelated to ZergRoot though.
Z4Root: Nothing.
Towel root: Custom and standard failed.

Tools:
Axon7Tools: Couldn't connect
DirtyC0w: Couldn't compile correctly
Metasploit: Used every exploit, and none returned a shell other than adb, which was still userland.
SELinux patching: Failed. Requires root access
ADB brutrforce: All directories are r/o other than /sdcard

Misc:
Various chrome exploits: Crashes chrome, doesn't elevate.
Kernel panic: Couldn't make it panic.
Fork bomb: Didn't know what I expected, just hung the phone.
EDL Python: Sent messages back and forth to me, seems to be looking for a specific file for me to send. Was only able to talk to it once. All others failed to connect. (If you want to try, EDL talks via python).
Wrong firehose: Couldn't connect
FTM: Basic shell access. Couldn't do a whole lot that I couldn't do in terminal emulator.
Pulling and attempting to install a modified system file: Couldn't install, file already installed.

Just for the hell of it:
Shell ASM injection: No magic bit. Couldn't make it elevate (emulator).
CPU hang: Overloaded with fork bomb, attempted to write to /system during. Was unable to write due to CPU not responding.

Possible things we could do:
Kernel panic write
Click to expand...
Drammer: No bits found to exploit
Kernel Panic: Can't get anything to crash the phone.
Heat: Just slows phone down
Cold: Laggy but no crash.
 
SapphireEx said:
King is very misleading. Even at 100% it may not do anything, and rebooting is just a simple shell reboot command. Now if it booted into FTM, or EDL, that'd be better as it shows king is actively using specific commands. I'm going to catlog King and see what it does.
Click to expand...
It went further for me today too. Maybe they're working on new exploits but they need to be tweaked for us.
 
iancc86 said:
It went further for me today too. Maybe they're working on new exploits but they need to be tweaked for us.
Click to expand...
I'm stuck at 51%, but then again, that's misleading. But it does seem King has a specific frame in mind for getting this rooted.
 
Status
Not open for further replies.
Back
Top Bottom