yashsingh1/xdaforums huggingface dataset:
[ZTE ZMAX Guides, News, & Discussion] DroidisLINUX:
OK if you permrooted with kingroot, and are having issues getting SuperSU to read binary here is what you have to do

1. Get full read/write to system per [MENTION=2376614]jcase[/MENTION] tutorial

2. Get su binary on sdcard

3. use either adb or terminal emulator and grant su

4. Keep the adb or terminal emulator as su and uninstall kingroot, make sure you unchecked all three of the root options in kingroot, keep updated, backup, and the other one I already forgot lol.

5. In adb or terminal emulator use

cat /sdcard/su > /system/xbin/su

chmod 755 /system/xbin/su

cat /sdcard/su > /system/xbin/daemonsu

chmod 755 /system/xbin/daemonsu

cat /sdcard/su > /system/xbin/ku.sud

chmod 755 /system/xbin/ku.sud

cat /sdcard/su > /system/usr/iku/isu

chmod 755 /system/usr/iku/isu

This should allow SuperSU to see su binary, the problem we are having is that install-recovery.sh instead of running daemonsu as a service with /system/xbin/daemonsu --auto-daemon &

is its just linking to another su in system/xbin and system/usr/iku

so were just going to replace those extra su with SuperSU binary instead, when we permrooted with kingroot it added a /dev/null for its recovery-install.sh to survive ota update and Its beyond my knowledge to change that, but I can tell you how to change kingroot su to SuperSU, and thus we have SuperSU instead of kingroot.

After binary is pushed in all spots install SuperSU and enjoy!

After this please reinstall twrp recovery so you don't brick your device.

Sent from my Z970

root@draconis:/ # id

uid=0(root) gid=0(root) context=u:r:init:s0
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
So funny story here my su binarys are persistent through a factory reset lol
[ZTE ZMAX Guides, News, & Discussion] totlth:
Will this work on my Amega 500?

They mostly come at night....mostly.
[ZTE ZMAX Guides, News, & Discussion] DroidisLINUX:
They would be all it does is delete /data, /cache, /dalvick-cache

System isn't touched

Sent from my Z970

root@draconis:/ # id

uid=0(root) gid=0(root) context=u:r:init:s0
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
Figured..

Do we we have a way to do a full reset??
[ZTE ZMAX Guides, News, & Discussion] DroidisLINUX:
[MENTION=4530658]totlth[/MENTION] You used kingroot? Look at your install-recovery.sh

Were it points to

/this/location/is/su

/and/this/location/is/su

Replace this location with the locations they have with SuperSU binary i.e su and bam! Install SuperSU and be happy.

Make sure to keep name and location exact

Sent from my Z970

root@draconis:/ # id

uid=0(root) gid=0(root) context=u:r:init:s0

---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------

@extremeasure If someone that tmp roots, and installs twrp before they do anything does a system backup

And posts there system.img we could use that to return to vanilla stock, this is grey area.... But should work looks at the 5.0 standing over there.

Sent from my Z970

root@draconis:/ # id

uid=0(root) gid=0(root) context=u:r:init:s0
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
The only way the kingroot /system changes are made is if you uninstall after you have system write access...

If you uninstall before your first reboot recovery it won't happen
[ZTE ZMAX Guides, News, & Discussion] DroidisLINUX:
??? If someone uses kingroot tmp root, installs twrp uninstalls su, deletes kingroot, kinguser, and then manually powers off then manually powers on with volume up and power to boot into twrp creates a full system backup, we could return to stock vanilla ROM, with no kingroot permissions or kingroot installs recovery.sh or ota survival that it had in place. Someone would have to do it from non rooted, tmp root to twrp, and backup system, then share system.img

Sent from my Z970

root@draconis:/ # id

uid=0(root) gid=0(root) context=u:r:init:s0
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
UPDATE: Link to Stock Rom

Sorry, fell asleep before I could update the link, here you go. Please read my post above BEFORE playing with this...

http://www.mediafire.com/download/f9d627elt01arnv/z970stock_tmo_442_5142015124.zip
[ZTE ZMAX Guides, News, & Discussion] DroidisLINUX:
If you missed the first time.

OK if you permrooted with kingroot, and are having issues getting SuperSU to read binary here is what you have to do

1. Get full read/write to system per [MENTION=2376614]jcase[/MENTION] tutorial

2. Get su binary on sdcard

3. use either adb or terminal emulator and grant su

