yashsingh1/xdaforums huggingface dataset:
[ZTE ZMAX Guides, News, & Discussion] fire3element:
Wasn't taking a stab at you. No, you have done much research. Matt just make a good post for advice.

I am learning just as much as you. And if you read ant of my posts, I try hard to make sure people know I am not being harsh on anyone.

Truck on brother. We are all here to help one another. :victory:

---------- Post added at 07:36 PM ---------- Previous post was at 07:32 PM ----------

That batch is only for those that have just temp rooted with KingRoot and have trouble following the rest of the steps.

If you reboot at all after getting Root with King, King will then install itself as SU in xbin.

YOU WILL NOT BE ABLE TO REMOVE KINGUSER'S SU GRIP AND REPLACE WITH SUPERSU.

That will require you to boot back into the stock recovery and Factory Reset.

Again, info that has already been discussed, but is now lost in the sea of pages.
[ZTE ZMAX Guides, News, & Discussion] Meekplague:
No I wasn't taking offense [emoji4] I just kinda figured it was sorta directed at me because he quoted my quote and you quoted his you keeping up? Lol but no really I know you wasn't trying to be mean or anything just wanted to clear it up that I didn't just stumble onto the thread yesterday and I've been trying my hardest to keep up with everything but honestly its a bit overwhelming anyways I'm rambling at this point so gonna stop. Cheers [emoji12]
[ZTE ZMAX Guides, News, & Discussion] Cyconumnum:
Sorry about the redundancy......I just have one question about the script......

It's dumb I'm sure.......

So...after I run the script....it will boot to Android....And I can reinstall TWRP to reestablish recovery on the phone?
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
Yes.. Run the recovery script included in the folder
[ZTE ZMAX Guides, News, & Discussion] Cyconumnum:
Sorry...I really am literally that slow
[ZTE ZMAX Guides, News, & Discussion] Exconvict:
Just here testing....
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
All the script does is backs up the active recovery partition to sdcard.. So if twrp is set as active recovery it should be the recovery img backed up to the sdcard
[ZTE ZMAX Guides, News, & Discussion] biledigger:
The easiest way for you to customize your O.S. is to get it into R/W mode and uninstall bloatware and add upgraded apps into the system ROM. Just be careful because some apps won't run at all from the ROM sector. After you have it customized. Install TWRP and make a backup of your O.S. You should be ready to go afterwards. In all honesty. Having TWRP is better than R/W permissions. A lot of software runs perfectly fine such as sixaxis, trickster mod and xposed.
[ZTE ZMAX Guides, News, & Discussion] fire3element:
Yeah, I follow...

Well, I did just stumble on this tread a "few" days ago. Bought this phone on May 2nd. We now have temp Root, a script to finish the perm Root, a partial Recovery, and now a Rom in development. Your point?

I kid I kid :P (picking a fight here, you follow?) :silly:

Reply to another post:

_delete_

nevermind :)
[ZTE ZMAX Guides, News, & Discussion] UnderCovaBrotha:
Wanted to chime in briefly. Thanks to all who worked on a root solution to this cheap,carrier phone. From all reading, I was able to root by king root app, got kinguser su rights, then installed flashify. BACKED UP recovery.IMG and stock kernel,then installed twrp apk. Used quickboot apk booted into trwp recovery..BACKED UP ROM... ..flashed su zip file v2.46...rebooted..uninstalled all three king user related apps...perm root achieved on all reboots...no adb crap...only issue unable to install xposed and unable to rw to system..I can only freeze apps with bloat freezer pro..Any clear suggestions...thanks
[ZTE ZMAX Guides, News, & Discussion] ghet2rockuu:
wit out r/w u cant install exposed
[ZTE ZMAX Guides, News, & Discussion] tech_yeet:
Actually you can "Try the method I used!

Make sure you have TWRP installed btw

How to do it:

Install Xposed Installer

Change from Write to /system to: Recovery (Flash Zip Automatically)

It will download and ask to reboot.

i freaked out at this point: The phone will install it via Recovery, then it will Boot into Security Error Mode : Flashing Green and Red

Just reboot into Recovery and select Reboot Bootloader

Phone should boot back up as normal and Xposed will be installed! Grab some modules, Check em and reboot to apply!﻿"

Z999LP-A-LTE

---------- Post added at 01:20 AM ---------- Previous post was at 01:17 AM ----------

https://plus.google.com/105855773732882713268/posts/VDADzGaYdRY

https://plus.google.com/105855773732882713268/posts/eqLdwNMAJNW

