CM11 ROM resetting to defaults after a reboot on Nook HD+ (Ovation) - Nook HD, HD+ Q&A, Help & Troubleshooting

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?

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.

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

whackwhack said:
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
Click to expand...
Click to collapse
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

whackwhack said:
...
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
Click to expand...
Click to collapse
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.

digixmax said:
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.
Click to expand...
Click to collapse
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 #

whackwhack said:
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 #
Click to expand...
Click to collapse
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

leapinlar said:
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
Click to expand...
Click to collapse
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.

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:

Related

Gingerbread ROMs not playing nicely with Dark Tremors apps2sd?

SOLVED.
Used another SD card that wasn't partitioned and everything works fine.
MM Gingerbread and PhoenRom both cause me to not be able to install/update/restore apps due to insufficient storage even though there is plenty of space.
If I go back to CyanogenMod everything works fine.
My SD card is partitioned 7GB Windows/1GB Linux.
Going into Settings/Applications/Downloaded shows "72MB used / 124MB free"
On SD card shows "3.2GB used / 3.3GB free"
I currently have the PhoenRom installed, this is what df now shows:
Filesystem Size Used Free Blksize
/dev 192M 32K 192M 4096
/mnt/asec 192M 0K 192M 4096
/mnt/obb 192M 0K 192M 4096
/system 145M 141M 3M 4096
/data 196M 75M 120M 4096
/cache 95M 4M 90M 4096
/system/sd 955M 26M 928M 4096
/mnt/sdcard 6G 3G 3G 4096
/mnt/secure/asec 6G 3G 3G 4096
/mnt/asec/com.android.BlackMarketApp-1 3M 1M 1M 4096
When wiping user data in recovery I get the message
E:Can't mount /dev/block/mmcblk0p2 (or /dev/bloc/mmcblk0)
(Invalid argument)
Error mounting /sd-ext/!
Skipping format
I don't know if this is significant.
Hi. I have same problem on LG Optimus One with Android 2.2.1 ... how you solve that?
So don't partition
From your brief description of "Solved" ... it sounds like you just grabbed another FAT32 formatted SD Card and just put it in. No partition setup. However from reading other posts on DarkTremor's apps2sd ... you MUST have an EXT3 formatted partition in addition to the FAT32 partition in order for apps2sd to function.
From my understanding, since the Android OS has no problems running apps from EXT2 and EXT3 partitions ... the trick is that the apps are actually moved to the FAT32 partition and shortcuts (a.k.a. links) are put on the EXT3 partitions. This tricks and Android OS into thinking the apps are installed on EXT3 and not FAT32.
Unless I am just totally missing how this works.

[Q] low space in /system

Hello
any ideas why my system directory is full?
Filesystem Size Used Free Blksize
/dev 185M 64K 185M 4096
/mnt/asec 185M 0K 185M 4096
/mnt/obb 185M 0K 185M 4096
/system 330M 319M 11M 1024
/data 1G 322M 1G 2048
/cache 61M 4M 57M 2048
/mnt/extasec 185M 0K 185M 4096
/lgdrm 2M 2M 398K 2048
/mnt/sdcard 5G 2G 2G 32768
/mnt/secure/asec 5G 2G 2G 32768
take a look in /system/app and you will understand why
ilos said:
take a look in /system/app and you will understand why
Click to expand...
Click to collapse
i know that all the files are double and odexed already....the question is how can i fix it since this is a scratch install...
just removed app that you don't want.
I always used TB to remove app that i don't need, here the result after removing some craps... ( ie LG default craps... and some live wallpapers )
here my df :
Code:
Filesystem Size Used Free Blksize
/dev 185M 64K 185M 4096
/mnt/asec 185M 0K 185M 4096
/mnt/obb 185M 0K 185M 4096
/system 338M 251M 87M 1024
/data 1G 355M 1G 4096
/cache 61M 4M 57M 1024
/mnt/extasec 185M 0K 185M 4096
/lgdrm 2M 2M 410K 2048
Rom => V20L
ilos said:
just removed app that you don't want
Click to expand...
Click to collapse
i want them all, i simply dont get it why its like this
before v20L it was about 120Mb,
could it be that the V20L just copied files over and made dups?
you used all app ? FSecure etc.... ?
ilos said:
you used all app ? FSecure etc.... ?
Click to expand...
Click to collapse
nope i froze must of them
i will just smartflash v10d and then kdz
so uninstall them in place of freezing them
ilos said:
so uninstall them in place of freezing them
Click to expand...
Click to collapse
i saw no reason to un-install when i can simply freeze them it was o.k beforehand
ahhh.... never mind.
thanks.
... or just leave it alone? Why do you need space on /system anyway?
BTW, wrong forum for general questions
Sent from my LG-P990
up
Hi all.. today I'm with this issue.. low space on system.
No issue before some installs.. I explain.
I needed to reinitialize system partition because R/W issues.. so I executed a script that make backup of system content, format it and restore contents; I used it before and it work, but this time it locks due to some errors, I think.
Reinstalled rom, reinstalled kernel (that reinit ext-4 partition if needed), re-executed the script (good execution).
When rebooted.. low space notify on system!
I think there's something is wrong.. but I don know what I need to check.. can you help me??
Just backup the apps and uninstall them. you can't keep apps n increase free space at the same time. I can't see why you want bloatwares..
That sounds odd. I would suggest to use NVFlash to start with some fresh formatted partition layout.
yea, that's there, but i'd rather not waste my time to keep bloatwares, you agree?
RknDroidFreak said:
yea, that's there, but i'd rather not waste my time to keep bloatwares, you agree?
Click to expand...
Click to collapse
Im referring to extreme who has different issues than the op. (ops post is from last year btw).
Sent from my LG-P990 using XDA

