• 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.
Not sure if this is my 1st or 2nd post, but please don't let that discourage you from reading this (and the fact that the only decent amount of development is on here and not XDA where I'm usually at). I've been following this thread around for literally months now, racking my brain as to what could be done to root this bastard. I remember someone trying to obtain temproot by causing a scare by whatever exploit I can't remember at the time, but what about dirtycow? Drammer? I thought somebody had tried stage fright, I'm not certain. But I'm just trying to throw a bone out to anyone and see if they can't turn up with something, I'm not as adept as I'd like to be, but I'm not a novice user, and I have a spare T-Mobile variant ZMAX pro I can chock up as a loss and a guinea pig, just let me know, if this post was utterly useless and I'm an idiot, sorry , my mistake, but hopefully it proves to be useful instead. EDIT: has anyone poked around the axon 7 fastboot/bootloader unlock file and maybe port it to our device? I mean ive seen crazier things happen, and I know they're 2 completely different phones with different hardware, but thinking of same parent company so hey, anything can happen, but it literally looks like ZTE just patched in fastboot onto the axon 7 through an OTA. Just my 2 cents and maybe worth looking into. My biggest reasoning is because it's able to be flashed through a stock recovery.
1. Yes check the last 107 pages for people trying publically available stuff.
2. We can't access fastboot on this device.
3. Flashing anything from another phone to this phone or ANY phone for that matter means death for that device.
4. Axon 7 is bootloader unlocked. This is not.
 
This may be a stupid question but would it help to have a systems dump off the T-Mobile (B13) . I got the one off my phone.
 
It's just an example dude. Not all Samsung phones are rootable, even when there's a tool that works for most of them. So rooting this ZTE is not even in the same league of difficulty.
Bro I know sorry if I upset you was tring to start an argument I know not all phone e are rootable I have made y phone that don't have root
 
So I've tried kingo root recently and all I got was 90% all 3 times I tried and keep getting the same error code 0x1FE762 I even tried on Windows it said 100% but failed

I'm on V1.0.0B20
 
So I've tried kingo root recently and all I got was 90% all 3 times I tried and keep getting the same error code 0x1FE762 I even tried on Windows it said 100% but failed

I'm on V1.0.0B20

King/kingo/srs/rooters/etc will all fail on this phone unless a very serious kernel level bug shows itself and can be exploited in software and remove dm-verity.

The system just rolls back any changes we make. Check pages 60-80 (I think) where we talked about a software method.
 
King/kingo/srs/rooters/etc will all fail on this phone unless a very serious kernel level bug shows itself and can be exploited in software and remove dm-verity.
The system just rolls back any changes we make. Check pages 60-80 (I think) where we talked about a software method.


Didn't you guys have temp root?
 
I'm expecting something soon.

Good POC, some people already have it working on laptops and even the nintendo switch. (The bug, not root)

http://boosterok.com/blog/broadpwn/

It has promise, and the 3DS SSB exploit uses a similar function of raw beacons, so it has been done in the wild.
Creating the beacon itself shouldn't be an issue (Kali already has stock tools for doing this), but getting enough executable data would be the hard part. With a NAND image it'd be quite quick as we can just allocate where we need to, but as it stands right now, this could take a ton of trial and error before getting anywhere.
 
It has promise, and the 3DS SSB exploit uses a similar function of raw beacons, so it has been done in the wild.
Creating the beacon itself shouldn't be an issue (Kali already has stock tools for doing this), but getting enough executable data would be the hard part. With a NAND image it'd be quite quick as we can just allocate where we need to, but as it stands right now, this could take a ton of trial and error before getting anywhere.
haha I love the packet clone sploit on the 3DS.

I mean a lot of trial and error but searching for pointers shouldn't be impossible. Theres no ASLR.
 
Status
Not open for further replies.
Back
Top Bottom