https://plus.google.com/105855773732882713268/posts/5hx6DwMyMh3

Some proof...

Z999LP-A-LTE
[ZTE ZMAX Guides, News, & Discussion] Cyconumnum:
script won't go past start.......

i even tried placing all the files from the zip in the adb folder........

but, i did try in an elevated window adb devices...and mine showed..unblocked...

before i did the TWRP SU Update flash..it would show that my device was blocked or somthing to that effect......

could it be i'm allready fully rooted ?

i installed xposed mods without a hitch....

with one exception that i fixed ....

SU asks about permissions with everything that should ask about it.....

in an elevated window...what can i type to confirm root?
[ZTE ZMAX Guides, News, & Discussion] UnderCovaBrotha:
That worked..xposed installed..thanks
[ZTE ZMAX Guides, News, & Discussion] fire3element:
Very possible. Why are you trying to use the script if you already have root?

This script is meant for those that have just gained temp Root from KingRoot, and are too afraid to proceed.

If you continued on the ADB steps, rebooted into android as Recovery, KingUser is now your SU. You can NOT remove it without a complete Factory Reset, then going through all the steps again. And you have to restore the Factory Recovery before you can do the reset.

This is why everyone was warned about proceeding. Extremeasue went through the trouble of making a script to help the less knowledgeable.

I am not being down on you in particular. This is a message to all those that have KingUser as the SU now.
[ZTE ZMAX Guides, News, & Discussion] UnderCovaBrotha:
By any chance ..is there a mod to stop system update.. stuck in notifications.?
[ZTE ZMAX Guides, News, & Discussion] Cyconumnum:
because i was'nt completly sure....that's why i asked about possibly getting confirmation by inquiring in an elevated cmd window

please re read what i asked...thank you
[ZTE ZMAX Guides, News, & Discussion] ghet2rockuu:
i had it installed the first day with no issues
[ZTE ZMAX Guides, News, & Discussion] Cyconumnum:
nevermind....i'm cool...sorry i made anyone mad.....was'nt trying to get chewed on because i asked a question

i'll just go back to watching ....thanx for the help
[ZTE ZMAX Guides, News, & Discussion] fire3element:
Uncheck the [_] Show Notifications box in the app settings for Google Play Services.

---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------

Not mad at you dood. I always try to be as informative in my posts as I can be, so no questions are left.

It was a valid question. I learn, you learn, we all learn. Can't do that without questions and ANSWERS.

Happy to help :)
[ZTE ZMAX Guides, News, & Discussion] 70cutty:
Thanks bruh ...it worked
[ZTE ZMAX Guides, News, & Discussion] Ranger1189:
Too scared to try this root method for fear I might brick my phone. Every other phone that I rooted was done with a one click apk method. I am however learning a lot of things and when I feel comfortable I may give it a shot. Thanks to all for their input so far.
[ZTE ZMAX Guides, News, & Discussion] fire3element:
Its not that bad now. The KingRoot app is not dangerous by itself. It only provides a temp root that will be gone after a reboot.

That is, if you are lucky to get it to root your phone.

The script that we have now should automate the rest. You need to know what version of the Zmax you have. MetoPCS, Tmobile, Univision.

We are working on scripts for different variants, and possibly combining all the scripts into one for easier use.

Waiting is a wise decision right now. Right on the "tip of the iceberg" per say. I would guess by months end, we will have some concrete on the Zmax.
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
Try to mount system... What do you mean it's not running pay start..?
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
You literally cannot get any easier under the ZMAX's circumstances. KingRoot does half the work and the script does the other half. I ran this script about 25 times during testing, each time it did write to my recovery partition, which is one of the easiest ways to brick if you don't know what you are doing, and I'm typing to you from this phone. There were many steps taken to make this noob proof. Fact of the matter is that without an unlocked boot loader to disable write protection, this is sort of the only way you will get functioning permaroot.

Just to throw this out there, flashing a boot loader is one of the most dangerous modifications you can do to an android phone, next to S-OFF for HTCs. That half a second before your phone screen turns on is the time where the bootloader checks the integrity of all the partitions. No boot loader means no check which means no functioning phone. You won't get root without the methods available, point blank.
[ZTE ZMAX Guides, News, & Discussion] dmeeks72:
Thanks to all for your hard work on getting this phone rooted! I look forward to seeing what comes out of it.

One reason I am holding off on rooting this phone is to make sure I can update it when they finally do an OTA to enable Band 12.

I asked today on the TMobile page when we might see Band 12 enabled on this phone. Here is the reply I received:

"T-Mobile: Hi David! I got word back, we should see it in the next 2-3 months. I won't be able to get more specific than that though. *LL"

Is there any chance this phone has a service or engineer mode we can go in to and manually enable Band 12 or are we just going to have to wait for TMobile?
[ZTE ZMAX Guides, News, & Discussion] loonycgb2:
Metropcs update can easily be adopted to the t-mo version.

Difference is the tmo version will like always include tmo specific apps.
[ZTE ZMAX Guides, News, & Discussion] jcase:
Isn't MetroPCS CDMA?

That would mean different hardware, radios etc.

Don't flash CDMA firmware to a good phone
[ZTE ZMAX Guides, News, & Discussion] hroark13:
T-Mobile owns Metro now, all their new phones are GSM
[ZTE ZMAX Guides, News, & Discussion] tech_yeet:
No it use to be cmda now its GSM and runs off the T-mobile network...

Z999LP-A-LTE
[ZTE ZMAX Guides, News, & Discussion] jcase:
O how did I miss that buyout.

Ah then i take that back
[ZTE ZMAX Guides, News, & Discussion] tech_yeet:
Hey jcase is it still possible to hard brick a phone by flashing stuff you not supposed to? Even with TWPR?

Z999LP-A-LTE
[ZTE ZMAX Guides, News, & Discussion] ghet2rockuu:
this happened in 2012 :/

---------- Post added at 04:29 AM ---------- Previous post was at 04:27 AM ----------

OF COURSE
[ZTE ZMAX Guides, News, & Discussion] stinkbud:
Just a thought ... with all the developments happening with this phone, the FAQ at the beginning of this thread should be updated. It would save noobs all kinds of time searching out an ever growing thread.
[ZTE ZMAX Guides, News, & Discussion] tech_yeet:
But I through that TWPR was like a OS to its self?

Z999LP-A-LTE
[ZTE ZMAX Guides, News, & Discussion] ghet2rockuu:
if u flash something that isnt compatible with the phone it can brick .

say u flash audio aciid or something like that ive bricked my f6 beofre flashing wrong version .