4. Keep the adb or terminal emulator as su and uninstall kingroot, make sure you unchecked all three of the root options in kingroot, keep updated, backup, and the other one I already forgot lol.

5. In adb or terminal emulator use

cat /sdcard/su > /system/xbin/su

chmod 755 /system/xbin/su

cat /sdcard/su > /system/xbin/daemonsu

chmod 755 /system/xbin/daemonsu

cat /sdcard/su > /system/xbin/ku.sud

chmod 755 /system/xbin/ku.sud

cat /sdcard/su > /system/usr/iku/isu

chmod 755 /system/usr/iku/isu

This should allow SuperSU to see su binary, the problem we are having is that install-recovery.sh instead of running daemonsu as a service with /system/xbin/daemonsu --auto-daemon &

is its just linking to another su in system/xbin and system/usr/iku

so were just going to replace those extra su with SuperSU binary instead, when we permrooted with kingroot it added a /dev/null for its recovery-install.sh to survive ota update and Its beyond my knowledge to change that, but I can tell you how to change kingroot su to SuperSU, and thus we have SuperSU instead of kingroot.

After binary is pushed in all spots install SuperSU and enjoy!

After this please reinstall twrp recovery so you don't brick your device.

If you need to update binary, you need to use twrp, and copy over

/system/usr/iku/isu

And

/system/xbin/ku.sud

And chmod 755 both files, can be done in twrp with file manager

Sent from my Z970

root@draconis:/ # id

uid=0(root) gid=0(root) context=u:r:init:s0
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
I could do a system backup when I get home... Since I have nothing involving kingroot left in system and have the updated su binary... That's if you guys want it... I'm also not a TWRP user lol
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
My stock ROM doesn't have anything KingRoot in it either :) you can download it if you want! Few posts above I believe
[ZTE ZMAX Guides, News, & Discussion] steventechno:
Monster UI works but can cause lag with other mods

XhaloFloatingwindow works great

Appsettings works great

Kit Kat SDcard Full access works great

Google offline voice works well

SwypeTweaks works great

Unbeloved Hosts works well

And xPrivacy works great!

---------- Post added at 05:41 PM ---------- Previous post was at 05:31 PM ----------

Also the OP should be updated to say Yes with a link to the how-to guide under the can the phone be rooted section. Lol it still says root is unachievable.:)
[ZTE ZMAX Guides, News, & Discussion] imattmodz:
It's basically a brick when it boot loops and you can't un-boot loop. This is misinformation my friend, unless you know how to suggest a fix for the people that have a phone stuck in boot loop.
[ZTE ZMAX Guides, News, & Discussion] Shady545:
I was stuck in the boot loop.

To fix it, I held up on the volume rocker and the power button as it was looping.

Twrp loaded and I had twrp power the device down completely. Not restart it.

Boom, got out of boot loop. So no, it wasn't bricked.
[ZTE ZMAX Guides, News, & Discussion] Cyconumnum:
Same here
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
unless designated, a factory reset does not wipe the /system partition, which is why when you flash, say, cyanogenmod but factory reset like it's nobody's business, the root persists. If a factory reset wiped the system, you would have a phone with no OS.
[ZTE ZMAX Guides, News, & Discussion] DroidisLINUX:
Everyone go to new device request forum, and ask for zte forum

Sent from my Z970

root@draconis:/ # id

uid=0(root) gid=0(root) context=u:r:init:s0
[ZTE ZMAX Guides, News, & Discussion] imattmodz:
It is starting to get a little hard to follow.
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
I think its easier for us to start our own thread and have everybody place an "I" or something in there saying that they want a section, then after a 100 or so sigs we send the link of the to a mod directly. I feel like seeing as how people are on at different times, we could have a 100 signatures there but they are so spread out that they aren't seen
[ZTE ZMAX Guides, News, & Discussion] tech_yeet:
There is no lag my end and I'm using like 8 modules...m

Z999LP-A-LTE
[ZTE ZMAX Guides, News, & Discussion] TedRBarnes:
Alright, I give up for now. KingRoot is too unreliable. I'll wait until a simpler method is discovered. Good luck all!
[ZTE ZMAX Guides, News, & Discussion] krazyone2006:
Ok phone is getting covered by warranty so will have a new one in 3 days so I bought another for $100 with a new number so I will have two zmaxs here soon lol
[ZTE ZMAX Guides, News, & Discussion] Vyrus69:
http://xdaforums.com/showpost.php?p=60688490&postcount=1862

