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

ZTE Zmax Pro, State Of the Development On This Device .

K well i'll check back in a bit. hope it doesn't take 2 days lol
 
This is the return for the mount and the recovery log. As far as I know it had the correct path [Dev/block/mmcblk0p20]
@Astr4y4L
Could that be the Magisk path. Doesn't Magisk already suppose to try to do this already on first install ?
It is a check box in the Magisk APP. Probably uses the same code. Would be something to check in the Magisk zip.
 
Last edited:
Jesus it's been a while since I've been here to contribute. I see roots been found. Also I'd like access to the discord again I had to take a hiatus, somebody DM me. Thank you - Harv
 
This is the return for the mount and the recovery log. As far as I know it had the correct path [Dev/block/mmcblk0p20]


thanks Bro got it.

can you run another code and post the out put again please thanks.

Code:
su
cd /dev/block/bootdevice/by-name
ls -a

the output of this will tell me how to patch that line in the other installer.
 
@Astr4y4L
Could that be the Magisk path. Doesn't Magisk already suppose to try to do this already on first install ?
It is a check box in the Magisk APP. Probably uses the same code. Would be something to check in the Magisk zip.


yeah I'm going to compare codes a bit...
but, i've moved from supersu compatibility, to trying to flash Opt-encrypt.zip so that we can disable selinux and dm-varity completely .

I think if we kill those real good, we'll get new doors open in the device.
new possibilities and such.


if anyone else has any good ideas or stuff to try against this thing list it here
 
It gave this, but maybe this is more useful.
 

Attachments

  • bootdevice_byname.txt
    bootdevice_byname.txt
    320 bytes · Views: 363
  • Systemdump1.PNG
    Systemdump1.PNG
    28.7 KB · Views: 368
  • Systemdump2.PNG
    Systemdump2.PNG
    37.9 KB · Views: 387
Back
Top Bottom