Database Develop

[Q] Help getting any rom to run off internal

Ok, backstory, picked up this Nook Color on craigslist, came with Honeycomb v4 on microSD, booted fine into that, but without uSD would boot to 'n' screen and freeze/stall. Got another uSD formatted with CWM Recovery and the clean original nook image to try and load that from scratch. While following the instructions to restore the original image I would get errors while trying to format system and data (something to the effect of Error cannot format system/!). So I tried to install both CWM to the internal and CM7 to the internal and both would say install complete from microSD, but when booting without the uSD, it would still try to boot into the original nook software and hand on the 'n'.
I tried this to see if my partitions were messed up, but I had the same partition structure and size as it should be (according to the post):
http://forum.xda-developers.com/showthread.php?p=13003431#post13003431
Possibly because I ran this "repartition-boot-with-stock" from this post:
http://forum.xda-developers.com/showthread.php?t=914690
Please help, would prefer to run this off the internal!
Got CM7 running off yet another microSD with this thread:
http://forum.xda-developers.com/showthread.php?t=1000957

Assuming the partition table is in tact then try formatting /system /data /cache in Clockworkmod.
If that doesn't work if might be time to entertain the possibility that you were sold a Nook with a bad emmc.
Sent from my NookColor using XDA App

When I try to format /system /data /cache in CWM, I get an error message. What is the function of the emmc?

mattdogg02 said:
When I try to format /system /data /cache in CWM, I get an error message. What is the function of the emmc?
Click to expand...
Click to collapse
Putting it in PC terms, the emmc functions as the ROM for the bios, and as the solid state drive for whatever you're running on internal memory.
(What is the term for the tablet/smartphone equivalent of the "bios"?)

akaCat said:
(What is the term for the tablet/smartphone equivalent of the "bios"?)
Click to expand...
Click to collapse
Bootloader.
As to the OP - It's still possible your internal flash is bad but the fact that you can list your partition table gives me hope that isn't the case.
I read through JoJa15's post you linked in "Dummies Guide to Fixing 'My Nook Won't Boot'" - It sounds like you listed your partition table per his post and found that it matched what he posted but didn't modify anything right?
The fact that your partition table appears to be in tact is good but the contents of those partitions could be complete gibberish which may explain why CWM errors out when trying to format them. What is the exact error CWM is giving?
I think the next "safe" step is to have a look at DeanGibson's post here: http://forum.xda-developers.com/showthread.php?t=1094371
Dean's CWM scripts will essentially blow away partitions 6-8 (/data / cache and /emmc) and re-create them. If your problem happens to be in one of those partitions then his tool may be a quick fix without having to play with fdisk. That said, I doubt it will work since you can't format /system (partition 5) and his tool doesn't touch the /system partition.
At that point you are pretty much left playing with fdisk, unless you can sweet talk DeanGibson into putting together a CWM flash that will re-do partitions 4 and 5 (extended partition and /system partition) which he may do.
From there it boils down to how comfortable you are with the Linux commands dd and fdisk...?
Good Luck,
Martian21

Ok, followed Dean's instructions with the packages from his post, but still no go.
The error I'm getting when going to Mounts and Storage Menu and running the format /system /data /cache options are:
ClockworkMod Recovery v3.0.2.8
Formatting /system...
Error formatting /system!
Formatting /data...
Error formatting /data!
Formatting /cache...
Error formatting /cache!
Really want to try and get this resolved as I want to install stuff onto the internal!

No one with any other advice on this?

mattdogg02 said:
No one with any other advice on this?
Click to expand...
Click to collapse
Your previous post showed that you were using clockworkmod recovery v3.0.2.8, that version does not have support for the “blue dot” NC. Not knowing for sure if your NC is really a “blue dot” or an original one, I would follow these steps.
1. Create a bootable CWM v3.2.0.1 SD card using the image located HERE. The instructions for it are located HERE. I know the post says v3.0.2.1, but it is miss-marked.
2. Once the card is made, download the repartitioning files located HERE, and the stock 1.2 image file “update-nc-stock-1.2-signed.zip” located HERE.
3. Put all those zip files onto the SD Card
4. Shut down the NC
5. Insert and start the bootable SD card
6. Follow the directions to flash the repartitioning files
7. Once that completes, flash the stock 1.2 image
8. When that is done, remove the SD card, and reboot the device
Hopefully at this point, you will be booting into a stock 1.2.0 system. You can now do whatever you want with the device.

Nook Color CM10 emmc Data Partition Size

