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

ZTE Write Protection for ZMAX and other ZTE phones

I tried it on the elite it will reboot lost root when reboot re roted and still cant delete system apps if can figure out if I can flash su using flashify then I should get full root
 
I tried it on the elite it will reboot lost root when reboot re roted and still cant delete system apps if can figure out if I can flash su using flashify then I should get full root
it's already been labeled in OP that this may not work, I'm hoping that I can find the same/similar spot for the terminal cmds @hroark13 found with the zmax. Any help would be greatly appreciated. I'm hoping they just changed the cmd
 
I was able to Root the ZTE N817 from Qlink Wireless, after using abd command line on Windows 10 with the correct drivers and adb shell installed, the command executed successfully and was able to achieve persistent root on the ZTE N817 after updating the google security patch even!
current Version:
MODEL NUMBER: N817
ANDROID VERSION: 4.4.4
BASEBAND: N817B01
KERNEL VERSION: 3.4.0-gb9ccd38-00530-gfb048cczte-kernel@Zdroid-SMT
SW VERSION N817V1.0.0B11 (current google update)
HW VERSION:CQ5110V2.0

***attempting to root your device may void your warranty, doing so is at your own risk, I nor androidforums is responsible for any damages that may arise from any posted material, proceed at your own risk.***

using terminal or adb shell issue the following command:

reboot disemmcwp

then proceed to root using kingoroot (worked for me)
I will be testing out Kingroot as well after doing a full unroot and factory reset
I will get back to you on this and possibly some custom roms and tweaks.
 
Works ZTE Grand x3

Could you explain exactly how you got it working? I entered the command on my windows laptop, and tried to push an edited build.prop that had the settings changed to userdebug with no results. It still told me it's a read-only file system and it failed to push it.

(Then again, he might not be using the Cricket Wireless Z959 version).

Also, sorry if I'm in the wrong category for this, I didn't know at the time of posting (and editing) if this is just for rooting, or if it allows write access for things other than Kingo. I did try rooting with Kingo and it told me "ROOT FAILED; try again or contact us for further support". Not to mention it kept popping up with "CONNECT SERVER FAILED" and "RETRY" or "QUIT" options. For some reason, the window was operable behind this with no need to press retry, and pressing quit closed the program.
 
Last edited:
Try downloading the kingroot app past versions from 4.0 to 5.+
Android terminal app ,BusyBox app,then run "su disemmcwp reboot" in Android terminal app
 
Try downloading the kingroot app past versions from 4.0 to 5.+
Android terminal app ,BusyBox app,then run "su disemmcwp reboot" in Android terminal app

Were these instructions for me? Installed all 3, android terminal failed to find su, busybox failed to open a root shell and KingRoot failed to even attempt a root, instead just had me make a request. Not sure of how your instructions help me here.
 
ZTE Grand X 3 has a crippled bootloader. It's unable to be launched. Sadly, your instructions aren't valid for my case.

Also, I contacted ZTE by email and they told me none of their phones have unlockable bootloaders, so it's apparently impossible to root any of their devices. Since I bricked my phone, I'm buying an LG Harmony.
 
My phone is a a ZTE grand xmax plus z987
It's oem boot loader option can be unlocked in developer options it's fully rooted by kingroot and supersume 7.6
They lied to you! Also if you can still power it on or if it goes into recovery mode still it's not bricked. Just download the original software zip on a SD card insert it and update thru recovery mode .under install update with SD card option.phone should reboot with normal functions
 
My phone is a a ZTE grand xmax plus z987
It's oem boot loader option can be unlocked in developer options it's fully rooted by kingroot and supersume 7.6
They lied to you! Also if you can still power it on or if it goes into recovery mode still it's not bricked. Just download the original software zip on a SD card insert it and update thru recovery mode .under install update with SD card option.phone should reboot with normal functions

Sadly, I found out later on that my phone was only out of charge, not bricked. Although, I already have my new phone now, so there's nothing I can really do about it. The only option I saw similar to anything with OEM, was "Enable OEM unlock". it didn't activate the bootloader, and I didn't see any other options that had OEM in the name.
 
ZTE Z958 Marshmallow Update WITHOUT ATT SIM

AT&T requires an active SIM in order to do a software update.

I don't have an active AT&T SIM so is there any way update my ZTE Z958 to Marshmallow
 
Worked on my ZTE Axon 7 with root and lineage os installed. I couldnt alter systems files such as fonts and stuff, after issuing command changes now stick.
 
Did not work on a new ZTE z959,will not root and says access denied at terminal when i input. tried adb worked but still wont root.
 
Hello,,
after command reboot disemmcwp icant root my device
my device android box ZTE B860H android box
i`m use terminal because adb locked from carier.
can help me please?
Sorry my langue is bad
 
Still nothing can be done to this terminal for this year 2019?
I have a terminal with IMEI: Unknown, it does not enter Bootloader, it stays in the AT&T ball and then it enters directly into the software, the software presents certain parts that are not normal, if you try to go out turning it off normal, it stays spinning and thinking and at After a few seconds it freezes before closing, you have to remove the battery to turn it off, I have it already debugged and I activate the OEM unlock, tell me how I do it to unlock the bootloader since with ADB this message comes out:
C: \ Program Files (x86) \ Minimal ADB and Fastboot> adb devices
List of devices attached
b955..xxxx unauthorized

Of course, after reading this whole forum, I know that these terminals are a mess to unlock the bootloader that is factory closed! :(

I can't get the Firmware Stock Compilation: Z958V1.0.0B16B Original and when trying to try to Flashear another similar one in Mode MicroSD Download, this error appears:

E: footer is wrong
E: Signature verification failed
Installation aborted

Logically it seems that it is not the correct Stock Firmware!

* I managed to make a Dump Firmware to the whole ROM, when I was only with the IMEI: Unknown
But when trying to Flashear the same Dump, the same error message comes out ....
* I managed to make a backup of tyoda the security zone!
* I can't do the QCN Backup, I don't know why? Surely for not having the ROOT, without ROOT it is impossible in this terminal.

Reading Device Information:

Model: Z958
Hardware: lol
Android Ver.: 5.1
Android OS: Lollipop
Platform: msm8916
Display id: Z958V1.0.0B16
Build Date: Sat Oct 10 03:38:42 CST 2015
Build id: LMY47O
Brand: ZTE
Manufacturer: ZTE
Product: lol
Carrier: unknown
GsmVersion: 5.1_r1
Build Date: Sat Oct 10 03:38:42 CST 2015

They can help??
 
Works for ZTE speed if you install the driver first
ZTE speed? Which speed do you mean?
You mean the high-speed driver, the dirver I have them very well installed, in fact, the Boxes that can detect the ZTE do it correctly and I have no problems with that, I mean it is the ROM Stock that flashes through the MIcroSD, I was already finding out and apparently it is an original file signed by ZTE, if the phone does not detect it as a ZTE signature it does not let it load, now .... when it seems nobody has a ROM Un-Brick file Firmware ZTE Z958 on the web and nobody, adding more problems, has been able to penetrate the bootloaders of these terminals that according to some developers are not interested in the qualcomm line, prefer Huawei, or Samsung. They are not interested in getting out more of these brands, they even get upset if you contradict them. Qualcomm may not be a great line of good taste programming, but there are many teams that even in this year 2019 are still using it and it is a somewhat closed way of thinking about it.
Sorry for my English...
 
Back
Top Bottom