I think TWRP have a fix permission feature. Maybe you can try, sir.It doesnt work. I get the message again.
No problem here..and the SytemUI Crash comes again too
Try rebootingAnyone else have this problem? Change themes to one with wallpapers/lockscreen wallpapers, then change back to System Default, and then change you wallpaper in Launcher3. Lockscreen still has default CM wallpaper.
Nope. Still stuck on default background on the lockscreen.Try rebooting
Yes, I had crash when trying to change keyboard, for exampleI can't add any keyboard Google keyboard or vocal keyboard i encounterd error message ....
Are you re-flashing gapps every time? That would cause this.1) On all nightlies i tried each time i update i lose all my apps updates and need to update them again from begining.
Need some help here couse no clue if its CM Rom or my Philz Touch CWM Recovery?
I tried again and followed these steps exactly, once with @knizmi 's build and once with the new Jan 19th nightly build. Albeit I used TWRP 2.8.3.0 again since I only have TWRP backups. I'm not sure if it's even possible to restore TWRP backups with cwm, is it? Unfortunately no success, I waited for more than 10 minutes both cases and was still stuck in the boot animation. Thanks again for the exact steps though, it was worth trying.In which order did toy flashed and restored ?
I think you should do the following :
- go to recovery (cwm-based is better in that specific case)
- wipe /system, /data, /cache
- restore the backup
- do NOT reboot out anything
- flash @knizmi 's build and then gapps
- reboot
- wait for 10 minutes
- should work
![]()
I agree, it's a bit disconcerting. For me it also looks like Nandroid backups could be unreliable right now, at least in some circumstances (CM12, TWRP, Falcon, ...?). Any other experiences?My biggest concern is caused by this chain of facts:
[...]
These means to me that nandroid backups of CM12, right now, are unusable, on my phone at least.