• 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.
Sounds like you've had some defective units friendo. I've only had the glitchy keyboard problem but switching to another SMS app fixes it.
The first two were completely defective. The second ones seem to have the same problems everyone else has, not nearly as bad as some have. The first ones were made in July, the ones I have now we're made in September.

I tried switching the SMS app, but they wouldn't show as read until I looked at them in the stock app. It didn't matter what was set as default.
 
The first two were completely defective. The second ones seem to have the same problems everyone else has, not nearly as bad as some have. The first ones were made in July, the ones I have now we're made in September.

I tried switching the SMS app, but they wouldn't show as read until I looked at them in the stock app. It didn't matter what was set as default.

Hangouts works fine for me.
 
OK I tried to stay optimistic. I have the ZTE grand max 2 which is the same as the pro except it has a extra camera where y'all fingerprint sensor is. My phone was released on Cricket way before y'all got the pro on metro so I been trying to root this phone before all of yall(unless you got a grandmax2)and I been very patient. I see no root in the future for our phones and I think the reason is actually US! it's too much of a coincidence when we get a step closer and all of sudden ZTE pushes a update. This has been going on since @Masterchief87 started the original thread. It's obvious ZTE is monitoring us here and Everytime someone post something they KNOW will get us closer they give us "fixes for our stability issues". Further locking down this phone. My advice would be to close these threads and communicate in private emails with trusted people. Till root is achieved then reopen the thread with the methods for root. This is the only way to outsmart the sneaky ZTE spies.
 
I'm pretty sure they aren't spying on us. I use the same picture on both sites. There are quite a few of us on both.
 
can anyone give this a try for me http://androidforums.com/threads/ne...s-with-the-new-sdcard-update-from-zte.786236/

"***So basically the key to rooting successfully is that you hold down on volume up on each 1st reboot attempt to boot to FTM and then let it boot normally if it is the 2nd or 3rd reboot for the current exploit it tries. Mine was successful after the 2nd exploit it ran so I only had to boot to FTM Twice. The total process took me about 3-4 minutes. If someone wants to help with more detailed instructions I am sure a lot of less experienced Android users could benefit from them."

im assuming we are going at this wrong. ive been trying adb shell and trying to get su for a while as long as these threads were up, i try to chime in when i have some insight but from here they basically go into FTM (maybe for some privileges that are not accessed in standard boot) after the initial reboot that is supposed to take place to finish up any root process. they worked around their restrictions. im now going to be trying different methods to maybe force a way in like how they have done. kingroot gets to 95% then fails but even if kingroot can get root its still root. and also im grabbing a copy of the b012 update. they pulled it back for some odd reason(they claim it defected more phones than fixed which is a bullshit reason to pull a complete OTA update) so im going to further investigate that build and see if there are any vulnerabilities because thats why im assuming they pulled it and then b014 will be out soon... b014 they wont slip up on but b012 i think they did. so we have 2 leads better than nothing. one is to try different brute methods of manipulation and the second is to find vulnerabilities within build b012 and see if there is something changed or a door we can put our foot in.
 
can anyone give this a try for me http://androidforums.com/threads/ne...s-with-the-new-sdcard-update-from-zte.786236/

"***So basically the key to rooting successfully is that you hold down on volume up on each 1st reboot attempt to boot to FTM and then let it boot normally if it is the 2nd or 3rd reboot for the current exploit it tries. Mine was successful after the 2nd exploit it ran so I only had to boot to FTM Twice. The total process took me about 3-4 minutes. If someone wants to help with more detailed instructions I am sure a lot of less experienced Android users could benefit from them."

im assuming we are going at this wrong. ive been trying adb shell and trying to get su for a while as long as these threads were up, i try to chime in when i have some insight but from here they basically go into FTM (maybe for some privileges that are not accessed in standard boot) after the initial reboot that is supposed to take place to finish up any root process. they worked around their restrictions. im now going to be trying different methods to maybe force a way in like how they have done. kingroot gets to 95% then fails but even if kingroot can get root its still root. and also im grabbing a copy of the b012 update. they pulled it back for some odd reason(they claim it defected more phones than fixed which is a bullshit reason to pull a complete OTA update) so im going to further investigate that build and see if there are any vulnerabilities because thats why im assuming they pulled it and then b014 will be out soon... b014 they wont slip up on but b012 i think they did. so we have 2 leads better than nothing. one is to try different brute methods of manipulation and the second is to find vulnerabilities within build b012 and see if there is something changed or a door we can put our foot in.

SRSRoot hasn't even been updated in a long time, and it's full of malware. Volume up and power doesn't take you into FTM mode either.
 
I haven't seen this mentioned anywhere yet, what if the reason this phone is impenetrable is because the way in is a factory cable? Old Motorola devices and the first two Kindle Fire tablets (there must be more but these are the examples I know of) required a factory cable which was a USB cable with two specific pins shorted. Also, I am on b08 as well. Can't you guys who are on b012 just flash the old firmware? People who missed the b012 update have flashed it manually.
 
I haven't seen this mentioned anywhere yet, what if the reason this phone is impenetrable is because the way in is a factory cable? Old Motorola devices and the first two Kindle Fire tablets (there must be more but these are the examples I know of) required a factory cable which was a USB cable with two specific pins shorted. Also, I am on b08 as well. Can't you guys who are on b012 just flash the old firmware? People who missed the b012 update have flashed it manually.
stock recovery doesn't allow downgrades and even if we did need a factory cable where would we get one.
 
stock recovery doesn't allow downgrades and even if we did need a factory cable where would we get one.

Well I know that you can buy micro USB factory cables, or you can make your own if you have a cord that comes apart easily enough and you're good at soldering tiny things. As for USB c though, I have no idea. Haven't looked it up yet but they may be sold as well. If not, micro and c have the same pins right? I'd assume the same two would have to be shorted as before, since all the micro USB devices used the same pins.


Forgive that stupid part about micro and type c having the same pins. What I meant thinking back on it was that since the Pro has a type c port but is only actually 2.0, it only uses the pins micro USB has, doesn't it?


http://www.droidforums.net/threads/how-why-to-make-your-own-motorola-factory-cable.146492/

Since our phone uses the usb 2.0 standard only 5 pins are used. I assume that they would be 1-5 in the same order as on a micro USB connector but I really have no clue. Could be any of the 18 pins type c has I guess.
 
Last edited:
If and when root comes for this phone it will almost certainly be for an older build. Why are you going to limit your chances for no reason?
 
I doubt it's a special cable. They probably have software that isn't public. We don't have any that is for this phone. The Axon was released without it too. They opened it up eventually. I'm sure they could do the same with this one.
 
The update fixed quite a bit of stuff.

Anything notable? Our phones seem to uh, not share a pattern of failures. My phone was complete trash on B08. Oddly enough, the bad B12 they yanked from the server totally fixed everything for me and smoked other people's phones. I'm not sure I wanna touch B14 yet, unless there are major aesthetic changes
 
I've noticed the differences seem to vary from phone to phone. Mine is running smooth. No major changes. I haven't had anything really weird happen yet. That's odd for these things.
 
I myself am on b08 and haven't had any issues besides the odd screen glitch once in a while, but it only lasts a fraction of a second. I did buy my phone this month though, it seems like you all bought your phones last year.
 
Status
Not open for further replies.
Back
Top Bottom