• 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.
loonycgb2 said:
Lmao this is why i dont share exploits with people as this is why they get patched immediately.

Great job!
Click to expand...
If you got a exploit, then you shouldn't share the technical aspects of it in this forum. Its ok to say "I found a way to exploit the system" but how you did it or what you used, should only be shared with trusted people through pm or email. If you actually root the phone and install twerp and custom rom,you still shouldn't share the methods here in the public till all bases are covered.
 
Greysworld007 said:
If you got a exploit, then you shouldn't share the technical aspects of it in this forum. Its ok to say "I found a way to exploit the system" but how you did it or what you used, should only be shared with trusted people through pm or email. If you actually root the phone and install twerp and custom rom,you still shouldn't share the methods here in the public till all bases are covered.
Click to expand...
The exploit was already made public due to it being used for another phone, and other forums have already taken to testing it. There was nothing secret about it. Also, the vanilla exploit alone isn't enough to actually do anything, and it needs to be modified to actually work, which I didn't share the details of.
 
SapphireEx said:
The exploit was already made public due to it being used for another phone, and other forums have already taken to testing it. There was nothing secret about it. Also, the vanilla exploit alone isn't enough to actually do anything, and it needs to be modified to actually work, which I didn't share the details of.
Click to expand...
Ok I know that but the point I was trying to make is specific methods should not be posted in a open forum till everything is finished.
 
SapphireEx said:
The exploit was already made public due to it being used for another phone, and other forums have already taken to testing it. There was nothing secret about it. Also, the vanilla exploit alone isn't enough to actually do anything, and it needs to be modified to actually work, which I didn't share the details of.
Click to expand...
Pingpong root for s3 is public, but it can be used for all zte with kitkat. Does zte know that?

Kingroot is 6-8 exploits premade on a server so its easier to mention kingroot as it doesnt specify which is used.

Dirty c0w originally does not affect this system, but to mention which does then you lead a better direction to manufacturers.

If you knew about this method already why not continue to push on it?
 
I spy with my little eye a device named urd
 

Attachments

  • 21444748.png
    21444748.png
    1 MB · Views: 279
Further black belt on my google-fu. The creator of the 'that' said:

By the way if your bootloader is locked it won't do anything, it will write to recovery but just reboot into system how it was and system will flash stock recovery back again

And someone exactly has same output with locked bootloader device And that one actually has boot.img. installed. So we are back to the problem of that damn locked bootloader then?
 
asianrocker said:
Further black belt on my google-fu. The creator of the 'that' said:

By the way if your bootloader is locked it won't do anything, it will write to recovery but just reboot into system how it was and system will flash stock recovery back again

And someone exactly has same output with locked bootloader device And that one actually has boot.img. installed. So we are back to the problem of that damn locked bootloader then?
Click to expand...
Somewhat, in our situation its not just capable of writing to recovery, but also the main boot partition.
 
asianrocker said:
Further black belt on my google-fu. The creator of the 'that' said:

By the way if your bootloader is locked it won't do anything, it will write to recovery but just reboot into system how it was and system will flash stock recovery back again

And someone exactly has same output with locked bootloader device And that one actually has boot.img. installed. So we are back to the problem of that damn locked bootloader then?
Click to expand...
yea It always took me to a black screen after reboot
 
JoshuaAwe said:
How long has this thread been active for? I practically have given up root for this phone. I just pop adguard on and carry on. I'll check back in six months to see if this phone really gets root. lol.
Click to expand...
One silver lining to this phone is I found alternative ways to optimize my phone Without Root.
Adguard premium
Nova launcher with screen off apk for double tap scren off gesture.
Package Disabler apk for disabling bloatware
Status apk for centering clock and removing carrier name from status bar and
Audio pocket apk for YouTube playback in the background.
I use Xposed on my other rooted phones .
But my daily LG Stylo 2 Plus k550 has the 7.0 update and Xposed is not that friendly on Nougat yet.
Although 7.0 is running superb. Best O S by far.
Oh and don't expect 7.0 on the zmax pro. Zte has never updated an O S on any phone ..They just make another similar model with the new O S ..lol
 
OK.. Just a Headsh-Up:

I've mostly stayed silent in hopes of Root and development. This being said, I've a close friend who has one and it's a total piece is schitt. They don't do anything but call & text but almost never get notifications, phone calls, texts.. Almost none send out either. Phone calls included. Don't waste your breath or efforts on this garbage. I'm usually happy with ZTE devices but this model is horrible
 
Status
Not open for further replies.
Back
Top Bottom