[Moto Maxx Android Development] fgl27:
There is a possible relation between reboot and those error after all you try to use a app with faulty files it will cause a problem and that may be a reboot, the com.google.android.gms is google app used a lot by others app and if that is with problem that is a big problem...

I recommended a even older gapps pack... after all the problem seems to start this week so test the one from two may more weeks ago

"I just can't wipe cache/dalvik." don you see your on pic from yours previously post, the wipe finished just fine, the data is unmounted and mount after the wipe of any partition, and there is the problem not in the wipe of cache or dalvik.

if the partition is formated with F2FS during boot the kernel will check for error you can see this in Driver message log (dmesg):

[ 2.647539,0] fs_mgr: Running /system/bin/fsck.f2fs [COLOR="Red"]-a[/COLOR] /dev/block/platform/msm_sdcc.1/by-name/userdata
[ 2.809054,0] fsck.f2fs: Info: Fix the reported corruption.
[ 2.809054,0]
[ 2.809182,0] fsck.f2fs: Info: sector size = 512
[ 2.809182,0]
[ 2.809246,0] fsck.f2fs: Info: total sectors = 111689472 (54535 MB)
[ 2.809246,0]
[ 2.809305,0] fsck.f2fs: Info: MKFS version
[ 2.809305,0]
[ 2.809371,0] fsck.f2fs: "Linux version 3.10.101-BHB27-kernel-V1.2.9-8-M (bhb27@baybutcher27-Android) (gcc version 4.8.5 (UBERTC-4.8.5) ) #1 SMP PREEMPT Fri Jun 3 12:31:52 BRT 2016"
[ 2.809371,0]
[ 2.809429,0] fsck.f2fs: Info: FSCK version
[ 2.809429,0]
[ 2.809494,0] fsck.f2fs: from "Linux version 3.10.104-SliN_BHB27_Kernel_1.4 (bhb27@Android) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Nov 24 03:48:55 BRST 2016"
[ 2.809494,0]
[ 2.809559,0] fsck.f2fs: to "Linux version 3.10.104-SliN_BHB27_Kernel_1.4 (bhb27@Android) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Nov 24 03:48:55 BRST 2016"
[ 2.809559,0]
[ 2.809617,0] fsck.f2fs: Info: superblock features = 0 :
[ 2.809617,0]
[ 2.809678,0] fsck.f2fs: Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
[ 2.809678,0]
[ 2.809736,0] fsck.f2fs: Info: total FS sectors = 111689440 (54535 MB)
[ 2.809736,0]
[ 2.809793,0] fsck.f2fs: Info: CKPT version = 46a9e
[ 2.809793,0]
[ 2.809849,0] fsck.f2fs: Info: No error was reported

if it finished with "fsck.f2fs: Info: No error was reported" that is the result no error for me and that must be to all of you the problem is a corrupted or something else cause by a faulty gapps file in data.

the same can be done in TWRP but is need to unmount data (or the partition to test) first

the result display is different but the same

~ # fsck.f2fs [COLOR="Red"]-a[/COLOR] /dev/block/platform/msm_sdcc.1/by-name/userdata
Info: Fix the reported corruption.
Info: sector size = 512
Info: total sectors = 111689472 (in 512 bytes)
Info: MKFS version
"Linux version 3.10.101-BHB27-kernel-V1.2.9-8-M (bhb27@baybutcher27-Android) (gcc version 4.8.5 (UBERTC-4.8.5) ) #1 SMP PREEMPT Fri Jun 3 12:31:52 BRT 2016"
Info: FSCK version
from "Linux version 3.10.104-SliN_BHB27_Kernel_1.4 (bhb27@Android) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Nov 24 03:48:55 BRST 2016"
to "Linux version 3.10.104-BHB27-kernel-V2.0.2-4-M (bhb27@Android) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Tue Oct 25 00:33:31 BRST 2016"

[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Ok..] [0x7e8908]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0x4937]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x4937]
[FSCK] valid_inode_count matched with CP [Ok..] [0x295a]
[FSCK] free segment_count matched with CP [Ok..] [0x2a07]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Ok..]

all OK

instead of use -a, -f can be used

-a check/fix potential corruption, reported by f2fs

-f check/fix entire partition

----------

This corrupted files can be the cause of reboot that some users report I have no idea way they are happening and the ROM can't be the problem, if it was the problem must be in all app and I only see google app with problem and only some user with the problem...

Try to use old gapps if the problem persist try to not use gapps is possible I already explain how unfortunately some app are gapps depended but most are not

I will try to search to see if I can find a cause or a solution for the problem, if anyone find a real cause let me know in the thread...