Use this method..its the one that worked for me the best, and I also had it plugged into the computer.
[ZTE ZMAX Guides, News, & Discussion] tech_yeet:
But then again I did some mods on the phone to make it run faster but maybe not because I have a zte sontana 4G that runs it without lag...

Z999LP-A-LTE
[ZTE ZMAX Guides, News, & Discussion] rkey1000:
After it failed and I uninstalled all kingroot apps I ran cm cleaner and rebooted. Reinstalled Kingroot and run. Worked like three times in a row for me before I got perm root. MPCS 4.4.4
[ZTE ZMAX Guides, News, & Discussion] TedRBarnes:
Alright, well unfortunately I'll need to wait until I get home to try as my work's guest wifi is constantly down. But thank you for the advice.

---------- Post added at 01:02 PM ---------- Previous post was at 12:57 PM ----------

When you say "cm cleaner" do you mean Clean Master by Cheetah Mobile?
[ZTE ZMAX Guides, News, & Discussion] smilesintears77:
+1
[ZTE ZMAX Guides, News, & Discussion] rkey1000:
Yes. Uninstall all 3 kingroot apps, run cm cleaner, reinstall kingroot and run.
[ZTE ZMAX Guides, News, & Discussion] Reallionare:
My request is there, need more though a lot of people lurks/monitors the thread so the Zmax community is large..
[ZTE ZMAX Guides, News, & Discussion] krazyone2006:
Kinda off topic but ZTE must have finally fixed the screens on the ZMAXs cause I don't have the bright white spot at the bottom of this one like my other one did and other people say theirs do. :)
[ZTE ZMAX Guides, News, & Discussion] JAWheat411:
I don't have this phone but I had been following the progress closely since it relates to a phone I have here at home, the ZTE Warp Sync. I actually used KingRoot to root a Verizon tablet I have also. I never installed SuperSu or anything. I had actually had it installed prior trying to root with other apps. When I was using KingRoot it popped up and said it crashed. So I uninstalled it. I now only have KingUser installed. It works just fine. There was actually an app called Clean Master that would not get root access through SuperSu for whatever reason. KingUser popped right up and I confirmed it. I noticed this because I had SuperSu on several other devices and Clean Master always told me it didn't have SU rights even though it was in the list with a #. Just wanted to throw my two cents out there that KingUser works and I am actually running it on one device with SuperSu.
[ZTE ZMAX Guides, News, & Discussion] kevyreil:
Lesson learned - root/factory reset/bootloop

I struggled with kingroot for a couple of hours. Sorry no real clue how to make that work better. I had wiped/factory reset my phone and had nothing installed and it worked on try ~50 for me. I will mention that I had the crying face and thought root had failed but I was in fact rooted so check root (or for all three king apps) before trying again.

The lesson learned is this: Don't do a factory reset after you root. I entered a long boot loop (about 24 hours until I fixed it). :o

To fix my bootloop:

Fix bootloop after root

held volume up and down together (plus power) and entered red led black screen mode.

held volume down and power to enter FTM mode.

adb shell (I was root)

# rm -rf /cache/* (not sure this was needed or helped but saw jcase mention it earlier in thread).

# reboot recovery (note that I was still in "dd if=boot of=recovery" mode from jcase instructions

Phone came up without having been reset (bootloop started with factory reset request).

And for completeness I rebooted once more and all appears normal. :p

Hope this helps. (Actually hope no one needs this help).

Cheers,

Kevin
[ZTE ZMAX Guides, News, & Discussion] rkey1000:
Also with last update.
[ZTE ZMAX Guides, News, & Discussion] Cyconumnum:
How do I get to where I vote for the thread?

Sorry I'm a little slow
[ZTE ZMAX Guides, News, & Discussion] imattmodz:
http://xdaforums.com/showthread.php?t=1660354&page=1780
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
Ok test time kiddies behind the scenes flame mingo and I have been working for the good of the chicken nooblet...

What I need from you a select few of you...

I need 2 people from each device version who are temp rooted to try a script...

What I need from everyone

I need the product number from each device

(Tmobile . univision . metro )

So I can adjust a script for each device

For now this will only work for windows users
[ZTE ZMAX Guides, News, & Discussion] stinkbud:
Mine was replaced a couple months ago. There was no bright white spot until this week. It's back in the exact same place.
[ZTE ZMAX Guides, News, & Discussion] thegrim11:
Metro version: P892T57_MPCS
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
Great info, gonna add this to the root thread
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
IF YOU HAVE NOT UPDATED YOUR PHONES THIS WILL NOT WORK

