S
SapphireEx
Guest
I might be able to code an app to do this. I don't quite understand how it would escalate though
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root ZTE Zmax Pro Official Root Discussion
- Thread starter anubis2048
- Start date
-
- Tags
- root zte zmax pro
- Status
Once the exploit is ran, you would be able to escalate.
Ethorbit
Member
Page 61 of 74 on
http://androidforums.com/attachment...y-stumping-the-mobile-chipset-pdf-zip.117710/
has examples of doing the 2016-2504 exploit.
Page 16 of 74 for the 2016-2059 exploit.
Hope you find what you're looking for.
Also, if we run into problems, maybe we can contact the ZoneAlarm Forums?
http://androidforums.com/attachment...y-stumping-the-mobile-chipset-pdf-zip.117710/
has examples of doing the 2016-2504 exploit.
Page 16 of 74 for the 2016-2059 exploit.
Hope you find what you're looking for.
Also, if we run into problems, maybe we can contact the ZoneAlarm Forums?
If you want to play around with busybox, install busybox no root from the playstore. You can use it with terminal emulator.
S
SapphireEx
Guest
I can already use the built in busybox. Just need to give it the right permissions
This "fixes permissions" while installing.
https://forum.xda-developers.com/showthread.php?t=2195692
S
SapphireEx
Guest
Busybox is preinstalled into /system/bin. No need to install a seconday busybox. It's already fully functional, just doesn't have userland permissions for the important things. Open terminal emulator, do "ls -l /system/bin/busybox".
Gotcha. Just didn't know if you could use it.
S
SapphireEx
Guest
We can, just need the proper perms. It's read only, and I can't chmod into system. I pulled it into data/local/tmp to chmod, but the commands themselves are symlinked elsewhere
Dude... This phone is already rooted.
S
SapphireEx
Guest
That only applies to user installed busybox, not ZTEs busybox that comes preinstalled on stock firmware. We already have su from busybox, but it requires SUID, which I can't get as it requires different permissions. The userland permissions are there, but the root permissions are not.
I'm not interested in a psudo busybox that exists on userland, only the preinstalled one that resides in system/bin, that the permissions can't be changed without root.
Yes. But executing them requires building an APK.
S
SapphireEx
Guest
How so?
From everything I've seen lately it seems ZTE has root in there and it's hidden.
S
SapphireEx
Guest
Most likely as busybox su asks for suid. The problem is finding where they stored the binary, and executing it
Ethorbit
Member
But there's no absolute proof that it has been rooted already, just rumours
It will be hard to find without access.
Just from what I see. It behaves as though it's rooted. We just don't have permission.
PattyBear9210
Member
Grrr well no luck so far with the root.sh I got an with a fresh SDK an NDK install
Ethorbit
Member
Any progress?
S
SapphireEx
Guest
I haven't started. Gotta find a way to actually do it. The actual coding wont be rough, just implementing it.
asianrocker
Android Enthusiast
I was playing around the busybox commands. I found out something that solve my mysterious random numbers coming up my battery app.
It's a uid account. Try this command:
ls acct
And there you have the uid accounts. 2 of them show up on my battery use 99453 and 99443. Would it help?
ls dev and ls sys also interesting.
It's a uid account. Try this command:
ls acct
And there you have the uid accounts. 2 of them show up on my battery use 99453 and 99443. Would it help?
ls dev and ls sys also interesting.
Last edited:
asianrocker
Android Enthusiast
I also use this command and what is displayed is almost the same as in my phone.
cat /proc/filesystems:
https://www.centos.org/docs/5/html/5.1/Deployment_Guide/s2-proc-filesystems.html
cat /proc/filesystems:
https://www.centos.org/docs/5/html/5.1/Deployment_Guide/s2-proc-filesystems.html
- Status