Loving the CM10 ROMs. Everything has been snappy on my nook since beta 2.
I thought I had the newer (revision 1.2+) nook partition layout (5gb data(apps)/1gb media). But now with CM10 I am getting an out of space error when trying to install new apps. I have moved all apps to my sd card and still get the error about not enough space. If I try and look at the partiton size it looks like it is maybe only 1gb now. Did installing a CM10 ROM change my partition size? Am I missing something else? Perhaps I am just wrong about my original partition sizes.
I searched some threads and the web and saw some discussion on my issue, particularly mention of a 'new CM10 partition layout', but this was confusing at best. It may not have even been nook related, but pertained to some phones.

dcahoe said:
Loving the CM10 ROMs. Everything has been snappy on my nook since beta 2.
I thought I had the newer (revision 1.2+) nook partition layout (5gb data(apps)/1gb media). But now with CM10 I am getting an out of space error when trying to install new apps. I have moved all apps to my sd card and still get the error about not enough space. If I try and look at the partiton size it looks like it is maybe only 1gb now. Did installing a CM10 ROM change my partition size? Am I missing something else? Perhaps I am just wrong about my original partition sizes.
I searched some threads and the web and saw some discussion on my issue, particularly mention of a 'new CM10 partition layout', but this was confusing at best. It may not have even been nook related, but pertained to some phones.
Click to expand...
Click to collapse
You can tell by looking in settings and storage. It will tell you the size of your media storage. If you truly have the 1Gb /data, you might want to look at Dean Gibson's repartitioning thread. He has a 2gb/4gb version.
And no, there is no repartitioning that cm10 does. That was for a phone you saw.
Sent from my Nook HD+ running Tapatalk

Well, I think I do have the 5gb data/1gb media partition layout afterall.
In Setting->Apps->Downloaded it shows at the bottom 'Internal Storage, 753Mb used, 4.2Gb free'.
If I launch a terminal window:
$ df /data
/data Size=4G Used=643M Free=4G Blksize=4096
$ df /emmc
/emmc Size=1G Used=83M Free=942M Blksize=4096
$ df /mnt/sdcard
/mnt/sdcard Size=15G Used=10G Free=4G Blksize=8192
I guess the only app that is giving me the out of space is Titanium Backup. I can't get it to install from either the appstore or from .apk that I downloaded. Both methods start installing and then say 'out of space'. I have been installing and removing other apps along the way with no similar problem.
I did wipe cache/dalvik cache when installing ROM. I also tried CWM Fix Permissions. I also tried CWM Backup -> Wipe Data/Factory Reset -> Restore.
Anyone know why Titanium Backup won't install?

dcahoe said:
Well, I think I do have the 5gb data/1gb media partition layout afterall.
In Setting->Apps->Downloaded it shows at the bottom 'Internal Storage, 753Mb used, 4.2Gb free'.
If I launch a terminal window:
$ df /data
/data Size=4G Used=643M Free=4G Blksize=4096
$ df /emmc
/emmc Size=1G Used=83M Free=942M Blksize=4096
$ df /mnt/sdcard
/mnt/sdcard Size=15G Used=10G Free=4G Blksize=8192
I guess the only app that is giving me the out of space is Titanium Backup. I can't get it to install from either the appstore or from .apk that I downloaded. Both methods start installing and then say 'out of space'. I have been installing and removing other apps along the way with no similar problem.
I did wipe cache/dalvik cache when installing ROM. I also tried CWM Fix Permissions. I also tried CWM Backup -> Wipe Data/Factory Reset -> Restore.
Anyone know why Titanium Backup won't install?
Click to expand...
Click to collapse
The only thing I can think of is some users are having read only problems on both SD card and /data, which is where apps get installed. Have you tried to install other apps since the TB install failed? A test you can try to see if you are one of the users with ro issues is to use a root file manager (there is one built into CM10 now) to create a test file somewhere on /data.
Sent from my Nook HD+ using Tapatalk

[Q] Missing /sdcard mount (milaq nightly)

Hey folks,
I have recently replaced my older Evervolv on the Touchpad with a current Milaq Nightly, and for some reason it doesn't mount the internal SDcard partition (worked fine with Evervolv).
When I 'mount -t vfat /dev/mapper/store-media /sdcard' manually, it works fine and I can see the files in there, so the file system apparently is intact, but Android doesn't seem to recognize it as usable SDcard storage (i.e. no "move to SD" option in the app manager etc). The mount doesn't persist across reboots either, and adding an entry to /fstab.tenderloin is equally pointless.
Any hints on what could it be that prevents my device from automounting this partition?

WooShell said:
Hey folks,
I have recently replaced my older Evervolv on the Touchpad with a current Milaq Nightly, and for some reason it doesn't mount the internal SDcard partition (worked fine with Evervolv).
When I 'mount -t vfat /dev/mapper/store-media /sdcard' manually, it works fine and I can see the files in there, so the file system apparently is intact, but Android doesn't seem to recognize it as usable SDcard storage (i.e. no "move to SD" option in the app manager etc). The mount doesn't persist across reboots either, and adding an entry to /fstab.tenderloin is equally pointless.
Any hints on what could it be that prevents my device from automounting this partition?
Click to expand...
Click to collapse
It's not simply a matter of flashing the newer datamedia builds over an older, probably non-DM build. It requires restructuring the internal storage of the TP. Explicit directions are here. Use the newer version of the tool.

