• 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

Status
Not open for further replies.
No one played with rom toolbox yet? I did. I tried the boot animation, I disabled it. Yeah. Nothing, actually after I click disable and ok, it went back to default setting which is enable animation.

This is for the brave soul out there. Under tools there's a scripter. And there is a fix permissions script. You can look on the script program. It is clearly using busybox, which we have. You also have an option to execute the script. Or run it on boot.

IF you are brave, you can try it. I am not, LOL. But it might work. We have busybox installed, people. Just saying.
 
Last edited:
Billyckansbar said:
OK I ran jrummy's ROM toolbox. Script fix permissions. Rebooted my pro Z981B01. It didn't brick thank gawd. Also didn't do anything so...
Click to expand...
So have you tried fixing permissions without a reboot? It seems like reboot time is when this phone likes to change everything back to default. Maybe even mess around with some of the command line reboot options. I don't know, I am just speculating at this point.
 
But yeah, I as well am on B08.Boight this phone the day it came out and immediately disabled auto updates for this exact reason. I knew there would be security holes. And I knew they would patch them.
 
And I don't know if this would work or not, but has anybody tried running the ROM through a disassembler? Maybe somebody could use one to reverse engineer the ROM and find some of the more intimate hidden settings and change them? I know this works for a lot of PC software.
 
One more thing. I remember somebody mentioning that ZTE changed the pin configuration on the USB-C port. Has anybody managed to find the pinout config of this port compared to the normal USB-C pinout? I have a feeling a "factory cable" may be possible to build if we can find this information.
 
Jimmy Dixx said:
So have you tried fixing permissions without a reboot? It seems like reboot time is when this phone likes to change everything back to default. Maybe even mess around with some of the command line reboot options. I don't know, I am just speculating at this point.
Click to expand...
I tried both ways with root without root and about to set it at boot. I thought I did do that I'm gonna do it again. One minute
 
Jimmy Dixx said:
So have you tried fixing permissions without a reboot? It seems like reboot time is when this phone likes to change everything back to default. Maybe even mess around with some of the command line reboot options. I don't know, I am just speculating at this point.
Click to expand...
OK I fixed permission with root and without root option checked and with on boot selected. Ran script each time I checked and unchecked the with root option. The phone hung longer than normal on white ZTE boot screen. I was actually reaching for my laptop cause thought that's it it's bricked. Nope it booted. It fixed itself at boot
 
Billyckansbar said:
Jimmy DixxSo have you tried fixing permissions without a reboot? It seems like reboot time is when this phone likes to change everything back to default. Maybe even mess around with some of the command line reboot options. I don't know, I am just speculating at this point.
Click to expand...
OK I fixed permission with root and without root option checked and with on boot selected. Ran script each time I checked and unchecked the with root option. The phone hung longer than normal on white ZTE boot screen. I was actually reaching for my laptop cause thought that's it it's bricked. Nope it booted. It fixed itself at boot
Click to expand...

Damb
 
michaelchristian147 said:
Billyckansbar<blockquote>Jimmy DixxSo have you tried fixing permissions without a reboot? It seems like reboot time is when this phone likes to change everything back to default. Maybe even mess around with some of the command line reboot options. I don&amp;#039;t know, I am just speculating at this point.
Click to expand...
OK I fixed permission with root and without root option checked and with on boot selected. Ran script each time I checked and unchecked the with root option. The phone hung longer than normal on white ZTE boot screen. I was actually reaching for my laptop cause thought that&amp;#039;s it it&amp;#039;s bricked. Nope it booted. It fixed itself at boot</blockquote>Damb
Click to expand...

Damn*
 
I am beginning to wonder.. you know how most computers these days don't come with recovery disks, and instead have a hidden recovery partition on the hard drive? I wonder if that is what is happening here. A hidden partition that stores the factory system files, and on reboot, maybe the phone checks the system files against the ones in the hidden partition, and then replaces any that have been changed with the originals. Something to look into anyway.
 
Jimmy Dixx said:
And if that is the case, as far as how to access that hidden partition/memory chip? That would be the billion dollar question.
Click to expand...
Most keep a copy in the system folder or in a second folder in system of recovery.

I have not seen anybody use a dedicated partition for them as it would cause issues with system updates.
 
loonycgb2 said:
Most keep a copy in the system folder or in a second folder in system of recovery.

I have not seen anybody use a dedicated partition for them as it would cause issues with system updates.
Click to expand...
That is true, but what if they have designed their updates specifically for that system? I don't know much about the update process on the zmax pro though, because I haven't updated, nor do I plan to.
 
OK. I found out something really interesting guys. We also have toybox! Google it. And android built it in all their marshmallow devices!! You can access it in terminal emulator just type toybox it works like busybox! When I tried the mount rw command in toybox it gave me something about can't use it in fstab message. Also this is for devs here:

I ran getprop in terminal emulator and the recovery id is there. Do you think this can help in building TWRP for our phone?

http://www.joshslauson.com/2016/02/08/resolving/


Billyckansbar said:
Also this is PSA. I'm willing to brick my phone to help get root. Give me instructions I will try. Messi, asianrocker,iancc86, sapphire, Anubis,jimmyhendrix, etc..
Click to expand...

Well since you asked.. ONLY if you are willing to try it. Edit the fix permissions script replace ALL busybox words in the command lines in the script. Replace it with toybox. Save it. Then run it and/or on boot.

I must warn you this might brick your device because toybox is really the one being used by marshmallow devices ok?

You don't have to do this. Try at your own risk.
 
Last edited:
asianrocker said:
And.... I think this is what we need?

https://android.googlesource.com/platform/external/toybox/+refs

I am so gonna try the toybox suid command here:

https://android.googlesource.com/platform/external/toybox/+/marshmallow-dr-dev/Config.in

You guys should seek help with this guy:

https://forum.xda-developers.com/an...tool-flashable-busybox-toybox-merger-t3313199

This is I believe what will help flash this phone.
Click to expand...
Who knows? Maybe? Makes for interesting reading nonetheless.
 
It is interesting. Because of these box applet/commands. I kind of get how android works. And it works like windows 95 days. Where you have windows (the android) and also boot in DOS mode (the box applets).

So the only thing left for me to learn is how to compile these applets so I can access root.

I wonder if I can unbrick my alcatel with this new knowledge.
 
asianrocker said:
OK. I found out something really interesting guys. We also have toybox! Google it. And android built it in all their marshmallow devices!! You can access it in terminal emulator just type toybox it works like busybox! When I tried the mount rw command in toybox it gave me something about can't use it in fstab message. Also this is for devs here:

I ran getprop in terminal emulator and the recovery id is there. Do you think this can help in building TWRP for our phone?

http://www.joshslauson.com/2016/02/08/resolving/




Well since you asked.. ONLY if you are willing to try it. Edit the fix permissions script replace ALL busybox words in the command lines in the script. Replace it with toybox. Save it. Then run it and/or on boot.

I must warn you this might brick your device because toybox is really the one being used by marshmallow devices ok?

You don't have to do this. Try at your own risk.
Click to expand...
I'am in! Now I know that this is dumb, because I have no way of fixing the phone if it bricks at this point. I am ok with that. I'll tell you, I'am attempting this because a: you think it may work B: I want to own my phone I paid for C: I'm pretty much done with it anyway.

I'll never buy another zte from here on out. And I'll shout about it everywhere. So if it bricks I'll get my laptop out let you know.
 
Status
Not open for further replies.
Back
Top Bottom