[ROM][OFFICIAL][Wi-Fi] CyanogenMod 13

[steslatt]

I don't know why the setup wizard crashes - i had the same problem - but you can delete the wizard and skip the problems.
In TWRP mount system. Then go to system/priv-app and delete settingwizard.apk
When booting into Android you just go to the settings and add you account.

That is what i did last week - and it worked.
A few days later i flashed Dirty Unicons ROM and Banks gapps.
No problems with crashing setup wizard.

Ok this worked, I've been able to boot to the home screen but now play store and play services crash repeatedly so I am unable to use the device.

---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------

CM comes with an integrated root.

Flash latest vendor.img from stock Android.
Flash TWRP.

From within TWRP: Reset, flash cm followed by opengapps or whatever.

Tried this, it doesn't work, I just get the same issue.

 

[dmantilal]

Tried this, it doesn't work, I just get the same issue.

Try a different gapps package.

Also, make sure to confirm the md5/sha1 checksums to ensure your downloaded Android files are error free.

 

[steslatt]

Try a different gapps package.

Also, make sure to confirm the md5/sha1 checksums to ensure your downloaded Android files are error free.

I've tried open gapps arm64 nano and stock, both with verified md5. Neither of them work.

 

[vl319]

I've tried open gapps arm64 nano and stock, both with verified md5. Neither of them work.

I have this problem too last night after updatebto latest nightly. I just cant boot into home screen as google services error keep appear on the screen. I already flashed latest vendor image but no luck. Prior to flashing opengapp i was able to boot into home screen. Right after flashing opengapp the errors occur. I think opengapp is the culprit

 

[steslatt]

I have this problem too last night after updatebto latest nightly. I just cant boot into home screen as google services error keep appear on the screen. I already flashed latest vendor image but no luck. Prior to flashing opengapp i was able to boot into home screen. Right after flashing opengapp the errors occur. I think opengapp is the culprit

I have given up now. Tried everything, I just can't get it to work with any gapps at all. Flashed dirty unicorns and it works perfectly first time. It's something to do with cm13 and gapps.

 

[dmantilal]

I have given up now. Tried everything, I just can't get it to work with any gapps at all. Flashed dirty unicorns and it works perfectly first time. It's something to do with cm13 and gapps.

What alternative gapps did you use?

I just installed the cm13 snapshot with opengapps pico and I am having the same problem as you. I had this problem with opengapps 2 or 3 times and a different gapps fixed it.

 

[dmantilal]

I have given up now. Tried everything, I just can't get it to work with any gapps at all. Flashed dirty unicorns and it works perfectly first time. It's something to do with cm13 and gapps.

Update: I deleted the settingwizard.apk like @Lar5 said and everything worked fine.


(Talking out my ass here...) I noticed that while opengapps is flashing, it preemptively optimizes/de-odexes (?) settingwizard.apk app, so the app's folder additionally had a dex file and an oat folder when other apps had only the apk. Could that be the cause for the crash?

 

[steslatt]

Update: I deleted the settingwizard.apk like @Lar5 said and everything worked fine.


(Talking out my ass here...) I noticed that while opengapps is flashing, it preemptively optimizes/de-odexes (?) settingwizard.apk app, so the app's folder additionally had a dex file and an oat folder when other apps had only the apk. Could that be the cause for the crash?

Yeah I deleted the whole folder but I got constant crashes with play store and play services instead. I've tried 2 other sets of gapps from dirty unicorns and they didn't work either, I've forgot the names of them now.

---------- Post added at 01:16 PM ---------- Previous post was at 01:13 PM ----------

What alternative gapps did you use?

I just installed the cm13 snapshot with opengapps pico and I am having the same problem as you. I had this problem with opengapps 2 or 3 times and a different gapps fixed it.

What's cm13 snapshot? I've just been using the latest nightly

 

[dmantilal]

Yeah I deleted the whole folder but I got constant crashes with play store and play services instead. I've tried 2 other sets of gapps from dirty unicorns and they didn't work either, I've forgot the names of them now.

---------- Post added at 01:16 PM ---------- Previous post was at 01:13 PM ----------


What's cm13 snapshot? I've just been using the latest nightly

CyanogenMod Snapshot

It is the stable version of CyanogenMod that is released every few months.

 

[dumdum2]

Screen lock doesn't work, you can only use NONE or SWIPE, if you define a pattern it doesn't work....any solution?

 

[kak4rot]

What is the actual STOCK ROM Firmware Required for the last nightlys? Is for avoid the missmatching vendor.img error at booting

 

[tibere86]

What is the actual STOCK ROM Firmware Required for the last nightlys? Is for avoid the missmatching vendor.img error at booting

MHC19Q :good:

 

[kak4rot]

MHC19Q :good:

MHC19Q? There isn't any MHC19Q factory image version for nexus 9. The last one is MOB30D and with this version a get the error: "There’s an internal problem with your device" at startup on the last nightly

 

[Bastlwastl2010]

"There’s an internal problem with your device" at startup on the last nightly

This will fix it:

http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347

 

[placebo_domingo]

MHC19Q? There isn't any MHC19Q factory image version for nexus 9.

MHC19Q :good:

MHC19Q is for Nexus 6p not for Nexus 9, in case anyone's confused. :silly:

 

[razorloves]

MHC19Q? There isn't any MHC19Q factory image version for nexus 9. The last one is MOB30D and with this version a get the error: "There’s an internal problem with your device" at startup on the last nightly

This will fix it:

http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347

That is not a fix. That just hides the warning message. To correctly fix it, you have to flash the vendor img that matches the version rom you're using. Having the wrong vendor img means you're using the wrong binaries/drivers, which will likely result in bugs/issues.

 

[kak4rot]

And what is the correct vendor.img that match last nightly?, I don't find any information about it, I have tried with version showed in the first page of this post, but I keep on getting the error message at startup

 

[razorloves]

And what is the correct vendor.img that match last nightly?, I don't find any information about it, I have tried with version showed in the first page of this post, but I keep on getting the error message at startup

https://github.com/CyanogenMod/android_device_htc_flounder/blob/cm-13.0/cm.mk#L42

and the snapshot that came out last month uses the same.
https://github.com/CyanogenMod/android_device_htc_flounder/blob/stable/cm-13.0-ZNH0E/cm.mk#L42

 

[kak4rot]

Thanks a lot!

 

[sketchman16]

Anybody else's camera not working with latest nightlies?

Also, I tried the last snapshot, and I get the same issue. Also present in Dirty Unicorns. However if I flash the Google images the camera works fine. Going to try to flash another 3rd party again, and see if it magically works there too now.