[Q] "cp: can't create '/efs/nv_data.bin': Out of memory"

Hi all,
I have an i9000 which I flashed with Orange&Samsung's Froyos and Gingerbreads, but decided to try out TeamHacksung's ICS, build 11. (I know this isn't the dev forum, but I've been very quiet and wouldn't call myself a complete noob, but haven't hit 10 posts yet)
My phone had Recovery3e rather than 2e due to the Samsung Gingerbread, so I successfully used Odin to flash CF-Root kernel and achieve CyanogenMod Recovery. The ICS and Gapps packages installed very smoothly and apart from the occasional reboot and a blank IMEI, it's good.
I have ADB installed on my ArchLinux machine (not a noob, lol) but when I try to restore my EFS backup I get this message:
Code:
[email protected]:/emmc/Galaxy_S_Unlock/efs # cp nv_data.bin /efs/nv_data.bin
cp: can't create '/efs/nv_data.bin': Out of memory
1|[email protected]:/emmc/Galaxy_S_Unlock/efs #
I thought this might be a space issue, so I checked DF, and found /efs was at 12MB/12MB.
My next command was
Code:
rm -r /efs/*
and the output was
Code:
rm failed for /efs/lost+found, Is a directory
ok, busybox's rm doesn't use the same args as linux rm...
I tried rebooting the phone but /efs still contains only lost+found, not even a nv_data for dummy IMEI.
my curent status is
Code:
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 163M 32K 163M 4096
/mnt/asec 163M 0K 163M 4096
/mnt/obb 163M 0K 163M 4096
/system 250M 203M 46M 4096
/cache 17M 2M 15M 4096
/radio 16M 14M 1M 4096
/data 1G 188M 1G 4096
/datadata 172M 27M 144M 4096
/efs 12M 12M 0K 4096
/mnt/emmc 1G 755M 1G 32768
/mnt/sdcard 5G 1G 4G 4096
/mnt/secure/asec 5G 1G 4G 4096
[email protected]:/ # cd /efs
[email protected]:/efs # ls
lost+found
[email protected]:/efs #
What should be my next step?
I just lost and restored my efs folder with success. You need to make some room. The phone is always making backups.
First download "spoof firmware" from the market and backup your efs folder just in case.
Now using root explorer delete older backups of your file in question to make room. If anything goes wrong just restore efs backup and set permissions to rw-rw-rw and most important both owners to radio.
** JetMOD, Talon & ThunderBolt **
Ok, flashed Stock JVT with repartition then CF-Root and got the IMEI back. Will try TH's ICS Build11 again tomorrow. I'll take another EFS backup using ADB too and try your method if the problem reoccurs and I still can't restore EFS.
Strange this is the first time I've read about a blank IMEI, most IMEI problems appear as some kind of dummy number with zeroes at the end.
Ok, starting from JVT+CF,
Flashed Build 11 using CF's ClockWork Recovery, got Bootloops this time.
Maybe I need to start from something between JVO and JVT!!

Internal memory and partition...

Hi Guys,
Every time I tried to understand the android partitions I get more confuse. Let me clear my doubts. These are based on CyanoGenMod 9/10 and Galaxy S I9000 ....
This is how the partition exists in CyanoGenMod.....
We have a very fast NAND which is 512MB. This memory shared between /cache, /system, /datadata, /modem etc.
Then we have a flash memory which is either 8GB or 16 GB. This one partitioned into 2.
2GB for /data
6GB or 14GB for /sdcard
Question 1
So normally all your Apps are installed into the /data partition?
Question 2
In that case can I say MoveToSD means moving the Apps to the /sdcard partion?
Question 3
I noticed that for each application I move to SD I see a entry in "/mnt/asecure" . What's the use of it?
Last week I bought a Galaxy S3 because I thought I need a hardware beast. (I was really enjoying and still enjoying the Galaxy S with Cyanogen) And using "df" commands partitions are as follows....
/dev 896M 84K 896M 4096
/mnt/asec 896M 0K 896M 4096
/mnt/obb 896M 0K 896M 4096
/efs 19M 4M 15M 4096
/cache 1007M 17M 990M 4096
/system 1G 1G 463M 4096
/data 11G 4G 6G 4096
/firmware 199M 45M 154M 4096
/tombstones 251M 18M 233M 4096
/storage/sdcard0 10G 4G 6G 4096
/mnt/asec/ch.teamtasks.tasks.paid-1 4M 2M 1M 4096
/mnt/asec/com.disney.brave_google-1 26M 25M 1M 4096
/mnt/asec/com.touchtype.swiftkey-1 14M 10M 3M 4096
Question 4
Can someone explain this partition? why the /data shows as 11GB. And /sdcard0 is 10GB. I'm not quite sure my phone is 16GB model and it's not possible to have that much memory for /data.
Question 5
In this layout when I install Apps where it will get installed? I haven't root it yet so I cannot test.
Question 6
In this layout what is the meaning of MoveToSd could be? Samsung removed that option but I believe somehow it gets applied. Because I have plenty of Apps installed but some apps have a "mnt/asec" entry similar to Android secure. So is it similar are these apps get moved to /sdcard0 partition.
I'm developing some apps at the same time I'm trying to understand the core concepts with Android. Any guideline will be helpful and I really appreciate the replies. Thanks in advance....
wrong section
you should have posted this under Q&A!

[Q] I/O error - possible bricked phone

While trying to gain s-off (i downgrade from 2.24 to 1.29) and everything looked ok. I was able to boot into android, and la di da.
I then followed the instructions (or so I believe) to gain s-off using revone.
It was stuck for a while, during the process so I thought it hung so I did what I definitly should not have done. Ctrl-C. *dramatic music*. The phone behaved a bit finicky, and I forced a reboot by pressing power. It took much longer than before. Since then, I can not get the display to work, and I get flashing back and home buttons when I do (as if Im trying to force restart).
however...
My usb seems to be working, and I can adb in.
But...
I cannot reboot device nor can I get into recovery.
I get a ... " sh: reboot: i/o error"
I did a df to see what partitions were available
1|[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 783M 128K 783M 4096
/mnt/asec 783M 0K 783M 4096
/mnt/obb 783M 0K 783M 4096
/system 1G 1G 379M 4096
/data 25G 19G 5G 4096
/cache 629M 16M 613M 4096
/devlog 19M 14M 4M 4096
/data/qcks 20M 8M 11M 4096
/data/efs 20M 768K 19M 4096
/data/secure/data 783M 0K 783M 4096
/firmware/mdm: I/O error
/firmware/q6: I/O error
/storage/sdcard0 25G 19G 5G 4096
same IO error keeps popping. firmware..lol...that seems important
So, is there anything I can do. Im sure if I can get into recovery, I can figure out the rest, but right now, im kind of typing blind (yes, i know, that's what got me here in the first place lol)
I managed to get into recovery.
I was trying within the adb shell to reboot. I just tried 'adb reboot recovery' and it worked.
Now to finally try and figure this out...
**update**
Ok I got it working.
In recovery, I reflashed the RUU and tried the procedure again and everything worked out. I got S-OFF and then restored to my the ROM i was using.

Categories

Resources