shumash said:
It's not simply a matter of flashing the newer datamedia builds over an older, probably non-DM build. It requires restructuring the internal storage of the TP. Explicit directions are here. Use the newer version of the tool.
Click to expand...
Click to collapse
The Evervolv before already was a datamedia build, and I have adjusted the partition sizes accordingly.
It worked correctly after the EW->Milaq migration about two weeks ago, and broke when I flashed a new Nightly over it last weekend.
(I did the whole cleanup via CWM before flashing the new nightly, just to avoid that question.)

NookHD+ can't mount emmc; can't fully boot from SD recovery

Perhaps someone can help. I've read a lot of the great content here but I've hit a wall.
A few weeks ago my ovation device was running cm11+cwm but began random rebooting. Clearing the cache+dalvik only helped briefly.
I tried an upgrade with a twrp 3.0.0.0 (using the amazing multiboot recovery SD), but it hung formatting the cache partition (I waited about an hour). Tried again, same thing.
I used adb shell to fix a blank file system type on the cache partition but was only successful in creating an ext2 partition there. I got cm13 booting but it trebuchet kept crashing. I tried twrp again and flashing a different image and tried a factory reset. Big mistake.
Now when I try to boot any recovery SD it doesn't boot all the way. Using adb shell, my dmesg shows that umount is hanging. No emmc partitions seem to be mounted. The partition data exists in dmesg but calls to parted hang. Mkfs.ext4 also hangs (naturally).
So I've lost the ability to fully boot recovery SDs (they are probably hanging when they try to mount the emmc partitions). As such I can't flash a recovery. I have a clockwork backup that has a system.ext.tar file in it, but I don't know how to use it at this point.
I can't mount /rom so I'm worried.
Is my emmc shot? Is there any way to tell?
Thanks!

Would a noEMMC SD be safe?
I guess what I was hoping to do was use adb to completely wipe and restore the device to a sane state, which would include repartitioning and formatting the emmc partitions. Is that possible? Maybe not at this point.
I guess another question would be: if my NookHd+ emmc is technically working but currently unrecoverable, is it possible for me to safely use a NOemmc SD card? There seem to be some warnings about those wrecking emmc but I can't find any technical explanation as to why.

Based on further diagnostics, my emmc is one of the faulty Samsung models and so I think the crashes and ultimate recovery failures were the failure of the emmc.
I've successfully installed 10.1 noEMMC on one microsd. Runs Okay but a lot of apps I am interested in don't work on android from this vintage.
I tried to install 4.4.4/CM11 noEMMC but it can't mount the necessary partitions as per the install process on the iamafanof Wordpress page. I also see SELinux errors in the twrp recovery log. Does anyone know how to overcome this mount issue that apparently impacts some people.

Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks

Sorry to resurrect this thread, But it exactly speaks to my issue. You mention that the blk0 and blk1 devices need to be switched for cm11 image to mount partitions properly. Does anyone know specifically where this might be done. Can files of the existing nov4 cm11 image be altered to reverse these two devices?

CalculonsTalent said:
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Click to expand...
Click to collapse
Could you please teach me how to mount EMMC partitions and retrieve data specially /factory partition with ADB?
I can only boot my Nook HD+ with with bootable SD card with TWRP or CWM.
Thanks.

Newly Installed LineageOS 17.1 -- Storage already full??

Okay I'm new at this. Did the temp root instructions and the flashed LineageOS 17.1 along with Gaaps mini. Everything was going fine with setting up the phone, and now all of a sudden Play store is saying "App requires external storage" if I tried to install anything new. Also got an error when taking a screenshot to show you guys here saying "Can't save screenshot due to limited storage space."
However when I go to settings, it says I've only used 11.28gb of 32gb free. Did I do something wrong? Parts are corrupted? Encrypted? Partitioned?? I appreciate any help in advance.
Edit: I'm thinking this has something to do w/ partitions. In TWRP it says my internal storage is (21.64gb).. when you add that and the 11.28 lineage says I used, that adds up to the full 32gb internal memory. I just did a full format + a full wipe selecting all options in twrp, and still I was able to boot into the same Lineage install (only it was reset and I had to start configuring from scratch again).
Any ideas where I went wrong in this process and how I can start over or merge the partitions??

RESOLVED: Not sure exactly what did it, but in TWRP: did another full wipe on all partitions, did a format, did a repair on system and data, changed file system back and forth to EXT4. Now it's all working.