CM11 ROM resetting to defaults after a reboot on Nook HD+ (Ovation)

[whackwhack]

I'm currently running (and want to keep running) a CM nightly build (cm-11-20151122-NIGHTLY), though the issue isn't ROM specific to CM.
I've got a HD+ (Ovation) running TWRP recovery and CM11 nightly 20151122.

Again this isn't Cyanogenmod specific because the behavior occurred with two other non-CM ROMs.

After flashing and rebooting, the ROM boots fine as expected. It prompts you for WIFI info, Google account credentials, etc and gives you the two-step wizard about the launcher and widgets, all is fine.
Then you reboot the device for any reason (cold power off, software shutdown, software reboot, etc), the ROM is back to acting like you just flashed it again.
After the reboot, you're prompted to go through the whole setup wizard, no changes to icon positions, etc are saved in the OS.

I'm guessing it's something noob-ish like bad permissions somewhere that cause it to reset with each reboot. It was doing this before with a custom ROM that my friend (who I got the device from) was running. We assumed it was just that ROM being screwy.

I've spent quite a while this morning already Googling around, because it seems like it's probably something simple, but my results are heavily fuzzed by a million tutorials on how to boot into recovery mode or factory-reset the device.

Suggestions?

 

[digixmax]

I'd suggest you try re-flashing CM11 and GApps using CWM v6.0.x.y (e.g., v6.0.4.6). Make sure that you use a GApps package that is compatible with CM11/Android v4.4 see http://wiki.cyanogenmod.org/w/Google_Apps), and do "wipe /data & factory reset" before flashing the ROM and GApps zip files. See http://forum.xda-developers.com/showthread.php?t=2317500 and/or http://forum.xda-developers.com/showthread.php?t=2679899 for more info/pointers.

 

[whackwhack]

The reflashing works, regardless of what ROM I use (CM or any random custom one from XDA), so I don't think the flashing process is at fault. Whichever ROM I use, it flashes correctly and boots, but after I go through the initial setup and reboot, the installed ROM reverts to its post-flash I-need-my-initial-setup state.

The problem occurs when I install no additional software from recovery mode (i.e. GApps) as well as when I do install GApps.
I have been doing the full wipe of all storage locations (dalvik cache, system, data, internal storage, and cache) before flashing, each time.

I'm beginning to suspect the onboard storage is screwed up somehow. Since I posted last, I've noticed Android and Windows both see the thing as having 128mb of storage total.
i.imgur.com/U6LUmmI.png
i.imgur.com/GXn8Ytq.jpg

 

[leapinlar]

The reflashing works, regardless of what ROM I use (CM or any random custom one from XDA), so I don't think the flashing process is at fault. Whichever ROM I use, it flashes correctly and boots, but after I go through the initial setup and reboot, the installed ROM reverts to its post-flash I-need-my-initial-setup state.

The problem occurs when I install no additional software from recovery mode (i.e. GApps) as well as when I do install GApps.
I have been doing the full wipe of all storage locations (dalvik cache, system, data, internal storage, and cache) before flashing, each time.

I'm beginning to suspect the onboard storage is screwed up somehow. Since I posted last, I've noticed Android and Windows both see the thing as having 128mb of storage total.
i.imgur.com/U6LUmmI.png
i.imgur.com/GXn8Ytq.jpg

It looks like your partition 10 (/data) is hosed. Go to my HD/HD+ stock tips thread linked in my signature and look at item 16 to see the partition structure of the device. You might be able to fix the partition somehow.

Sent from my SM-T707V using XDA Premium HD app

 

[digixmax]

...
I'm beginning to suspect the onboard storage is screwed up somehow. Since I posted last, I've noticed Android and Windows both see the thing as having 128mb of storage total.
i.imgur.com/U6LUmmI.png
i.imgur.com/GXn8Ytq.jpg

If you can access the Android Terminal Emulator app (which comes with the CM ROM package), you can find out how much of your HD+ storage is currently allocated for the /system, /data, and /cache partitions. The default allocation on my HD+ is showed in the attached screenshot.

 

[whackwhack]

If you can access the Android Terminal Emulator app (which comes with the CM ROM package), you can find out how much of your HD+ storage is currently allocated for the /system, /data, and /cache partitions. The default allocation on my HD+ is showed in the attached screenshot.

I got it connected up via ADB to my work machine. Here's what I see. I haven't crossreferenced this with what @leapinlar says in his guide thread my partition table SHOULD look like.

[email protected]:/mnt # df
Filesystem Size Used Free Blksize
/dev 391.3M 136.0K 391.2M 4096
/sys/fs/cgrou 391.3M 12.0K 391.3M 4096
/mnt/asec 391.3M 0.0K 391.3M 4096
/mnt/obb 391.3M 0.0K 391.3M 4096
/mnt/fuse 391.3M 0.0K 391.3M 4096
/system 661.4M 358.6M 302.8M 4096
/data 128.0M 66.2M 61.8M 4096
/mnt/shell/emulated 128.0M 66.2M 61.8M 4096
/mnt/media_rw/sdcard1 1.9G 608.0K 1.9G 32768
/storage/sdcard1 1.9G 608.0K 1.9G 32768
[email protected]:/mnt #

 

[leapinlar]

I got it connected up via ADB to my work machine. Here's what I see. I haven't crossreferenced this with what @leapinlar says in his guide thread my partition table SHOULD look like.

[email protected]:/mnt # df
Filesystem Size Used Free Blksize
/dev 391.3M 136.0K 391.2M 4096
/sys/fs/cgrou 391.3M 12.0K 391.3M 4096
/mnt/asec 391.3M 0.0K 391.3M 4096
/mnt/obb 391.3M 0.0K 391.3M 4096
/mnt/fuse 391.3M 0.0K 391.3M 4096
/system 661.4M 358.6M 302.8M 4096
/data 128.0M 66.2M 61.8M 4096
/mnt/shell/emulated 128.0M 66.2M 61.8M 4096
/mnt/media_rw/sdcard1 1.9G 608.0K 1.9G 32768
/storage/sdcard1 1.9G 608.0K 1.9G 32768
[email protected]:/mnt #

Yeah, your /data is way too small. Depending which model you have it should be at least 5G.

Sent from my SM-T707V using XDA Premium HD app

 

[whackwhack]

Yeah, your /data is way too small. Depending which model you have it should be at least 5G.

Sent from my SM-T707V using XDA Premium HD app

Yep that's my assessment too.
Great.
How the hell do I fix it without screwing things up worse? Looks like it's the 16gb model (BNTV600)
I've got it hooked up to my PC via ADB currently, but I'm not about to fdisk anything without having a plan.

 

[whackwhack]

Nevermind I figured it out. The partition was formated F2FS. I reformatted it EXT4 and it formatted at the true capacity (shows about 12.5 gb free).
Changes now persist across reboots.
Thanks for the pointers in the right direction, everyone
:highfive: