• 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.
Charles367 said:
I don't understand why we can't get the files we need then being android is open sorce
Click to expand...
Certain parts of android do not have to be released if they have proprietary files included.

ZTE has always kept there sources closed. They usually only offer kernel sources.

Even then that would not not help as they will not release code to be exploited.
 
loonycgb2 said:
Sorry i worded that wrong..

There is software available for FTM mode from zte that which was leaked years ago, but is in chinese and is of no use since we do not have official formatted files to upload via the app.

So we can not officially write in FTM mode, but FTM gives adb shell access to which you can send and write and pull recovery via adb shell.

If you can write a new recovery you will be able to get system access to root. What we did before was pull both the bootloader and recovery images and write the bootloader to the recovery and recovery to the bootloader.

This way we would have system read/write, but i would not advise trying that till you have a twrp/recovery to use to fix the phone.

The bootloader is based off lkbootloader so it has two actual bootloaders in one.
Click to expand...
I remember having to flash the recovery switcher on the first ZMAX to write to system. I eventually left it switched to write access. How could I have overlooked that on this phone?
 
SapphireEx said:
dd permission denied. Hmm...
Click to expand...
They may have finally closed off access via FTM.

Have you tried reading via normal mode? Aka OS.

You may have to try different modes.. The main worry right now is if you can write since you can pull the recovery via the ota file.
 
loonycgb2 said:
They may have finally closed off access via FTM.

Have you tried reading via normal mode? Aka OS.

You may have to try different modes.. The main worry right now is if you can write since you can pull the recovery via the ota file.
Click to expand...
I'll run it through terminal, EDL (if I can ever get it to connect to me), and othet sources. Hopefully something works
 
SapphireEx said:
Seems FTM mode is locking down partitions. That, or I did something wrong.
Click to expand...
Are you able to create a partition? In theory, if you can create a partition, you can install systemless root there... And boom, root. I might be getting ahead of myself...
 
iancc86 said:
Are you able to create a partition? In theory, if you can create a partition, you can install systemless root there... And boom, root. I might be getting ahead of myself...
Click to expand...
I have no idea how to do that. And the entire system seems reads only.
 
iancc86 said:
I remember having to flash the recovery switcher on the first ZMAX to write to system. I eventually left it switched to write access. How could I have overlooked that on this phone?
Click to expand...
Hroark made the switcher zip as a automated way to do it. We started off DD writing the partitions as it wouldnt let use do it by direct write.

Its been a while since we looked into all this.

The zmax wasn't the first zte device to be rooted via this way.
 
Screenshot_20170309-004830.png


Well, emulator is denied too. Last option is EDL mode.
 
I can't read EDL at all. I have it connected via Qualcomm HS-USB QDLoader 9008. Anyone have a tool to read EDL data?
 
SapphireEx said:
I can't read EDL at all. I have it connected via Qualcomm HS-USB QDLoader 9008. Anyone have a tool to read EDL data?
Click to expand...
EDL is used as the nvdata connection for things like cdma workshop.

That doesn't have access to the partitions.

FTM is the recovery option.

Did you happen to update the phone recently?
 
loonycgb2 said:
EDL is used as the nvdata connection for things like cdma workshop.

That doesn't have access to the partitions.

FTM is the recovery option.

Did you happen to update the phone recently?
Click to expand...
I'm on 14, coming from 8. My spare I think is on B08. Same error on both.
 
DD itself is locked down. Just tried dd'ing a text file from storage to storage, and got permission denied.
*Edit I made a mistake. Dd is not locked down.
 
Disregard my last message. For some reason, I did /dev instead of /storage. dd is not locked down
 
Status
Not open for further replies.
Back
Top Bottom