IF YOU DO NOT HAVE TEMP ROOT THIS WILL NOT WORK

This file cuts all the dirty work out of the root method... after hours of testing not one device has been bricked because of the script...

Tmobile/univision:http://s000.tinyupload.com/?file_id=74882245379693622844

Metro: http://s000.tinyupload.com/?file_id=79326478133970788856

Thanks to [MENTION=3953573]mingolianbeef[/MENTION] [MENTION=2233713]fire3element[/MENTION] for help writing, cleaning it up and being my first victu......... beta testers

Thanks to jcase [MENTION=711482]beaups[/MENTION] for the commands and all the work it took to find them

If there are any legitimate problems with the scripts pm me so i can try to fix them.....

even with all of the testing we did something may have snuck through
[ZTE ZMAX Guides, News, & Discussion] imattmodz:
If you haven't done so, please visit http://xdaforums.com/showthread.php?t=1660354&page=1780 to request a ZTE ZMax forum.
[ZTE ZMAX Guides, News, & Discussion] LowPro:
Here are the xposed modules working on my perm r00ted ZMAX
[ZTE ZMAX Guides, News, & Discussion] hroark13:
So are there any developers currently working on or thinking about building CM12 for this device ?
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
I'm just throwing this out there

PLEASE READ​

You all do know that the ZMAX has a dedicated section on AndroidForums.com right? We all love XDA but I'm not holding my breath on a forum section any time in the near future and that's just honest. I'm still an XDA'er to the end of me, but we are losing valueable information in thousands upon thousands of posts. Great rooting guides, stock roms and automated root methods will be flurried in a sea of butternoob questions and general discussion. I implore you all to not leave XDA, but make accounts over at AndroidForums, as I'm really gonna make a push for developers to be on AF because we have a section already.

