Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4hey all here are some of my findings, I went out and got a ZTE Zinger (Unision Mobile - T-Mobile MOVN) and a ZTE Whirl 2 (NET 10 - T-Mobile MOVN)
Hardware is pretty much the same, but software is very different
ZTE Whirl 2
Android 4.3
recovery = yes (hold vol up and power)
FTM Mode = NO
DFU Mode = NO
Is vulnerable to ASEC exploit, BUT
The problem is the aboot, boot, recovery, and system partitions are write protected, I can dump them, but can not write back to them
This means no root, not custom recovery, no custom kernel, no trying different boot loader (aboot) from similar phone.
The ZTE Concord 2 had a similar issue, but only the system partition was write protect, while you were booted from the boot partition, I got around this by installing a custom recovery, which I was able to do, because the recovery partition was not write protected.
I do not know how to get around the write protection on the Whirl 2, maybe some one more advanced than me can do it, but I really do not think the people with theses skills would be interested in a 20 dollar phone.
OK so on to the ZTE Zinger
ZTE Zinger
Android 4.4
recovery = yes (hold vol up and power)
FTM Mode = yes (hold vol down and power
DFU Mode = yes (hold vol up, vol down, and power)
I could not find any root exploits that would work on this phone, so I was not able to get temp root or anything.
I was not able to access the NAND threw DFU mode, on some ZTE MSM8960 phones you can access the NAND when phone is in DFU Mode and you have it connected to a Linux computer, it usually shows ups as /dev/sdc. This function seems to be disabled on this phone.
In FTM mode I was able to read the NV RAM with QPST 2.7 Build 4.11, but was not able to read or write to the NAND
In FTM mode I was playing with the ZTE Open C Upgrade tool, and I was trying to write to the NAND, it looked like it wanted to work, but failed.
I do not know for sure, but I am willing to bet money that the NAND is write protected on this phone, the same way the Whirl 2 is
I am sure that ZTE has some type of back door to acces and write to the NAND, but I would not be able to find it.
I am sorry to be the bearer of bad news, but my opinion is that you will not get full usable root on either of these phones
By best suggestion is to boycott ZTE products, but you have to keep in mind that ZTE configures these phones to the specs of the Carrier, so really the fault is with Net 10 and Univision, they tell ZTE to lock down the phone, and ZTE does so. The carrier is ZTE's customer, not you, you are buying the phone from Net 10, etc, etc. You are not buying the phone from ZTE, so ZTE does not really care if you want root or not. If you stop buying ZTE phones from Net 10, Net 10 will stop buying the phones from ZTE, yadda yadda yadda
Now it is possible that a ZTE Zinger for T-Mobile, or Straight talk is more open, etc, etc, but I doubt it, and I am pretty sure they are not vulnerable to any know root exploits
Anyway, I will be returning both of these phones.
.hK3I just picked up ten Whirl 2s yesterday for Perk, and my timing couldn't be better. I've read through this thread as well as done some outside research and have put together a simple tool that will gain root via the ASEC method and use jcase's backdoor to force ADBD to run as root, which I've attached to this post. This is persistent and will survive a reboot, but will NOT drop a su binary as the partitions are still write protected, so traditional root apps will not be able to gain root access.
The tool comes pre-configured for and is confirmed to work on product name P821A17 (NET10 Whirl 2). It may work on other models that are vulnerable to the same exploits, but you will need to pull ro.product.name from your device and replace "P821A17" in exploit.sh with your product name in order for the tool to work.
Proof of root access:
Enjoy! Please let me know if you have any questions, feedback, or problems to report.
3Please root with kingRoot or Kingoroot before attempting!!!!!
Well guys I made a CWM Recovery link here: https://mega.nz/#!JThCyZ4a
Flash with Rashr: https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools&hl=en
Download latest SuperSu Flashable zip http://www.supersu.com/download
So I hope this gets out so we can start developing roms for this little device. I'm learning how to port roms for this device. So far I've been trying to use a Motorola Moto E as a source rom but keep getting boot looped. If any one would like to help out, that would be great. BTW if your planning to build with this recovery, you must set the name as *w3ds* ( Don't type *)
I'd Recommend Superr Kitchen: https://xdaforums.com/apps/superr-kitchen/windows-linux-superr-s-kitchen-v3-0-0-0-t36017022When it was posted I was told it was for the zmax but when I tried to run the app on my zmax it says it is for a different model. But yes it comes from ZTE and when you open it it say "confidential for ZTE" and that redistribution, copying, etc is strictly prohibited. Not sure if it will work at all but since this thread has been so quite for weeks now I figured maybe it would get a few people interested again lol
Sent from my (ROOTED) Z970 ZTE Zmax2
