• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ZTE ZMAX Pro (Z981) root discussion

Status
Not open for further replies.
anubis2048 said:
It'd be nice if the new people actually read the older posts before asking the same questions that everyone else asked... Now we have 2 pages full of crap that was already discussed back in September.

Not being rude, but you guys should read the older posts of this thread, because you were discussing things that had already been tried before.

You can't get to fastboot, you can't control it, you cannot unlock this phone using it. This has been known for a while now.
Click to expand...
They thought the new update patch could fix the fastboot. But honestly I think that's never gonna happen.
 
The OTA didn't unlock anything and fastboot is still inaccessable; all of those button combinations on startup we already knew about and could access before the latest OTA.

We kinda are just reciting what we already discussed months ago...
 
Tennaki said:
The OTA didn't unlock anything and fastboot is still inaccessable; all of those button combinations on startup we already knew about and could access before the latest OTA.

We kinda are just reciting what we already discussed months ago...
Click to expand...

The only way of knowing if the fastboot was unlocked with the update was retrying, but I agree some people are too lazy to read the whole thread and it bothers others who do have.
 
bcrichster said:
That'd be the $h¡t. [emoji41] Ty- in advance.
Click to expand...
Her it is.. https://drive.google.com/file/d/0B0PLOoNmK7L8dWxsUDIzS2tEQlk/view?usp=drivesdk. I didn't have time to test when next to a PC. If you or someone on here can test to see if it works I'd appreciate it. Also this is just a thought but can we take the OTA update file posted, extract the it and SuperSU zip, place the SuperSU files in the appropriate location in the OTA, repackage OTA, place on the SD card root directory and flash via settings? Another new feature with the update is the option to flash OTA via SD card through settings..
Screenshot_20161129-145058.png

If my theory works, I'd say someone at ZTE or metro found a way to help without getting fired.. lol..
 
lambo352 said:
Her it is.. https://drive.google.com/file/d/0B0PLOoNmK7L8dWxsUDIzS2tEQlk/view?usp=drivesdk. I didn't have time to test when next to a PC. If you or someone on here can test to see if it works I'd appreciate it. Also this is just a thought but can we take the OTA update file posted, extract the it and SuperSU zip, place the SuperSU files in the appropriate location in the OTA, repackage OTA, place on the SD card root directory and flash via settings? Another new feature with the update is the option to flash OTA via SD card through settings..View attachment 112462
If my theory works, I'd say someone at ZTE or metro found a way to help without getting fired.. lol..[/QUOTE how do i flash update via sd card or how do i get the zip and put it there so i can flash it in recovery
Click to expand...
 
biledigger said:
Did anyone get otg support from the firmware update?
Click to expand...
Thanks for reminding me.. I meant to check.. can someone try using this tool to inject SuperSU manually into OTA for SD card update in settings..
Also can the person who does it post here with title modified OTA.. and where's Messi? We can use his input right bout now..
 
lambo352 said:
Thanks for reminding me.. I meant to check.. can someone try using this tool to inject SuperSU manually into OTA for SD card update in settings..
Also can the person who does it post here with title modified OTA.. and where's Messi? We can use his input right bout now..
Click to expand...
I downloaded the update , checked it and found boot/recovery patchs in the patch folder and i think The best thing to try now is to replace the recovery.img.p by twrp's recovery.img and modify the update script to erase the old recovery and flash the new one also i don't think that will work with those who already updated as the update script have some check lines that will prevent reapplying the ota update so it will need to be edited in case of reapplying the ota although it needs to be doing carefully to avoid system fcs and errors as we don't have stock rom to flash in case of something is going wrong.
 
Last edited:
messi2050 said:
I downloaded the update , checked it and found boot/recovery patchs in the patch folder and i think The best thing to try now is to replace the recovery.img.p by twrp's recovery.img and modify the update script to erase the old recovery and flash the new one also i don't think that will work with those who already updated as the update script have some check lines that will prevent reapplying the ota update so it will need to be edited in case of reapplying the ota although it needs to be doing carefully to avoid system fcs and errors as we don't have stock rom to flash in case of something is going wrong.
Click to expand...
Sounds good, I shouldn't have installed the update though[emoji28]
 
messi2050 said:
I downloaded the update , checked it and found boot/recovery patchs in the patch folder and i think The best thing to try now is to replace the recovery.img.p by twrp's recovery.img and modify the update script to erase the old recovery and flash the new one also i don't think that will work with those who already updated as the update script have some check lines that will prevent reapplying the ota update so it will need to be edited in case of reapplying the ota although it needs to be doing carefully to avoid system fcs and errors as we don't have stock rom to flash in case of something is going wrong.
Click to expand...
I understand why you would want to replace the stock recovery. but since ZTE hasn't and probably never will provide source, shouldn't injecting supersu and gaining root be the main goal here?
 
str8upx said:
I understand why you would want to replace the stock recovery. but since ZTE hasn't and probably never will provide source, shouldn't injecting supersu and gaining root be the main goal here?
Click to expand...
Yes but if he can successfully replace stock recovery with twrp using said method, all that would need to be done to obtain root is flash SuperSU
 
svnxn said:
https://www.google.com/amp/androiding.how/dirty-cow-root-android/amp/ anyone seen this? havent been keeping up with the thread much so dont flame me if someone already posted this.
Click to expand...

Jesus f-ing christ
This has been posted at least
4
Different
Times.
Along with
Hey guys I just noticed that if you unlock developers mode you can click unlock bootloader
And
Hold power and volume down/up does something
Forum etiquette people
Read first
Comment second.....
Been lurking this thread for the past month
 
ohnoiforgotmypas said:
Jesus f-ing christ
This has been posted at least
4
Different
Times.
Along with
Hey guys I just noticed that if you unlock developers mode you can click unlock bootloader
And
Hold power and volume down/up does something
Forum etiquette people
Read first
Comment second.....
Been lurking this thread for the past month
Click to expand...
ignorance is bliss my friend. people rather rush and post things instead of going through the thread to see what has already been attempted.
 
Tennaki said:
The OTA didn't unlock anything and fastboot is still inaccessable; all of those button combinations on startup we already knew about and could access before the latest OTA.

We kinda are just reciting what we already discussed months ago...
Click to expand...

It does attempt to flash it from the sd card in recovery now. That's new. If we had a modified rom it might work.
 
You guys i fell asleep last night and woke up this morning and kingroot had finished and said it had root but there was a root auth error but i had the screen for root protection and everything but when i tried to use es file explorer and tick root browaer it failed just a heads up. With king root it went to 100 for. Me but gave root auth error
 
EliiphasLevi7414 said:
You guys i fell asleep last night and woke up this morning and kingroot had finished and said it had root but there was a root auth error but i had the screen for root protection and everything but when i tried to use es file explorer and tick root browaer it failed just a heads up. With king root it went to 100 for. Me but gave root auth error
Click to expand...
I just tried KR and it said exploit not avaliable
 
Status
Not open for further replies.
Back
Top Bottom