I think we might won't get CM13 from current maintainer rmcc, because he only fixed critical bug after months in cm12.1 and other upstream code wasn't merged on geular basis. Also there might be some more hacks needed for cm13 gproj and he might don't want to spend time on that, but official or not doesn't matter. Let's see.
/* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
Good job mate. About the sim pin I think @dadi11 has already fixed it.I may have found the problem for the 'SetupWizard' crash.
In the process of bugtracking I set selinux to 'permissive', so I wouldn't have to bother SeLinux during bugtracking.
Strangely after setting Selinux to permissive I was able to clear the 'SetupWizard' without any troubles.
So my suspicion is there may be some permission problems due to Selinux.
I'll investigate this matter a little more in the coming days.
Update 1: I can confirm I was right in my findings.
Selinux blocked some requests which were needed for the SetupWizard.
I'll upload the patches to the CyanogenMod Gerrit and then hopefully they will be pushed upstream very soon.
The next thing to investigate will be the Pin problem. Unfortunately this doesn't seem to be a permission problem.
I've seen some hints in the logs which may give some clues on what is going on, but it's too early to base any conclusions on those findings.