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

Root cm13 booting on a zmax

hroark13 you're a bad @$$. AWESOME WORK!!! A beer or two on me :-).
I kwow that CM13 is not camera friendly when it comes to use the stock app so maybe we will need to use Open Camera or something like that... I'm sure that's not even important now lol.
We all appreciate your hard work.
 
He does it again!!!!!!
Thanks for caring enough to put in the effort and time and sweat and frustration.....
I bet it was a walk in the park :)
What's the biggest difference between 12 and 13 besides being based on M ?

Never mind.. I googled it... Sry
 
Last edited:
CYCONUMNUM said:
He does it again!!!!!!
Thanks for caring enough to put in the effort and time and sweat and frustration.....
I bet it was a walk in the park :)
What's the biggest difference between 12 and 13 besides being based on M ?

Never mind.. I googled it... Sry
Click to expand...


I honestly don’t know the difference. my kernel and device tree need some changes, and still do

I got it booting. but there is a lot of stuff not working, but getting cm13 booted on a new phone is a major milestone
 
OK for those that want to help

I am uploading an alpha rom, everything is still broken

one of the things I need to do is figure out which of the pre-built and proprietary files that I used in cm12.1, will work in CM13

here is the rom

http://www.mediafire.com/download/u0ack7q31hkobbt/cm13_zmax_alpha1.zip

here is the zip file that has the files i used in cm12

some of these files will fix stuff, and some of them with break stuff, and make the rom not boot

https://www.mediafire.com/?7pko5tcc8lm8d7s

here is a list of what some of these files are for
https://github.com/hroark13/android_device_zte_draconis/blob/cm12.1/proprietary-files.txt

I am not sure how much time I will have to put into this project, but at least if I get some people to help, maybe stuff will get fixed quicker
 
Last edited:
here is the source if anyone wants to try and build this

Device tree
https://github.com/hroark13/android_device_zte_draconis/tree/cm13

Kernel
https://github.com/hroark13/android_kernel_zte_draconis/tree/cm13

Vendor
https://github.com/hroark13/android_vendor_zte_draconis/tree/cm13

you have to patch VOLD, the patch is in the device tree
https://github.com/hroark13/android...vold_do_not_abort_on_setexeccon_failure.patch

after it builds you have to unzip and switch out the boot.img and re-zip it

because the
file_contexts
property_contexts
sepolicy
inside the boot.img needs to be replaced

you can just use my pre-built boot.img, but if you are making changes to the kernel source or ramdisk, then you will need to make repack your own boot.img
 
Last edited:
I'm running Carbon 5.1.1 on my Z970 right now, and it's way better than the stock 4.4.2 ever was, but I'm so chuffed to think that M might actually be a possibility now! Thanks for all your efforts @hroark13 !
 
hroark13 said:
pretty quiet in here, 9 downloads and no one is talking
Click to expand...

Once phone/MMS and data are working I'll start using it as a daily driver and try to help with finding bugs and how to reproduce them.

In the mean time I might be able to find a little extra time at night to expirement with those proprietary files for the existing build when I don't need to be able to use the phone nearly as much.

We might also be getting a couple other developers back to work on stabilizing Marshmallow now that you got it to compile and boot.

I might even fire up my box and try compiling it myself as well, but dont hold out too much hope on me being able to accomplish anything from that end. So far the only device I can compile ROMs for is my 2013 Nexus 7. I don't know what it is cause Ethan told me he could use your tree and kernel the way they were but they wouldn't work for me.

Either I wasn't setting everything up right, or changes were made to the android source code after you finished your tree and kernel that made it necessary to modify them. My builds would always error out with "no rule to make target" errors. Anyway, I seriously doubt that's enough info to know the cause of my problems but just throwing it out there.
 
Last edited:
I had to add a commit for the kernel for timeconst.pl to get her to build. Had to eliminate the perl warning.
here is the commit
https://github.com/dfuse06/android_...mmit/31b84adc1330460f9bac5443ef532418bc8e5217
Just waiting on Masterchief87 now!!!! :(o_O:D

d8204a1738f16f17cfd54b5794ae9e82.jpg
 
dfuse06 said:
Awesome job bro! Compiling Broken now!
Click to expand...

just to be clear, a lot of stuff still does not work, you probably have the newest version of the vendor folder, which has almost all those files from that zip still in it

I am not sure if we should try to use the latest 4.4.4 files, like b13 or what ever it was

also did you repack your botot image ?
 
hroark13 said:
just to be clear, a lot of stuff still does not work, you probably have the newest version of the vendor folder, which has almost all those files from that zip still in it

I am not sure if we should try to use the latest 4.4.4 files, like b13 or what ever it was

also did you repack your botot image ?
Click to expand...
I know a lot of the stuff doesn't work and I didn't re pack the boot img. I wanted to see what would happen. Got to optimizing apps and was able to get a log.
 
dfuse06 said:
I know a lot of the stuff doesn't work and I didn't re pack the boot img. I wanted to see what would happen. Got to optimizing apps and was able to get a log.
Click to expand...

if we are able to make a working sepolicy, the ramdisk does not need re-packing

but selinux baffles me
 
OK now I'm messing with the cm13 alpha for a while cause we're done messing with broken for the night.

@hroark13 you probably already know about most of this stuff if not all of it but I'm gonna throw it all out there in case there are any issues you have not yet noticed.
List of broken stuff I've found.
WiFi
Data/cell signal(when I try to open mobile network settings I get the message that com.android.phone has stopped and settings force closes)
Doesn't recognize sim or SD card
Bluetooth
Home button just vibrates
Can't connect to camera(changed selinux to permissive via terminal and still had same issue...used "setenforce 0" to change to permissive mode)
No sound
Tried to mount my micro USB flash drive and it didn't work with stick mount or with the option in settings(it hung up at "checking for errors)
Tried to figure out how to mount the SD card manually but couldn't figure out the correct mount point and didn't want to mess up the phone by mounting the wrong partition.

I'm going to go back to my nandroid of broken5.1.1 now and get some sleep. I'll start getting logcats and go further in depth on the next test run. If there is anything else I can do to help let me know.
 
You must log in or register to reply here.
Back
Top Bottom