[ROM] [ZTE Z7MAX] [Android 5.1.1] CM 12.1 unofficial

[securecrt]

I also have problems while doing the update from V11 to V12.
I flash the V12 over V11 and also flashed the radio 357 in recovery, then I reboot the phone.
after long time waiting (android updating , apps optimization) the phone reboot by itself and enter boot loop....

I am downgrade the radio to 356 and still trying to see what will happen...

[securecrt]

I have the same problems as you.

[migel121]

a full wipe has not helped the Baseband 357 it can not but be that I had already on it, I had the feeling of the touchscreen is not responding.

[securecrt]

a full wipe has not helped the Baseband 357 it can not but be that I had already on it, I had the feeling of the touchscreen is not responding.

I am also failed after doing the full wipe on V12 + radio 357 or 356

[PaoloW8]

lol...I don't know why...to me it working well since yesterday
check if md5 is correct:

paolo@LinuxPC:~/Android/cm12.1/out/target/product/nx505j$ md5sum cm-12.1_nx505j-20150915-Rel_V12.zip 
657c89a31fd77b93b6a2605b97f1dc7c  cm-12.1_nx505j-20150915-Rel_V12.zip

anyway, for the moment stay with the V11 meanwhile I do some checking
(baseband 357 can be used with V11)

[inigoml]

Tested radio 3.57 with V11. Everything running without problem.
It appear to be a problem with V12 only. Perhaps only if coming from V11 without full wipe, but today I'm very lazy to perform a full wipe... :-)

[securecrt]

lol...I don't know why...to me it working well since yesterday
check if md5 is correct:

paolo@LinuxPC:~/Android/cm12.1/out/target/product/nx505j$ md5sum cm-12.1_nx505j-20150915-Rel_V12.zip 
657c89a31fd77b93b6a2605b97f1dc7c  cm-12.1_nx505j-20150915-Rel_V12.zip

anyway, for the moment stay with the V11 meanwhile I do some checking
(baseband 357 can be used with V11)

I have double checked the md5 it is same as yours.

now I will stay on the V11 + Radio 357.

[PaoloW8]

Tested radio 3.57 with V11. Everything running without problem.
It appear to be a problem with V12 only. Perhaps only if coming from V11 without full wipe, but today I'm very lazy to perform a full wipe... :-)

don't try
on my phone...update from V11 (with only wipe cache and dalvik) works well
but now I tried with a full wipe and I have the bootloop
so....I try to understand what is the problem

[inigoml]

don't try
on my phone...update from V11 (with only wipe cache and dalvik) works well
but now I tried with a full wipe and I have the bootloop
so....I try to understand what is the problem

If syncing from CM12.1 trunk, It could be a CM issue. Sometimes these things happen with mainstream...

[PaoloW8]

I have fixed the bootloop problem
with the new build id the kernel need some patch

so...I started a new kernel from scratch with the latest codeaurora compatible version (https://www.codeaurora.org/cgit/quic...LA.BF.1.1.1.c5)
now I have to add all the features that I had put into the old kernel