twrp is just a custom recovery
[ZTE ZMAX Guides, News, & Discussion] fire3element:
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 PM 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] sleepingturtle:
I did the KingRoot method on a Walmart Family phone got success on the second try. Installed TWRP with no issues, SuperSU tried to softbrick when I installed via recovery (regular method didn't work) to the red/green flashing LCD. Volume up and power sent me to TWRP. Restarted without issue. Installed Xposed, same result. Installed my modules. This phone is now über slick (pretty fantastic before). Plus I have R/W in system. Thanks everyone for your hard work!
[ZTE ZMAX Guides, News, & Discussion] mingolianbeef:
Well... I can officially say that the ZMAX is Unbrickable... lol
[ZTE ZMAX Guides, News, & Discussion] Wade876:
I'm just wondering what I'm doing wrong here. I ran the bat file (windows) and this is what i came up with. After all that root checker says not rooted properly. Sorry for the troubles and thanks for your help at the same time.
[ZTE ZMAX Guides, News, & Discussion] imattmodz:
Are you sure you had temp root before running the script? It's saying the files that copied over do not have the correct permissions set. Did it copy the boot.img correctly over to the recovery partition? Try booting into recovery and see if it boots to Android instead. It should be booting into Android. If it doesn't then you didn't have temp root before running the script.
[ZTE ZMAX Guides, News, & Discussion] Wade876:
Yes i did have temp root and after running the script it deletes kingroot and the other two apps with it. I tried to boot into recovery but it boots to android
[ZTE ZMAX Guides, News, & Discussion] imattmodz:
OK that's good. After it's rebooted in recovery did you try going into supersu and updating it's binaries? Choose normal method and not twrp, because you don't have a recovery right now.
[ZTE ZMAX Guides, News, & Discussion] Wade876:
Tried running SuperSU and update binaries but it failed. After it deletes the kingroot apps, root checker say I'm not rooted.
[ZTE ZMAX Guides, News, & Discussion] imattmodz:
OK I'm assuming it did ask you to update in this case. It sounds like it's not booted into "recovery android". Reboot and keep hold the volume up button until you feel it vibrate twice. Once it's powered on all the way then try updating the binaries again. I'm trying to cover the simple stuff first. Plus I'm still half asleep so bare with me.
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
Run the command and post your output

getprop*ro.product.name

Looks like the back door is failing to create
[ZTE ZMAX Guides, News, & Discussion] DroidisLINUX:
If you missed it the second time

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

Um yes you can, I posted a how to earlier

All you need to do is get the su binary on sdcard, open cmd promp shell user with root#, or use terminal emulator # after uninstall root stays till reboot if you have given it eoot permissions, use kinguser to unchecked top three choices, backup root, updateroot, and ota survival I think is what they are, uninstall kinguser after that

And replace

/system/usr/iku

With SuperSU binary su

cat sdcard/su > /system/usr/isu

replace system/xbin/su with SuperSU binary

cat sdcard/su > /system/xbin/su

cat sdcard/su > /system/xbin/daemonsu

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

And you have replaced the su binary to SuperSU

The only thing kingroot does is an dota survival, they are editing our boot.img upron reboot adding a /dev/null for the install-recover.sh this is why after root if you dota update you might brick your device. This also shows us that our boot.img can be edited or written to I.e new kernel.

Make sure to chmod 755 each su after moving it

Sent from my Z970

root@draconis:/ # id

uid=0(root) gid=0(root) context=u:r:init:s0
[ZTE ZMAX Guides, News, & Discussion] fire3element:
We pretty much tried all of that, trying to get SuperSU to replace the KingUser SU in xbin.

It would refuse to copy over every time.

Permission Denied.

I could swear I had also gone into the KingUser app and turned off those options before trying on my end. Maybe I did not, or the changes didn't stick.

Besides you, was there anyone else that did this and can confirm success?
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
And like I said when you posted this before...

Kinguser can't be writing /system till after it is mounted with RW access...

If it could kingroot would be an end all be root solution and we wouldn't have this issue.....

---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------

So unless Wade rebooted after trying to run previous tutorial steps he should be fine...

I'm case and point a perfect example I uninstalled kingroot before my first recovery boot and I didn't have to do any of that...
[ZTE ZMAX Guides, News, & Discussion] thegrim11:
Non root question:

Does anyone else have problems with Google play music not reading the SD card for music? It doesn't read the 15gb of music I have so I use a 3rd party app.

¯\_(ツ)_/¯
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
Haven't tried lol.... It's been wakeup answer questions get home eat dinner take care of my daughter answer questions..... Work on another script I'm working on..... Answer questions...... Answer questions.........

Answer questions.........

Sleep
[ZTE ZMAX Guides, News, & Discussion] thegrim11:
Haha and if I recall correctly, you've been answering the same questions over and over. Well seems to me that's what's happening. No worries. It's not that much of a deal to download NexMusic instead :P

¯\_(ツ)_/¯
[ZTE ZMAX Guides, News, & Discussion] imattmodz:
I think he was saying kinguser was uninstalled, but SuperSU just failed to update binaries. But like you said, I believe that's because he didn't boot with RW access to allow the binaries the ability to update the system. That's why I believe he keeps getting the not rooted message from root checker. He never replied back so IDK. I just tried helping him the best I could.
[ZTE ZMAX Guides, News, & Discussion] xtremeasure:
Your right I'll edit last post for answer question.......
[ZTE ZMAX Guides, News, & Discussion] Cyconumnum:
I'm having another odd issue....When I start adaway,rootbrowser, and a hand full of other apps.....they just show their icon like they're going to start...then go to a black screen...the time and stuff is still up top......But the soft keys are temporarily disabled for like ten traps on the home key....back and menu are nonresponsive...

And now I'm magically unrooted.....well....super
[ZTE ZMAX Guides, News, & Discussion] DroidisLINUX:
No even with rw, king user stays, because of its dev/null install into boot, it has overwritten permissions of install-recovery.sh

Which has two links instead of running deamonsu as a service, this is why binaries even in twrp or full read write can't be updated from SuperSU apk, this is why I made my post, to show you how to replace the kingroot su binary with SuperSU, because of the permissions change in install-recovery.sh you cannot change move delete it, so I just told you how to male SuperSU use the pre installed install-recovery.sh to see su binary

Maybe you should read what I posted a little better

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 jcase 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

This also shows that editing our boot is possible, or custom kernels are possible, means more open better ability to flash custom Roms once we get more advanced recovery or devs, to flash and edit boot.img, cyanogenmpd kernel and ROM is what I am hoping for

Sent from my Z970

root@draconis:/ # id

uid=0(root) gid=0(root) context=u:r:init:s0
[ZTE ZMAX Guides, News, & Discussion] jcase:
I appreciate the proper accreditation very much but if possible, can you leave off the @ symbol, I get sooooo many mentions a day, its much easier on me if I'm only get notification of it if I'm needed