Related
Due to popular demand I have created a size-agnostic SDCard CM7 installer.
Also allows to install unmodified CM7 builds on SD card.
Current version: 1.3
Grab the installer image here:
http://crimea.edu/~green/nook/generic-sdcard-v1.3.img.gz
it's a ~9M image that would unpack into ~130M disk image.
Also note - not all SD cards are created equal. Here is a thread of interest is you have not bought one yet: http://forum.xda-developers.com/showthread.php?p=12964262
Short version: buy Sandisk-branded class 4 microSD cards.
Write the image on your SD card. I tested with 2G, 4G and 8G cards and all worked.
Any uSD card of 1G or bigger in size should work if it is recognized by your nook.
Write on Windows by using WinImage and on Linux/MacOS X by using dd (to the entire device, not one of the partitions. The device name should not have any numbers at the end. The command is something like dd if=/somewhere/generic-sdcard.img of=/dev/sdX bs=1024k)
After done with writing, eject and then re-insert the uSD card into your computer.
Download a CM nightly build from here http://download.cyanogenmod.com/?device=encore (It is recommended to choose -87 nightly or later. If you plan to use prior version for initial install, stick with installer 1.2.1 for a different u-boot version)
Or just use your own update-cm-*-KANG-signed.zip file that is produced if you do your own builds.
The image would correctly detect unmodified CM7 builds and would make necessary adjustments to make them work on SD card.
Put the file to the SD card (there is only one partition). Don't change the name of the file.
unmount the uSD card and insert it into the nook.
Boot from this SD card. It'll boot and will update you on progress.
When it's done, it'll power off.
That's it, you now have CM7 on your SD card.
How to install market and gapps:
After you have booted into the CM7 on SD card for the first time and set up wifi access (important!)
Go to http://wiki.cyanogenmod.com/index.php?title=Latest_Version and at the end there is a table with various google apps versions. Get the one suitable for your cyanogen version (CM7 is the latest for now). The file is named gapps-....zip
shutdown your nook and take the SD card out, insert it into your computer.
Copy the gapps-... file to the SD card on the first partition (titled boot) without changing the file name.
Insert the uSD card back into the NOOK and boot into "Recovery mode" (hold nook N key and then press and hold power until the "Loading..." message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the bootloader "Loading..." message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long).
Alternatively if you do not want to fight the timing, boot normally into Android, then from desktop hold power key until a poweroff menu appears, In the poweroff menu choose "reboot", in the next menu choose "recovery" and press "OK". The nook would reboot straight into recovery.
How to update to a new build:
put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)
Boot from the SDcard in the recovery mode (see above) and the new snapshot would be installed.
The partition layout would be preserved, filesystems are NOT reformatted, so your data should be safe.
Installing other stuff:
Booting in recovery mode would install all files that are named "update-..." and end with .zip The files would then be deleted! Most of the packages should work, but I only tested a subset and not entire syntax of updater script is implemented. Certainly format and delete are not implemented.
OC Kernel installation instructions:
Starting with v1.2.1 there are no special instructions, install normally as described above.
Partition layout for the SD cards depends on size:
Less than 600M - unsupported.
up to 1G cards gets: system of ~300M and data of the rest of space. No FAT partition
2G cards (more than 1G up to 1800M) gets: 300M system, 612M data, rest is FAT sdcard
more than 2G cards gets: 460M system, 975M data, rest is FAT for sdcard.
How to update if you already installed using older version of the installer and don't want to reinstall (understandably):
Get update zip from http://crimea.edu/~green/nook/update-genimage-1.3.zip
Put the zip file as is onto the first partition of your sdcard..
reboot into recovery (triggered by the keys, the reboot into recovery does not work yet).
The new version would be installed and you are done.
You can combine this installation together with updating to .32 kernel in one step. Just put the update-cm file and the update-genimage-1.3.zip to the first partition. Make sure there is still at least 1M of space left!
Changes in 1.3
Install u-boot.bin and MLO loaders if provided.
Fixed a problem that led to overwrite of recovery kernel if a nightly was installed more than once)
(only in full image) updated u-boot to ignore BCB as that was a common source of problems. (that's why this version is not recommended for initial install with older nightlies, those don't provide a more correct u-boot for later operations. It's fine to do the update from older installer release, though)
Changes in 1.2.1
Really fixed dalingrin kernel packages installation
A bit more robust handling of install scripts
Changes in 1.2
Updated to new u-boot from B&N 1.2 update
Ability to obey BCB in eMMC (allows reboot into recovery from CM7)
Hopefully simplified the timing to trigger recovery boots from keyboard
Added support for Dalingrin's kernel update packages
The v1.1 version that is known good to work with 2.6.29 kernel releases is located at http://crimea.edu/~green/nook/generic-sdcard-v1.1.img.gz
This is very cool, thanks! My father bought a nook color after seeing mine, and after hearing what I have been able to get mine to do (thanks to the efforts of all the devs here) he has wanted to play a little more with his. Thanks to you, I have an easy way to set up the SD card and then ship it up to him. I can give him a taste without having to force him to even root his yet. Thanks again!
Very nice! Thanks.
Care to share the dates and differences between your build and say CM's? or perhaps a link to your builds progress?
I know you have done great work with BT, didn't want to get off topic, but I'm curious.
Thanks again.
12paq said:
Very nice! Thanks.
Care to share the dates and differences between your build and say CM's? or perhaps a link to your builds progress?
I know you have done great work with BT, didn't want to get off topic, but I'm curious.
Thanks again.
Click to expand...
Click to collapse
I did not work on BT (other than helping with testing), so I don't claim any credits there.
The difference between standard build and my build so far is only that my build has patched init files to boot from SD right in the zip file. (CM7 checkout as of today ~12pm), it was only created for testing, before I rolled the code that could update vanilla builds to work on SD cards.
You can use unmodified CM7 nightlies with this sdcard image now. The image itself does not contain any CM7 code, you need to copy zip file with it after writing the image to the SD card, but before attempting to boot.
Verygreen, I believe you have won the game. Congratulations!
Ah yes, I stand corrected, you created the first CM7 sd bootable for testing of BT.
Thanks again for your time on this latest project!
First off, this works very well! Thanks!
Now, after getting CM7 running on the sdcard, I plug the device into the usb port on my computer and instruct it to mount the sdcard. But, instead of the sdcard partition being mounted, the emmc partition is mounted.
Was that intentional or is it a bug?
Thanks
Thanks very easy to setup!
atomclock said:
First off, this works very well! Thanks!
Now, after getting CM7 running on the sdcard, I plug the device into the usb port on my computer and instruct it to mount the sdcard. But, instead of the sdcard partition being mounted, the emmc partition is mounted.
Was that intentional or is it a bug?
Thanks
Click to expand...
Click to collapse
New code in CM7 actually should cause both internal MMC AND sdcard to be mounted.
That is unless you used 1G sdcard, 1G sdcard does not have any mountable free space and then you'd only see emmc content as mountable.
verygreen said:
New code in CM7 actually should cause both internal MMC AND sdcard to be mounted.
That is unless you used 1G sdcard, 1G sdcard does not have any mountable free space and then you'd only see emmc content as mountable.
Click to expand...
Click to collapse
I'm using an 8Gb sdcard and I can access both the emmc and sdcard partitions through ADB but only the emmc partition is mounted.
So, I just need to try this with a different nightly build until I find one where the issue is corrected?
Well, I tried it with both cm_encore_full-25 and cm_encore_full-26 and still only the emmc partition is mounted.
atomclock said:
I'm using an 8Gb sdcard and I can access both the emmc and sdcard partitions through ADB but only the emmc partition is mounted.
So, I just need to try this with a different nightly build until I find one where the issue is corrected?
Well, I tried it with both cm_encore_full-25 and cm_encore_full-26 and still only the emmc partition is mounted.
Click to expand...
Click to collapse
As long as everything is mounted internally I don't think my changes broke anything else, so if there is a bug it's in the CM7 build itself.
I don't actually mount my nook on the computer, so I don't even know how to enable it by default come think of it.
I just know there was an ongoing work in this area to allow simultaneous mounting of multiple volumes and I heard it was already included, though I am not 100% sure about that.
To verygreen:
Well, I'm certainly doing something wrong here:
1. Using Win32DiskImager release 0.2 r23, i burnt my 2 GB with your generic.... .img image.
2. Copied your update.... .zip (on a second attempt an original cm_encore... .zip, plus gapps-GB-20110307-...zip, as installer was asking for it, at least to inflate), now I suspect your "put" is not equal to my "copy".
3. Tried to boot, enjoyed the penguin and boot scroll, but after everything was finished and prepared to "really" boot the boot was executed from my eMMC instead.
aludal said:
To verygreen:
Well, I'm certainly doing something wrong here:
1. Using Win32DiskImager release 0.2 r23, i burnt my 2 GB with your generic.... .img image.
2. Copied your update.... .zip (on a second attempt an original cm_encore... .zip, plus gapps-GB-20110307-...zip, as installer was asking for it, at least to inflate), now I suspect your "put" is not equal to my "copy".
3. Tried to boot, enjoyed the penguin and boot scroll, but after everything was finished and prepared to "really" boot the boot was executed from my eMMC instead.
Click to expand...
Click to collapse
Yes, the automatic reboot boots into eMMC for now, I am looking into it.
So just reboot again with the card in.
also, don't put gapps on the card at the first try. This combination does not boot for me into the desktop for some reason that I did not get to the root of. Possibly because it want internet connection setup that still is not if you try it on your first boot.
Thanks verygreen! This is a fantastic build! I was able to quickly and easily install this on my sd card.
Thanks again!
verygreen said:
Yes, the automatic reboot boots into eMMC for now, I am looking into it.
So just reboot again with the card in.
also, don't put gapps on the card at the first try. This combination does not boot for me into the desktop for some reason that I did not get to the root of. Possibly because it want internet connection setup that still is not if you try it on your first boot.
Click to expand...
Click to collapse
Somehow I went into non-booting phase, lol. My guess is after booting into my rooted Eclair with bookmarks-and-other-stuff-to SD I've got me an SD card not really good for "second" boot. Just have no idea what Eclair might do to that EXT4.
Anyways, repeated the experiment, now with pressing Power for >5 sec. Has booted into CyanogenMod 7 without a problem.
Can't do whatever testing: missing GAPPS very mucho! Please, Mr. verygreen, compile it into your image. In any case, I'm not really interested in swapping nightlies on this card -- by the last commits they didn't change much/significantly since n18. Just a static SD image of CM7 n26 + latest (03072011) Gapps will be a very desirable "mod" of yours. In any case you did exactly that (minus Gapps) for n17. Sure, there's a complete procedure of building SD image, but it's obviously much better followed when with a Linux box, and I don't have it.
aludal said:
Somehow I went into non-booting phase, lol. My guess is after booting into my rooted Eclair with bookmarks-and-other-stuff-to SD I've got me an SD card not really good for "second" boot. Just have no idea what Eclair might do to that EXT4.
Click to expand...
Click to collapse
Supposedly nothing. I routinely boot into eclair and then insert CM7 sdcard and it's fine.
aludal said:
Can't do whatever testing: missing GAPPS very mucho! Please, Mr. verygreen, compile it into your image. In any case, I'm not really interested in swapping nightlies on this card -- by the last commits they didn't change much/significantly since n18. Just a static SD image of CM7 n26 + latest (03072011) Gapps will be a very desirable "mod" of yours. In any case you did exactly that (minus Gapps) for n17. Sure, there's a complete procedure of building SD image, but it's obviously much better followed when with a Linux box, and I don't have it.
Click to expand...
Click to collapse
I can't distribute gapps, like I said
Well, until I figure out why recovery boot does not work what you can try to do is this:
after initial install was successful (and you setup your wireless), power off the nook, get the sd card.
Download gapps-gb-...zip and put it on the first partition.
move the uImage file to uImage.bak and uRamdisk to uRamdisk.bak.
Copy uRecImage to uImage and uRecRam to uRamdisk.
boot with the resulting image. It should say that it found the gapps archive and unpack it.
After it flushes caches and reboots, power off, put the sd card back into the computer
move uImage.bak to uImage and uRamdisk.bak to uRamdisk
boot off the card again, hopefully the gapps are working after that.
Please let me know if any problems arise.
verygreen said:
Supposedly nothing. I routinely boot into eclair and then insert CM7 sdcard and it's fine.
I can't distribute gapps, like I said
Well, until I figure out why recovery boot does not work what you can try to do is this:
after initial install was successful (and you setup your wireless), power off the nook, get the sd card.
Download gapps-gb-...zip and put it on the first partition.
move the uImage file to uImage.bak and uRamdisk to uRamdisk.bak.
Copy uRecImage to uImage and uRecRam to uRamdisk.
boot with the resulting image. It should say that it found the gapps archive and unpack it.
After it flushes caches and reboots, power off, put the sd card back into the computer
move uImage.bak to uImage and uRamdisk.bak to uRamdisk
boot off the card again, hopefully the gapps are working after that.
Please let me know if any problems arise.
Click to expand...
Click to collapse
I just tried following your directions for installing the gapps zip file. After renaming the uImage and the uRamdisk files the nook boots to your recovery with the penguin shows up with the follow:
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir (2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skipping format
Mounting /dev/mmcblk1p1 as /boot
Looking for the install images....
Initial Install files not found
Please download it from nook.linuxhacker.ru
and put on first partition of this SD card
the name should start with updatei-cm and end with .zip
Then the cursor just sits. No installation of the .zip file. Do I have to have the original cm zip file on the sd card with the gapp zip file? I thought it was posted that doesn't work.
Also thanks for the great work on this so far.
Absolutely Fantastic and pain free. You have done a great service.
Thanks
verygreen -
Would this work with an Android 3.0 Honeycomb Preview build, instead of a CM7 build ?
Modra76 said:
I just tried following your directions for installing the gapps zip file. After renaming the uImage and the uRamdisk files the nook boots to your recovery with the penguin shows up with the follow:
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir (2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skipping format
Mounting /dev/mmcblk1p1 as /boot
Looking for the install images....
Initial Install files not found
Please download it from nook.linuxhacker.ru
and put on first partition of this SD card
the name should start with updatei-cm and end with .zip
Then the cursor just sits. No installation of the .zip file. Do I have to have the original cm zip file on the sd card with the gapp zip file? I thought it was posted that doesn't work.
Also thanks for the great work on this so far.
Click to expand...
Click to collapse
Seeing the same. Also tried naming the gapps file "update.zip", to no avail.
Ok after many hours tonight I have managed to put together a couple .zip files that will install a modified vold.fstab on your Nook Color. (I am a total n00b at this)
The EMMC of the Nook Color has a partition for the ROM and a 5 GB partition that's mostly if not completely unused. Presently, there aren't any 3rd-party managers to move apps to that unused partition, so I modified the vold.fstab and am now able to use that partition for apps, files, etc.
NC.SWAP.VOLD.ZIP swaps the way the SD and EMMC directories are mounted. By swapping the mount points, and renaming EMMC to SDCARD, your apps, etc., will install to the internal storage, vs. installing to your SDCARD. Your physical SDcard is automatically mounted as "EMMC."
This also means that the music player still finds files, you can move files to "EMMC," and you can still eject the SDcard ("EMMC"), put it back in and it still shows up automatically. Now your NC won't freak out if you pull the card out without unmounting it - all of the apps are on the actual EMMC. You'd just find the SDcard under /mnt/emmc instead of /mnt/sdcard.
Because this ZIP file maps the change at an OS level, when you boot to recovery, your NC sees SD as the SDcard, so no issues occur. When you boot into your ROM, the mount points are swapped and you'll have access to the renamed "SDCARD" (5 GB) on your NC.
Use CWR 3.0.1.0 to install the .zip and check out the results with File Manager.
Thanks go out to Clark008, luciferii and Cali^Gal from #nookcolor, Loonacy and Raymondull from #Cyanogenmod, and EpicFail1236 from XDA.
Sorry if this is a bit crude, it's my first script ever. I would be happy to get any advice on how to make this better!
EDIT: I have been looking into renaming the emmc mount to say SD-External or better yet making it mount as /mnt/sdcard/sd-ext. it might be possible, ill be looking into it as soon as I can got laid up for a bit.
"Because this ZIP file maps the change at an OS level, when you boot to recovery, your NC sees SD as the SDcard, so no issues occur. When you boot into your ROM, the mount points are swapped and you'll have access to the renamed "SDCARD" (5 GB) on your NC."
/\/\ That clarifies a lot compared to the brief orig post. Will likely be flashing it this weekend.
BTW, if this expands and you need this 2nd post just have a mod give it to you. Thanks again!
BRILLIANT. Will be definitely testing this later today. Can't wait to run SD Tools on this
Sent from my NookColor using Tapatalk
it works! interesting how it'll work out as to unmounting, flashing roms. but with emmc being useless this is fantastic.
Thank you for the effort and time place in this mod
Yeah. The whole point of this was to utilize the 5GB internal emmc and not waste it. The next step is to mod the CWM to mount emmc as /sdcard so you can flash your zips from where you download them to (usually /mnt/sdcard/download), which in this case, goes to your emmc. But CWM will mount your external sdcard instead. For the time being, we can just put the zips we need to flash to the external sdcard, ie. /mnt/emmc.
I don't know if anyone noticed it yet, but if you usb mount after the swap, the transfer speed is kind of slow (~1.5mbps). I don't know if this is due to the emmc or that the read ahead cache needs to be tweaked.
We're open to make this even better. Feel free to comment and provide feedback.
This sounds like a step in the right direction, however, what I would like to see would be merging the emmc with the internal storage. What I mean is this; right now, when I go into "Storage", I see an "SD card" (8gb), "Internal Storage" (0.92gb), and "/mnt/emmc" (5gb). Why can't we combine the .93 Internal and the 5gb emmc together to make a 5.92gb Internal storage and eliminate the emmc from teh storage area? I'm sure there is a reason that I'm not aware of, but it seems that this would be the same as just about every other device. I am pretty sure the ROM is running from the emmc partition, so that has to have something to do with it, but I don't see a purpose for 3 storage places. I keep getting errors when I try to download apps and I don't even have very many installed. I have had to move most of them to the SD card to make room and some apps don't like to be installed on the SD card.
Another option would be to swap the emmc with the Internal storage. Then we'd be using the 5gb and the .92 gb would be sitting there doing nothing instead. Again, I'm sure there are reasons for this, I'm just asking to learn.
I agree.. ideally having the emmc mount be part of the system would be ideal.
Calla969 said:
This sounds like a step in the right direction, however, what I would like to see would be merging the emmc with the internal storage. What I mean is this; right now, when I go into "Storage", I see an "SD card" (8gb), "Internal Storage" (0.92gb), and "/mnt/emmc" (5gb). Why can't we combine the .93 Internal and the 5gb emmc together to make a 5.92gb Internal storage and eliminate the emmc from teh storage area? I'm sure there is a reason that I'm not aware of, but it seems that this would be the same as just about every other device. I am pretty sure the ROM is running from the emmc partition, so that has to have something to do with it, but I don't see a purpose for 3 storage places. I keep getting errors when I try to download apps and I don't even have very many installed. I have had to move most of them to the SD card to make room and some apps don't like to be installed on the SD card.
Another option would be to swap the emmc with the Internal storage. Then we'd be using the 5gb and the .92 gb would be sitting there doing nothing instead. Again, I'm sure there are reasons for this, I'm just asking to learn.
Click to expand...
Click to collapse
i have no idea TBH but thats far beyond my ability. really it would be nice to symlink emmc to the SD card or the other way around. the issue is that you cant symlink with fat partitions :-/
This is neet. I don't know enough to comment, but it looks valuble for some people.
I just use my stock emmc for music storage and let apps sit on SD w/ videos.
WobbleTheHutt said:
i have no idea TBH but thats far beyond my ability. really it would be nice to symlink emmc to the SD card or the other way around. the issue is that you cant symlink with fat partitions :-/
Click to expand...
Click to collapse
No, but you can symlink to them. Why not set vold.fstab to mount the partitions onto other names and make symlinks named /sdcard -> /othername? That way, the symlinks can do their jobs or rearranging the namespace to suit our needs.
The ramfs isn't FAT32, is it?
I'm an old cmdline type, tricks like this are used all the time to fool software with stubborn opinions about filenames.
Dennis
Jiggity Janx said:
If this works as effectively as it sounds like it will it's gonna rock! With the multiple wifi/bluetooth file transfer options I can say bye bye to the need for an sd card!
EDIT: I think this thread is eerily quiet because of the popular advice written up HERE. Specifically #5...
IMO, with a great write up on the best ways to work with this, all of the things it will affect (positive and negative), and the proper words of warning then the individuals that take it upon themselves to modify their devices are the only ones that can be held responsible if it doesn't work out as they had hoped. They also have to understand that when they work outside the boundaries of an accepted "standard" that they are somewhat desolate and will need to come back into the fold before they can/will be helped...
Just my .02...
Click to expand...
Click to collapse
This may be slightly off topic, but I cannot for the life of me figure out what that post is complaining/ talking about, I have had no trouble bouncing between HC, CM7 and stock.
All you have to do is flash to stock and then worst case you force the boot failure and the nook resets its self automatically
The last few posts on that message are myself and another person who have had not trouble with that now the OP hasn't responded so i'm not sure what to make up that post.
Is it real and an actual issue?
Or did the poster overreact to something?
Can some one please explain it to me if I am wrong about something in using a EMMC version of HC?
chisleu said:
This is neet. I don't know enough to comment, but it looks valuble for some people.
I just use my stock emmc for music storage and let apps sit on SD w/ videos.
Click to expand...
Click to collapse
Seems neet to me also. Always interested in using both emmc and sd space.
@ chisleau - I like the concept of putting all my music on emmc. Do you use an option in CM7 to install or move all your apps to your SD card?
thinking out loud (and not actually doing it) -- but we know that /data is /dev/block/mmcblk0p6 and and the "media" or "emmc" is located at /dev/block/mmcblk0p8 -- can't we just repartition and merge the two?
minotauri said:
thinking out loud (and not actually doing it) -- but we know that /data is /dev/block/mmcblk0p6 and and the "media" or "emmc" is located at /dev/block/mmcblk0p8 -- can't we just repartition and merge the two?
Click to expand...
Click to collapse
We can repartition but don't do it for this Reason -#5 http://forum.xda-developers.com/showpost.php?p=12494638&postcount=1
http://forum.xda-developers.com/showpost.php?p=12494666&postcount=2
ROMs that follow proper packaging - This emmc swap mod is one of them. So we're fine for those who are still hesitating.
Clark008 said:
ROMs that follow proper packaging - This emmc swap mod is one of them. So we're fine for those who are still hesitating.
Click to expand...
Click to collapse
Yep, I was hesitating, but between your post above and the "Thanks" from fattire to the OP, that is all the encouragement I need to take the plunge.
A few questions, tho, if someone can help me to understand this better....
I guess until I saw the OP, I did not realize that all apps in CM7 are installed to the SD card, as when I look at my installed apps in App Mgr, they don't show as being on the SD card. Is this some sort of CM7 voodoo or are my apps really on the internal memory?
Right now, with CM7, I am using the EMMC partition to store my music, under "My Files/Music". Power Amp can see this folder and it will play all my music just fine from within that directory on the internal partition, so if I install this update, what will that do to the 5Gb of internal storage I have now and the music on it?
Also, if I do install this update, what will happen to the apps and their associated data that I already have installed? Is this best done on a fresh build or will everything (apps/data and music) be A-OK after the Swap update is applied?
Just want to know what I am getting into by applying this update, as I have things pretty stable right now. If I could roll with apps on internal and music on SD, I would be more than fine with that, as long as I don't lose any of my apps/data/music in the process. If this is just mere partition re-naming/re-pointing, then I suspect my assets will remain intact?
Thanks to all who collaborated on this project!
why can't the entire internal partitions be imaged?
i use dd all the time to backup my sd card installs in case a test kernel or nightly goes poorly- or to burn a fresh install for multiple people. I just pop in the sd card into my laptop and burn the image back to the sd card.
if this was possible i'd have no issues with running off internal entirely if i could just burn the img. and get everything back as stock, including important device identifiers incase those were erased.
Need undo
This did what it's supposed to do but it seems to be causing a problem with the way I'm booting from sd. Is there a way to undo this?
Bump since I found this useful. +1 for CWM sdcard/emmc swap to enable SDcard-less flashing goodness from ROM Manager.
SOLVED - did a factory reset from inside CM9 and checked the box to format the sd card (god knows why this worked but the one in recovery didn't..also, why the hell didn't i think of this sooner? could have saved myself a week of searching)
while i was tinkering around trying to fix "mediaserver" (was killing my battery) i started to format my internal sd card memory (after backing it up)...for whatever reason i choose to do this via windows with the quick format off (wanted to scan for bad sectors and crap) then i forgot it was still running and unplugged my phone :facepalm:
novice mistake, i know.
anyhow, i've got adb up and running again, but i haven't been able to find a guide to fix it, or the info to bring up the partition tables, most sites give me specific commands to deal with the external card, but not ones to figure out how CM9\sgs2 is partitioned
ideally i'd like to just restore the partition, I do have backups if that's not possible though.
Phone is up and running fine minus that partition (which of course many apps rely on to store data, most don't have options to redirect it to my sd card.
any info on how CM9\sgs2 is partitioned or how to use ADB to find out would be greatly appreciated
Boot into your recovery and format your SD from within the recovery. That should fix it.
Lennyz1988 said:
Boot into your recovery and format your SD from within the recovery. That should fix it.
Click to expand...
Click to collapse
already tried that, the partition fails to mount, when i put my external sd card in the "sd card" partition mounts, but emmc doesn't (the sd card partition now being my external instead of my internal memory)
anyone even have a idea where i can find info on partitioning the internal memory? i've been searching as much as i can but i mostly only get link2sd pages, nothing on how to actually partition the internal memory
::edit:: i've made some progress, i've managed to install and operate parted via adb, but the version i have doesn't seem to support fat 32, i deleted then remade the partition but the phone still won't recognize it. cwm recovery is telling me "failed to mount /dev/block/mmcblk11 (invalid argument)" other pages seemed to imply that if i can get the partition to fat32 with a block size of 4096 it might work.
a factory reset from inside CM9 with the sd card format box checked did the trick, not sure why it took me a week of googling to figure that out :/ (wtb a facepalm emoticon)
"CM" you mean ?
CM = CyanogenMode?
CyanogenMod Kernel for Galaxy ?
"CyanogenMode" by installin from default ClockWorkMode? section of "Install ZIp from SD" ?
I need to re-partition Internal Memory too.
searched & found this your Topic.
would you please tell me what exactly has been done to fix re-partitioning internal memory?
maybe it can be so Important and Sticky.
Reza_Sadeghi said:
"CM" you mean ?
CM = CyanogenMode?
CyanogenMod Kernel for Galaxy ?
"CyanogenMode" by installin from default ClockWorkMode? section of "Install ZIp from SD" ?
I need to re-partition Internal Memory too.
searched & found this your Topic.
would you please tell me what exactly has been done to fix re-partitioning internal memory?
maybe it can be so Important and Sticky.
Click to expand...
Click to collapse
Actually, I have had the same problem, and if your device is not recognizing/mounting your internal SDcard, Bad news! You`ve lost it...
See this post for more details: http://forum.xda-developers.com/showthread.php?t=1665123
Next time think on a HTC or (even) Nokia, when you are about to purchase a new gadget (samsung, never ever more...:crying.
SociedadePsicopata said:
Actually, I have had the same problem, and if your device is not recognizing/mounting your internal SDcard, Bad news! You`ve lost it...
See this post for more details: http://forum.xda-developers.com/showthread.php?t=1665123
Next time think on a HTC or (even) Nokia, when you are about to purchase a new gadget (samsung, never ever more...:crying.
Click to expand...
Click to collapse
it's been a while, but it wasn't lost, i just had to repartition it, i described how i did this a few posts up.
i'm quite happy with my samsung sgsII, i'm not familiar with some of the other devices but i haven't run into any issues i can blame samsung for.
CM9 is exactly what i said it was, cyanogenmod 9. it's a whole rom package, not just a kernal
I am new at rooting, this is the first device I have tried to root. I followed the thread for a triple boot CM7 , CM9 and CM10 (also stock OS) from Malloneem. I decided to only flash CM7 and CM10 to NT 1.4.3. Everything worked great, except during the initial setup of both CM7 and CM10 it will not recognize my WiFi. I have tried twice, after first time I wiped NT and reformatted the sd card and started from scratch. same result both times.
I read through the replies and noticed that someone else had the same problem. the response said to wipe the cache and it should fix the dalvik. I wiped both the cache then tried and then wiped the dalvik and had the same results. With the CM10 it says "turning on wifi" and stays there.
I am a new member to xda so I cannot post a reply to the original thread.
Any help would be much appreciated.
If I cannot get this to work is there another method where you can use CM10 and stock OS? (something that is extreamly easy to follow)
Bears85 said:
I am new at rooting, this is the first device I have tried to root. I followed the thread for a triple boot CM7 , CM9 and CM10 (also stock OS) from Malloneem. I decided to only flash CM7 and CM10 to NT 1.4.3. Everything worked great, except during the initial setup of both CM7 and CM10 it will not recognize my WiFi. I have tried twice, after first time I wiped NT and reformatted the sd card and started from scratch. same result both times.
I read through the replies and noticed that someone else had the same problem. the response said to wipe the cache and it should fix the dalvik. I wiped both the cache then tried and then wiped the dalvik and had the same results. With the CM10 it says "turning on wifi" and stays there.
I am a new member to xda so I cannot post a reply to the original thread.
Any help would be much appreciated.
If I cannot get this to work is there another method where you can use CM10 and stock OS? (something that is extreamly easy to follow)
Click to expand...
Click to collapse
You can use this:
http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/
Write the image file to an SD card and you'll be good to go. You can use a repartitioning software to expand the partitions on your SD if you want. Use the instructions on the link I provided.
The SD card image will contain CM10.1 4.1.2. If you want to use a different ROM you can download the SDC version of any ROM ( has to be SDC!), place the zip on your SD card or internal storage. Boot into SDC recovery and installed the zip file. You'll need the GAPPS zip also (which has to be SDC also.)
Thank you for the help. My appologies for the redundant question but when I flash this ROM I will be able to bounce between CM10 and the stock B& N OS correct?
Bears85 said:
Thank you for the help. My appologies for the redundant question but when I flash this ROM I will be able to bounce between CM10 and the stock B& N OS correct?
Click to expand...
Click to collapse
Yes. Because CM 10 will be on your SD card. Stock will be on your internal. If your internal partitions or anything is messed up ( maybe the reason you can't boot stock) you can tell from CM.
datallboy said:
Yes. Because CM 10 will be on your SD card. Stock will be on your internal. If your internal partitions or anything is messed up ( maybe the reason you can't boot stock) you can tell from CM.
Click to expand...
Click to collapse
Thank you again. I have read throught the instructions on the link you provided and I am a little confused on the partitioning part. As I mentioned before this is my first time rooting anything. The instructions on the triple boot regarding the partitioning of the sdc were clear giving sizes for the newly created partitions etc., I didn't see that on this link (unless I missed it). Could you explain it so a newbie can understand it?
Thanks.
Bears85 said:
Thank you again. I have read throught the instructions on the link you provided and I am a little confused on the partitioning part. As I mentioned before this is my first time rooting anything. The instructions on the triple boot regarding the partitioning of the sdc were clear giving sizes for the newly created partitions etc., I didn't see that on this link (unless I missed it). Could you explain it so a newbie can understand it?
Thanks.
Click to expand...
Click to collapse
Well is there any reason why you would like triple boot? You need a fairly good size SD card if you want three systems. I just provided the simplest way to run cm on the nook. Write the image to your SD card and it will make it boot able. If you want to triple boot then setup your SD card partitions like you had before, but you only need to install the zips as alt boots.
Again, you probably don't need triple boot. Cm10+ has everything you'll need.
datallboy said:
Well is there any reason why you would like triple boot? You need a fairly good size SD card if you want three systems. I just provided the simplest way to run cm on the nook. Write the image to your SD card and it will make it boot able. If you want to triple boot then setup your SD card partitions like you had before, but you only need to install the zips as alt boots.
Again, you probably don't need triple boot. Cm10+ has everything you'll need.
Click to expand...
Click to collapse
No, I dont need the triple boot. Being a newbie I may have misread something (probably the case) but the link you gave me directed me to partition the sd card. it was this portion that was not clear to me. I was referencing the directions for partitioning on the triple boot thread as a comparison. The site you gave me said to partition the card but gave reference as to how big to make each partition. I don't need the triple boot.
My kid uses the NT to help read (read to me, etc...) I wanted something to get more of a tablet feel while keeping the stock system as well.
Thank you again. I appreciate the help. I will look at it again.
Bears85 said:
No, I dont need the triple boot. Being a newbie I may have misread something (probably the case) but the link you gave me directed me to partition the sd card. it was this portion that was not clear to me. I was referencing the directions for partitioning on the triple boot thread as a comparison. The site you gave me said to partition the card but gave reference as to how big to make each partition. I don't need the triple boot.
My kid uses the NT to help read (read to me, etc...) I wanted something to get more of a tablet feel while keeping the stock system as well.
Thank you again. I appreciate the help. I will look at it again.
Click to expand...
Click to collapse
On the iamafanof site you can scroll down there will be an SDC image. There is a difference between the image and the zips. All you need to do is download the SDC image, write it go your SD card using an file writer ( win32 disk writer will do) and your SD card will be ready to boot. Put it in your nook and and it will boot cyanoboot and should automatically do a SDC boot. It takes a little bit for the first boot to start ( usually 2 or 3 minutes)
Once you get your nook to boot cm I can tell you how to expand your SD partitions to hold more apps.
If you still have problems with WiFi it may be a different problem ( shouldn't happen).
If you need help or need a step by step guide I can find one or make one for you.
datallboy said:
...
If you need help or need a step by step guide I can find one or make one for you.
Click to expand...
Click to collapse
Just in time, "hot off the press" (almost) step-by-step guide: http://iamafanof.wordpress.com/2013...-2-jellybean-sdcard-img-for-nook-tablet-0416/.
For a more stable ROM build, use the CM10.0 image dated 12/31 in cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img.rar posted at http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/.
datallboy said:
On the iamafanof site you can scroll down there will be an SDC image. There is a difference between the image and the zips. All you need to do is download the SDC image, write it go your SD card using an file writer ( win32 disk writer will do) and your SD card will be ready to boot. Put it in your nook and and it will boot cyanoboot and should automatically do a SDC boot. It takes a little bit for the first boot to start ( usually 2 or 3 minutes)
Once you get your nook to boot cm I can tell you how to expand your SD partitions to hold more apps.
If you still have problems with WiFi it may be a different problem ( shouldn't happen).
If you need help or need a step by step guide I can find one or make one for you.
Click to expand...
Click to collapse
Thank you for your help. I worked and was simple. If you could explain the partitioning that would be great. If not, its working just the way I want it.
Thank you again!!
Bears85 said:
Thank you for your help. I worked and was simple. If you could explain the partitioning that would be great. If not, its working just the way I want it.
Thank you again!!
Click to expand...
Click to collapse
You have 4 partitions on your SD card: boot, system, data, sdcard. Your boot partition holds the files the boot CM. This is where recovery, mlo, uboot, etc is. System holds files essential for the ROM to work.
The only two you need to worry about are data and SD. Your data partitions holds apps. That is when you download an app the files in the apk file are put there. This would be like your internal storage for any phone or tablet. SD card is like an external SD card for your phone or tablet. Its where extra data files, photos, music etc go.
Depending on what size of SD card you have determines how big you can expand your data or SD partition.
Using a partitioning software ( like GParted) you can change the partitions and expand them to the side you want. I have a 16 GB SD card. So I expanded my data partition to 4 GB, and the rest went to SD card. Its okay to delete data or SD partition to expand it, but don't delete boot or system because you'll have to reformat the card and write the image file to the card again ( and ain't nobody got time for that.)
datallboy said:
You have 4 partitions on your SD card: boot, system, data, sdcard. Your boot partition holds the files the boot CM. This is where recovery, mlo, uboot, etc is. System holds files essential for the ROM to work.
The only two you need to worry about are data and SD. Your data partitions holds apps. That is when you download an app the files in the apk file are put there. This would be like your internal storage for any phone or tablet. SD card is like an external SD card for your phone or tablet. Its where extra data files, photos, music etc go.
Depending on what size of SD card you have determines how big you can expand your data or SD partition.
Using a partitioning software ( like GParted) you can change the partitions and expand them to the side you want. I have a 16 GB SD card. So I expanded my data partition to 4 GB, and the rest went to SD card. Its okay to delete data or SD partition to expand it, but don't delete boot or system because you'll have to reformat the card and write the image file to the card again ( and ain't nobody got time for that.)
Click to expand...
Click to collapse
This worked great!! thanks for all your help!!
That. I'm rooted with TWRP recovery, using the AOSP Extended ROM v3.2 (7.1.1 nougat).
I dont want to format my sdcard to internal, because I use it to save files and backups, and zip files to flash on an emergency.
Is there an alternative? I can't seem to find one.
It would be cool to make it think it has 2 sd cards, 1 internal and 1 external, while in real it's just one that is formatted in 2 partitions, but I don't think thats possible.
Thanks.
makmm said:
That. I'm rooted with TWRP recovery, using the AOSP Extended ROM v3.2 (7.1.1 nougat).
I dont want to format my sdcard to internal, because I use it to save files and backups, and zip files to flash on an emergency.
Is there an alternative? I can't seem to find one.
It would be cool to make it think it has 2 sd cards, 1 internal and 1 external, while in real it's just one that is formatted in 2 partitions, but I don't think thats possible.
Thanks.
Click to expand...
Click to collapse
What you want is possible. I'm using it on my moto e and moto z play.
I'll try to dig up the link for the procedure. You need a PC, and a basic knowledge of adb.
Edit: here you go. http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html?m=1
Here's what it looks like on Z play.
dandrumheller said:
Here's what it looks like on Z play.
Click to expand...
Click to collapse
Is it safe to do? In worst case scenario, will it brick my phone?
soft brick or hard brick?
(yes, i'm obviusly going to backup the contents of my sd card.)
BTW, thanks! if this works, ily so much lol
makmm said:
Is it safe to do? In worst case scenario, will it brick my phone?
soft brick or hard brick?
(yes, i'm obviusly going to backup the contents of my sd card.)
BTW, thanks! if this works, ily so much lol
Click to expand...
Click to collapse
It will nuke whatever is on your SD card. Won't touch a thing on your phone. Just follow the directions, he tells you how to confirm you're looking at the proper storage device.
AFAIK there are no negative effects beyond the normal additional read write cycles due to adoptable storage. Been using one card like this on the e (backup device, low use) for six months, and the other one for about a month now on the Z (high use daily driver). Working fine for me.
dandrumheller said:
It will nuke whatever is on your SD card. Won't touch a thing on your phone. Just follow the directions, he tells you how to confirm you're looking at the proper storage device.
AFAIK there are no negative effects beyond the normal additional read write cycles due to adoptable storage. Been using one card like this on the e (backup device, low use) for six months, and the other one for about a month now on the Z (high use daily driver). Working fine for me.
Click to expand...
Click to collapse
Seems legit. I have a 32gb sd (max for the Moto E surnia) and going for 25% internal (about 8gb) and 75% external (about 24gb.)
Thanks a lot!
EDIT: OK. I did it, but i forgotten to eject it, so now it's corrupted, and I can't seem to find a way to eject it to try to do it again, as when I press on the SD card, it tells me to format it. If I format it (temporarely, to then do it again) it will still say "Corrupted". EDIT2: I tried formatting it as portable and it worked, but then when I ejected with the icon next to the sd card, and then doing the commands gives the same result as before. "Portable Storage" is okay, named as "sdcard1 / vfat" but internal says "Corrupted". What do I try now?
makmm said:
Seems legit. I have a 32gb sd (max for the Moto E surnia) and going for 25% internal (about 8gb) and 75% external (about 24gb.)
Thanks a lot!
EDIT: OK. I did it, but i forgotten to eject it, so now it's corrupted, and I can't seem to find a way to eject it to try to do it again, as when I press on the SD card, it tells me to format it. If I format it (temporarely, to then do it again) it will still say "Corrupted". EDIT2: I tried formatting it as portable and it worked, but then when I ejected with the icon next to the sd card, and then doing the commands gives the same result as before. "Portable Storage" is okay, named as "sdcard1 / vfat" but internal says "Corrupted". What do I try now?
Click to expand...
Click to collapse
Hmmm. Probably better off to reformat the whole card to a single fat32 partition (use a card formating tool on the pc for this) and start over. Not sure if or how to do it via adb if it's seeing one partition as corrupt.
Fwiw, 32gb is the max " officially " supported SD card size on the surnia, but it works fine with bigger cards. I'm running 64gb.
I'm going to try a solution that is on the comments of the blog post. Thanks!
EDIT: tried the solution, heres the comment:
A Bored Boy 16 September 2016 at 19:54
For anyone that is getting the corrupted error on their SD card when creating a mixed partition. Here is the solution.
After you have partitioned the disk and while your SD card is corruped enter In the terminal the following:
$> adb shell sm list-volumes all
Which will list your volumes, for example:
private mounted null
public:179,1 mounted B5B1-140C
private:179,3 unmountable null
emulated mounted null
Then enter the following replacing 179,3 with whichever disk numbers you are given:
$> adb shell sm format private:179,3
$> adb shell sm mount private:179,3
Now your SD card in device storage should be properly mounted and your portable storage will still be there.
This worked on my LG G5 and should work on the S7.
On the 2nd and 3rd step I get the following error:
▶ adb shell sm mount private:179_67
Error: java.lang.IllegalStateException: command '55 volume mount private:179_67 0 -1' failed with '400 55 Command failed'
Help?
dandrumheller said:
Hmmm. Probably better off to reformat the whole card to a single fat32 partition (use a card formating tool on the pc for this) and start over. Not sure if or how to do it via adb if it's seeing one partition as corrupt.
Fwiw, 32gb is the max " officially " supported SD card size on the surnia, but it works fine with bigger cards. I'm running 64gb.
Click to expand...
Click to collapse
OK. Tried formatting into FAT32 with a chromebook (only computer I had access to atm, no usb adapter :/) and it formatted. Then putted the sd on my phone, selected as portable, EJECTED and did the proccess.. no luck.
Same result. The internal partition marks as "corrupted".
Anyone, help? I really need it, lol.
Thanks anyway,
dandrumheller? Someone? I really need it ?
I readed some more and see that link2sd is a better option? What's the difference?
makmm said:
dandrumheller? Someone? I really need it ?
Click to expand...
Click to collapse
Don't know what to tell you, I just followed the post and it worked. Do you have another card you can try with?
Does the original card work normally again after going back to fat32?
dandrumheller said:
Don't know what to tell you, I just followed the post and it worked. Do you have another card you can try with?
Does the original card work normally again after going back to fat32?
Click to expand...
Click to collapse
I think yes. I have other card(s) but they are not mine.
But what's the difference from this method than link2sd?
makmm said:
I think yes. I have other card(s) but they are not mine.
But what's the difference from this method than link2sd?
Click to expand...
Click to collapse
Haven't used link2sd in many years. Used to require lots of manual management, but it's the same concept. 2 partitions on SD card, 2 different formats, apps on one, media etc on the other.
Give it a shot. Used to have to manually format SD card to ext2 (iirc) for the app partition.
dandrumheller said:
Haven't used link2sd in many years. Used to require lots of manual management, but it's the same concept. 2 partitions on SD card, 2 different formats, apps on one, media etc on the other.
Give it a shot. Used to have to manually format SD card to ext2 (iirc) for the app partition.
Click to expand...
Click to collapse
I tried a thousand times with ext4 (and fat32) and it didnt work....
BUT WAIT, theres more! i tried with ext2 as you said (fat32 + ext2) and Just Works(tm)
Thanks, i really appreciate your help, you were the only one to respond lol...
PS: using apps2sd instead of link2sd as apps2sd has part manager, that's how i partitioned it, yay!
PS2: should i just use link2sd as "linker" and apps2sd as alternative/part manager?
thanks again ;D
Edit: I needed to change some config in SuperSU and create in advanced mode the Mnt script, but it works like a charm! It lets me move any app! ;D
makmm said:
I tried a thousand times with ext4 (and fat32) and it didnt work....
BUT WAIT, theres more! i tried with ext2 as you said (fat32 + ext2) and Just Works(tm)
Thanks, i really appreciate your help, you were the only one to respond lol...
PS: using apps2sd instead of link2sd as apps2sd has part manager, that's how i partitioned it, yay!
PS2: should i just use link2sd as "linker" and apps2sd as alternative/part manager?
thanks again ;D
Edit: I needed to change some config in SuperSU and create in advanced mode the Mnt script, but it works like a charm! It lets me move any app! ;D
Click to expand...
Click to collapse
Glad you got it working!
andorid sucks those years too