Hroark13 posted on there is TWRP image, some guy posted my root method post on there. Most people reading this don't even know [MENTION=2376614]jcase[/MENTION] said he was tinkering with the bootloader, and another wave of people won't see his guide when (or if, he didn't promise anything, let me say that) something cool happens. Like I said, it's not XDA like you guys are used to, but the location is irrelevant in the grand scheme. If you are a user, make the jump, if you are a dev, start posting there so your stuff doesn't get lost. I will be officially reposting my stock rooted rom on there today or tomorrow, along with some other goodies I'm sure you won't wanna miss. [MENTION=6545437]xtremeasure[/MENTION] has automated root for the butternoob world, and I'm gonna ask that he post it AF as well. Thanks!
[ZTE ZMAX Guides, News, & Discussion] loonycgb2:
It wont be easy since everything has to be ported manual.

As it is our devices arent lollipop natively
[ZTE ZMAX Guides, News, & Discussion] jamesthegreat88:
Wait there is automated root?
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
Thought about it, didn't wanna tackle anything like that until I knew for a fact that we could flash that stuff without bricking, getting a lot of mixed signals as far as what will work and what will screw up. Plus, with no Lollipop source, I would have to have a lot of help from people more versed in that realm that I am, I've only ported using the appropriate source for the version I was building. I have done dirty ports though, but that doesn't apply to your question.

---------- Post added at 06:46 PM ---------- Previous post was at 06:42 PM ----------

For the second half that doesn't involve kingroot yes
[ZTE ZMAX Guides, News, & Discussion] imattmodz:
If you have temp root and a Windows PC then yes. It's literally one page back.. This is why we need a forum as said before, or all the goodies are going to stay buried. Request @ http://xdaforums.com/showthread.php?t=1660354&page=1780 it only takes 1 minute of your time.
[ZTE ZMAX Guides, News, & Discussion] Meekplague:
So the automated root does it write all the scripts for system? And if so will it work since I have twrp? Lastly how does one go about using it?

Sincerely

Yours Butternoob lol
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
This is designed for those who have KingRoot temp root and nothing else. While it will work for your phone, it i will replace your TWRP with the original boot.img method (as part of the script). You can, however, flash your TWRP as normal, just know the script replaces it.
[ZTE ZMAX Guides, News, & Discussion] Meekplague:
Awesome thanks for the info and for everything else you've done for this thread. [emoji3]
[ZTE ZMAX Guides, News, & Discussion] fire3element:
Ok guys, I have posted over to the KingRoot thread for some help concerning the low success nature of the app and our Zmax.

If everyone here agrees, I think we need to offer the King devs the bounty to "inspire" quick action in adapting KingRoot to work more effectively for us.

We all have put time and effort into making root happen for this device. I myself have been working on this for the last week for collectively over 60 hours.

Testing testing and more testing, with what little bit of skill I have.

Let us NOT bicker over who gets the bounty money. The fact of the matter is, KingRoot is what actually obtained root on the device.

Thanks go to [MENTION=5885045]tech_yeet[/MENTION] for finding that out first. I am sure others of you have tried KingRoot before with no results before tech_yeet gained root.

Don't be in a tizzy if you were not mentioned. We all work together for advancement as a T E A M. Put your differences aside and be happy we are moving foward.

ALSO... DO NOT SPAM the KingRoot thread with help questions and other nonsense. We DO NOT want to ward them off from helping us.

Thank you for your time and reading this. Here is to advancement.

Edit: From here on till we get a good number of people in agreement, I will be posting a link to this post in all my future posts. Please read it and lets us know if you agree to offering the bounty to the KingRoot devs. Thanks!

UPDATE:

GUYS LISTEN UP!

I have contacted one of the devs for KingRoot. They are willing to take a look and help us out, but they need info from us so they know which logs to look at on their side.

Info needed from users that have been successful in obtaining Root with the KingRoot app only please!

If you have not been Rooted by the King app, there is no need to send your info. It will help nothing.

What they need is

IMEI <----- most important (no they are not stealing IMEI numbers to use them for nefarious reasons) LoL

Android version

Baseband version

Kernel version

Build Number

All of those are listed in Settings --> About Phone

IMEI is in Settings --> About Phone --> Status

DO NOT POST YOUR IMEI ON THIS OR ANY OTHER PUBLIC FORUM!!!!

You can send me the information and I will relay it. If you do not trust me with your sensitive info, you can send it directly to [MENTION=6674985]Kingxteam[/MENTION]

I do not know what I would do with your info anyways (lack of skill/knowledge), but I understand if you do not trust an internet stranger with it anyhow. LoL

The more info we get to them, the better they can assess the situation.

Thank you.
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
Glad I can help :)
[ZTE ZMAX Guides, News, & Discussion] hroark13:
If we get a dedicated section on XDA I will post any thing I come up with on XDA and AF, but for now it seems it would just lost and mixed in with a sea of of ther posts threads
[ZTE ZMAX Guides, News, & Discussion] imattmodz:
The script does the adb commands and rewrites recovery partition with the boot partition. It shouldn't matter that you have twrp, however you won't have it after running the automated script. You won't have any recovery, as this is the only way to have true RW permissions on the system. The boot.img will basically be copied over top of the recovery partition allowing RW capabilities. This will leave you unable to perform a factory reset unless you rewrite the recovery back to the recovery partition. Everything concerning this has been covered already. I would recommend catching up on the previous pages before proceeding any further, to be sure you don't make any mistakes that would leave your phone unusable.
[ZTE ZMAX Guides, News, & Discussion] fire3element:
Level headed advice from a level headed user.

More of you need to bother to read, else end up with a nice shiny door stopper that has a pretty blinking red light.
[ZTE ZMAX Guides, News, & Discussion] Meekplague:
Hmmm okay ty. What I might do since I have two other zmax is use this on one of those see if it works out okay since this is my main phone I don't wanna screw it up.
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
My sentiments exactly. There's so many good posts that get losts within hours from comments flooding in. I would love to post on XDA, as I always have when I dev, but throwing out stuff haphazardly in this thread of creating a new post in the general section (which will get lost quickly like the root method did) is counterproductive. AF isn't permanent, but it is a solution that will be the most beneficial given our circumstances.

Not trying to destroy dreams, but there was a post in the subforum request thread that said they have root, roms, recovery, and a lot of users requesting a subforum, and their request has not been granted. That's not to say give up, because that mentality would have stopped root, but I am saying be proactive and then integrate accordingly when the time is upon you guys.
[ZTE ZMAX Guides, News, & Discussion] Meekplague:
And I have been reading all the previous posts been following this thread for quite awhile I was asking about that script to make sure if I missed a post regarding that script I'm sorry. But when there's 100 new posts when I wake up in the morning its hard to keep up.
[ZTE ZMAX Guides, News, & Discussion] Exconvict:
Wouldn't use the .bat if you have twrp it will take root and twrp. Kingroot worked 1st time around tho