Related
This is one of those things that I've always assumed would work, but I don't think I've seen anyone actually confirm it or talk about it yet. Before doing any of this I did a clean wipe of everything, just to avoid confusion on my part.
Step 1) I DD'ed the entire filesystem to an 8GB microSD that I have.
Step 2) Mounted p1 from SD (which is a copy of P1 from internal)
Step 3a) Pulled ramdisk
Step 3b) Extracted ramdisk
Step 3c) Changed all mmcblk0 refs to mmcblk1 in init.rc
Step 3d) Recompiled ramdisk
Step 3e) Pushed ramdisk back to p1 on SD
Step 4) Shut down Nook, reboot, confirm via mount command that all mounted volumes are mmcblk1
As I said, this is nothing revolutionary, but I figured it could be good for testing, especially if anyone wants to take a shot at a potentially dangerous mod like recovery or installing a fresh /system. Also, if I ever seriously messed up my internal memory, I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way.
Very interesting. Thanks for the effort. Might be worth saving the image in case someone actually DOES brick their nook.
I'm curious as to the specifics. Aren't there several filesystems on the device? What did you do to pull/extract/recompile the ramdisk?
APKs
Are you able to install apk files to the emulated rom/nand on SD card...
also are you able to mount an extra partion on the card....
Thanks
"I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way"
That will be great if we can push those files back to NAND
FYI, Holding just power + Nook buttons for about 15-20 sec will bring up the factury reset screen.
nook'r said:
Are you able to install apk files to the emulated rom/nand on SD card...
Click to expand...
Click to collapse
I haven't yet, but I don't see why not. Nothing especially different about it as opposed to the internal filesystem.
nook'r said:
also are you able to mount an extra partion on the card....
Click to expand...
Click to collapse
Right now I left vold alone, so it rather stupidly mounts p1, which contains all the critical stuff. I don't see any reason why vold couldn't be made to point to another seperate partition. (which is what I did with some other trials when using the internal ramdisk to boot to /system on the SD - left p1 as a "sdcard" partition)
nook'r said:
"I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way"
That will be great if we can push those files back to NAND
Click to expand...
Click to collapse
I've backed up my own partitions individually. I suppose if I zero'd empty space and gzipped I could probably find some way to write the entire partition table to somewhere.
Would this be useful to someone who would want to dual boot with Ubuntu or MeeGo?
Could this be used to "dual boot" the fully stock Nook in store and then from card when you want to be free?
Homer
Homer_S_xda said:
Could this be used to "dual boot" the fully stock Nook in store and then from card when you want to be free?
Homer
Click to expand...
Click to collapse
This can be used for whatever you want to use it for. I've been running this way for quite a while, and everything works just as it would if you're running from the internal. It's just like dual booting on your PC.
The first (that I saw) and best documentation for setting this up can be found at:
http://blog.fsck.com/
axe2 said:
This can be used for whatever you want to use it for. I've been running this way for quite a while, and everything works just as it would if you're running from the internal. It's just like dual booting on your PC.
The first (that I saw) and best documentation for setting this up can be found at:
http://blog.fsck.com/
Click to expand...
Click to collapse
This is intriguing.
I would love to run everything off a micro sd and then pop it out to put it back to stock.
Would a 1GB micro sd work ok for this?
Someone needs to come up with an automated way to do this. That would be awesome.
moovius said:
This is intriguing.
I would love to run everything off a micro sd and then pop it out to put it back to stock.
Would a 1GB micro sd work ok for this?
Someone needs to come up with an automated way to do this. That would be awesome.
Click to expand...
Click to collapse
1GB is going to be too small to hold the whole system, but 4GB should work.
It should be something that would be scriptable assuming that the required tools exist on the standard rom, but I don't know if the tools are on there.
You could probably get to 1 GB if you dumped all the recovery junk and made media and data tiny. I'm trying to think if there's anything earing up tons of space besides /system.
Of course, just because you can doesn't mean you should.
how about multiple partitions on a 16gb
clockworx said:
This is one of those things that I've always assumed would work, but I don't think I've seen anyone actually confirm it or talk about it yet. Before doing any of this I did a clean wipe of everything, just to avoid confusion on my part.
Step 1) I DD'ed the entire filesystem to an 8GB microSD that I have.
Step 2) Mounted p1 from SD (which is a copy of P1 from internal)
Step 3a) Pulled ramdisk
Step 3b) Extracted ramdisk
Step 3c) Changed all mmcblk0 refs to mmcblk1 in init.rc
Step 3d) Recompiled ramdisk
Step 3e) Pushed ramdisk back to p1 on SD
Step 4) Shut down Nook, reboot, confirm via mount command that all mounted volumes are mmcblk1
As I said, this is nothing revolutionary, but I figured it could be good for testing, especially if anyone wants to take a shot at a potentially dangerous mod like recovery or installing a fresh /system. Also, if I ever seriously messed up my internal memory, I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way.
Click to expand...
Click to collapse
Think someone could put together a noob guide for this? I'd like to try running a rooted version of Nook Color from SDCARD (partitioned?) on my stock Nook Color.
If possible? Please & Thanks...
I'm opening a new thread as this is really the work of verygreen, racks11479, j4mm3r, stilger, and rookie1.... and I've hijacked their threads enough as I only did minor repackaging to put this together as a hopefully generic template image...
This is but an attempt to create a mostly generic SDcard template for installing all versions, as base for Froyo, CM7, or Honeycomb as an SDcard install...... Most of the features best lend themselves to CM7 as verygreen's Alternate (uAltImg/Ram) allows installing and upgrading all current variants of CM7... but with Recovery as CWR 3.0.1.0/Ext3/4 with verygreen's installer/upgrader as uAltImg/Ram it can handle all your CM7 variant install and upgrade/migrate to SDcard needs...
The generic 2GB expandable image is available from;
http://dev-host.org/aewwoavj437z/Nook-2GB-SDCard-CW3010-VGCM7InstallerAsALTinMultiBoot-v6.zip
I suspect/hope that this thread will fade fast from the first page but just hope it will be useful for folks when modeling and building generic SDcard bootable versions...
EDIT: For folks who just want to update just their existing SDcard boot partition and get this boot functionality
I removed the files you shouldn't change from an existing /boot dir and zipped up the rest and posted this zip in my dropbox
http://dl.dropbox.com/u/6922721/jtbnet-modified-bootfiles.zip
Just have your SDcard mounted as /boot on your PC and extract this zip to it to get the same boot options as my card...
The layout of the current .v6 template SDcard to allow it to fit on a 2GB minimum size card is;
Part. # Name FStype Alloc. size Free Space
1 /boot FAT32 149MB 120MB
2 /system EXT3 462MB 455MB
3 /data EXT3 964MB 948MB
4 /sdcard FAT32 39MB 38MB
This is a Generic 2GB expandable template SDcard image to use to create pretty much whatever bootable SDcard you want...
How it differs with earlier Generic SDcards is I reorganized the default, Recovery, and Alternate boot choices using j3mm4r's multi-boot bootloader.
I updated Recovery to the newest version CWR 3.0.1.0 modified to write to SDcard instead of Internal/eMMC memory partitions with the help of user stilger. This can be used for Backup and Restore of full cards... as well as installing of CW packages like Google Apps, and Custom CW Rom Install packages you can find for Froyo, Honeycomb Preview and Gingerbread in this forum...
I moved verygreen's CM7 Installer/updater to the Alternate boot choice... In verygreen's thread he uses this as the default Kernal and Ramdisk which gets overwritten by the package you install... thus the need for 2 cards or copying files around to reuse the original... with this as Alternate it doesn't get overwritten and thus is available next time you want to use it... like Install CM7 for the first time... then upgrade to the new Nitely the next day without need for finding and copying files or using 2 cards...
How verygreen's Installer/updater differs from CWR... With vg's installer you place the installable files on the /boot partition... this installer will install SDcard ready or agnostic installables AND will install eMMC designed version CM7 builds and do on the fly conversion to SDcard version during the install seemlessly...
CWR 3.0.1.0 for SDcard will expect the install zip or backup file to be on the 4th/sdcard partition and expects these to be agnostic installs as it doesn't do anything on the fly to make these run on SDcard... It they are built or modifed to run on SDcard thats fine and installing from this Recovery works as would be expected...
I extended the size of the boot partition to have ~120MB free to allow for installing larger images as the prior ~100MB space was too close to currently typical installable Custom Rom packages.
The 4th /sdcard partiiton is created Very small to fit on a 2GB SDcard and really needs to be expanded using Easeus Partition Manager on Windows or an equivalent program on your OS of choice to fit your size choice of SDcard...
I will offer some experience with SDcard here... I bought 10 different manufacturers, and Class/speed cards... I ran disk benchmarks for all and then used the ones that performed best for daily use... Sandisk brand is the most generally faster than the Class it's stamped... A Class 4 beats most brand's Class-6... I wanted the fastest... and settled on buying 8 cards as KingMax Class-10 SDcards, 4 4GB and 4 8GB, from buy.com... these aren't the cheapest cards by far, BUT in this case you DO get what you pay for...
So for daily use I'd reccommend the KingMax 8GB Class-10 cards as I've gotten better than 2000 Quadrant scores running these cards for Froyo, Honeycomb, and CM7 Gingerbread installs... this is as good or better performance than most scores I've seen from folks running the same installs on Internal/eMMC...
CM7 Install Example by User stilger
with comments added by jtbnet and xdabr:
----------------------------------
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v6)
http://dl.dropbox.com/u/6922721/Nook-2GB-SDCard-CW3010-VGCM7InstallerAsALTinMultiBoot-v6.zip
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Use Easeus Partition Manager to extend the 30MB 4th FAT32 /sdcard partition to fit your current SDcard
4. Once the card is written, place the cm7 zip in the root of the boot filesystem.
(Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
http://mirror.teamdouche.net/?device=encore
5. Place the gapps zip of your choice in the same "boot" filesystem.
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110307-signed.zip
6. Place SDcard in your Nook.
7. Turn on Nook.
8. Hit N button when it says Press any key for menu.
9. Choose SD and Alternate as your boot option
10. Let it finish. It says it will reboot but usually hangs for me so I give it 10 seconds after the screen goes black and long press the power button until it starts up...
11. Boot into CM7
TIP: To have rooted stock eclair version nook use the same sdcard partition (#4) as you use when booting on an SDcard bootable you can make one simple edit to the stock eclair /system/etc/vold.conf...
There are 2 definition blocks in the file... the first is for mount of internal eMMC partition 8 as /media, while the second block is to mount the 1st sdcard partition as /sdcard... to change this so that the 4th partition on the SDcard gets mount to /sdcard just Add a line;
partition 4
in the second block with your favorite editor like Root Explorer, or via adb pull,edit,push of the vold.conf file... and reboot...
I.E.:
## vold configuration file for zoom2
# modified for encore
volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
partition 8
media_type mmc
##mount_point /sdcard
mount_point /media
ums_path /devices/platform/usb_mass_storage/lun0
}
volume_sdcard2 {
## Currently points to internal eMMC, assumes eMMC is formatted as FAT32
media_path /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
partition 4
media_type mmc
##mount_point /media
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun1
}
Just to verify, this image has?
J4mm3r's multi-boot
CWM 3.0.1.0 but with correct mounts like racks11479's CWM 3.0.0.6 as uRecImg/Ram
verygreens installer as uAltImg/Ram
I had already done the same with racks CWM, but that's ext4 only I believe.
This will be great with CWM 3.0.1.0.
Thanks for putting this together
P.S. What is the CM7 vesion as uImage/uRamdisk?
Tried to burn the image on a 2Gb SDcard to look inside.
It's a 4GB image not 2GB.
bobshute said:
Tried to burn the image on a 2Gb SDcard to look inside.
It's a 4GB image not 2GB.
Click to expand...
Click to collapse
Sorry Bob... I uploaded the wrong image... Had a long day at work today so just getting to uploading a fresh image... this one IS 2 GB with larger/150MB /boot but a very small 4th /sdcard partition, and has formated system and data so won't boot to CM7 anymore but it's much cleaner...
Only thing this 2GB image only zips down to 800MB... strange as the wrong card I uploaded last night was a 4GB card I was testing with and with lots of data on system and data and it zipped down to 300MB... but this one is cleaner and does boot to CWR 3.0.1.0 as recovery and verygreen's CM7 install/updater as Alternate boot...
It's taking forever to upload so I may not be able to update the link in the original post till the morning as already well after midnight now...
bobshute said:
Just to verify, this image has?
J4mm3r's multi-boot
CWM 3.0.1.0 but with correct mounts like racks11479's CWM 3.0.0.6 as uRecImg/Ram
verygreens installer as uAltImg/Ram
I had already done the same with racks CWM, but that's ext4 only I believe.
This will be great with CWM 3.0.1.0.
Thanks for putting this together
P.S. What is the CM7 vesion as uImage/uRamdisk?
Click to expand...
Click to collapse
You are correct on what it has for uRecImg/Ram and uAltImg/Ram and yes Racks' 3.0.0.6 is Ext4 Only.... thus why I wanted to update to 3.0.1.0/Ext3 and Ext4...
That wrong 4GB upload from yestrday was the test card I had expanded and tested installing CM7 RC4 with UI tweaks to test VG's installer and then restored system and data from my normal card's backup to test CWR 3.0.1.0... so I mixed up the cards when I made the image and uploaded the expanded test 4GB version instead of the original blank 2GB version I started with...
Updated OP with cleaned up file...
Thanx to Verygreen's suggestion to zerofill the system and data partitions to allow for better compression I uploaded v4 where the zipped filesize is down to 420MB from prior zip of 770MB. OP link is updated...
I'm going to continue to see if I can find a way to make this significantly smaller while still containg all 4 mountable partitions and will upload any success story if/when it might occur...
I actually used the 2GB image itself booted to CWR and ran 'adb shell' to allow me to use the 'dd' command to zero fill the system and data partitions... THANX again to verygreen for that idea...
jtbnet said:
Thanx to Verygreen's suggestion to zerofill the system and data partitions to allow for better compression I uploaded v4 where the zipped filesize is down to 420MB from prior zip of 770MB. OP link is updated...
I'm going to continue to see if I can find a way to make this significantly smaller while still containg all 4 mountable partitions and will upload any success story if/when it might occur...
I actually used the 2GB image itself booted to CWR and ran 'adb shell' to allow me to use the 'dd' command to zero fill the system and data partitions... THANX again to verygreen for that idea...
Click to expand...
Click to collapse
jtbnet - I think zeroing the /data and /system file systems causes your script to fail. I put this image on an 8gb sd card today. I copied the latest Tablet Tweaks and gapps zip files to the boot partition rebooted into altboot.. It failed not being able to create files. Took the nook into recovery logged in via ADB and /system where full:
Before:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 250080 32 250048 0% /dev
/dev/block/mmcblk0p7 350021 52983 278967 16% /cache
/dev/block/mmcblk1p2 458925 458925 0 100% /system
/dev/block/mmcblk1p3 972436 972436 0 100% /data
Click to expand...
Click to collapse
Used recovery to format /data and /system.
After:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 250080 32 250048 0% /dev
/dev/block/mmcblk0p7 350021 52983 278967 16% /cache
/dev/block/mmcblk1p2 458925 8238 426992 2% /system
/dev/block/mmcblk1p3 972436 16424 906616 2% /data
Click to expand...
Click to collapse
Booted into alt boot after copying zip files to /boot again and everything installed fine.
stilger said:
jtbnet - I think zeroing the /data and /system file systems causes your script to fail. I put this image on an 8gb sd card today. I copied the latest Tablet Tweaks and gapps zip files to the boot partition rebooted into altboot.. It failed not being able to create files. Took the nook into recovery logged in via ADB and /system where full:
...
Used recovery to format /data and /system.
.
Booted into alt boot after copying zip files to /boot again and everything installed fine.
Click to expand...
Click to collapse
THANX
I had been just deleting the filler files in CWR (/system/zerofile and /data/zerofile) instead of formatting... BUT I think I have found the answer... I need to zerofill to cause the 2 partitions to compress reasonably... BUT if I create the files then sync,umount,re-mount then delete the files, sync, umount this frees space by freeing the inode but shouldn't actually touch the zerofill'd now freed space... so compression should be the same without the files...
I'll give this a try and upload v5 later hopefully...
EDIT: finally found time to upload v5... well mirror is still in process... /data and /system now empty and result is even a few bytes smaller...
Thank you jtbnet, but I am so confused.
Personally I'm mostly interested in SD card booting because I'd still like to leave the internal eMMC memory stock or near-stock.
But I get confused as to how the "size agnostic" approach ultimately writes to the card, whether it uses the NC or a PC as an intermediary to get the card written, how Clockwork Recovery comes into play if at all (I thought it was only used when you ARE futzing with the eMMC instead of cleanly booting off SD card), and more.
I would prefer a list of disk images I can write to an SD card with standard tools (I used "dd" on a Mac for brian's Nookie Froyo SD image), but it seems your mod here and the main size-agnostic installer are more complicated than that.
Is there a simple explanation you can give me (and other similar newbies)?
xdabr said:
Thank you jtbnet, but I am so confused.
Personally I'm mostly interested in SD card booting because I'd still like to leave the internal eMMC memory stock or near-stock.
But I get confused as to how the "size agnostic" approach ultimately writes to the card, whether it uses the NC or a PC as an intermediary to get the card written, how Clockwork Recovery comes into play if at all (I thought it was only used when you ARE futzing with the eMMC instead of cleanly booting off SD card), and more.
I would prefer a list of disk images I can write to an SD card with standard tools (I used "dd" on a Mac for brian's Nookie Froyo SD image), but it seems your mod here and the main size-agnostic installer are more complicated than that.
Is there a simple explanation you can give me (and other similar newbies)?
Click to expand...
Click to collapse
Check racks11479's thread for a good number of SDcard installable versions...
http://forum.xda-developers.com/showthread.php?t=998861
I do hope to find time to update the second post in this thread with some much better explanantion... but in short...
This is a Generic 2GB expandable template SDcard image to use to create pretty much whatever bootable SDcard you want...
How it differs with earlier Generic SDcards is I reorganized the default, Recovery, and Alternate boot choices using j3mm4r's multi-boot bootloader.
I updated Recovery to the newest version CWR 3.0.1.0 modified to write to SDcard instead of Internal/eMMC memory partitions with the help of user stilger. This can be used for Backup and Restore of full cards... as well as installing of CW packages like Google Apps, and Custom CW Rom Install packages you can find for Froyo, Honeycomb Preview and Gingerbread in this forum...
I moved verygreen's CM7 Installer/updater to the Alternate boot choice... In verygreen's thread he uses this as the default Kernal and Ramdisk which gets overwritten by the package you install... thus the need for 2 cards or copying files around to reuse the original... with this as Alternate it doesn't get overwritten and thus is available next time you want to use it... like Install CM7 for the first time... then upgrade to the new Nitely the next day without need for finding and copying files or using 2 cards...
How verygreen's Installer/updater differs from CWR... With vg's installer you place the installable files on the /boot partition... this installer will install SDcard ready or agnostic installables AND will install eMMC designed version CM7 builds and do on the fly conversion to SDcard version during the install seemlessly...
CWR 3.0.1.0 for SDcard will expect the install zip or backup file to be on the 4th/sdcard partition and expects these to be agnostic installs as it doesn't do anything on the fly to make these run on SDcard... It they are built or modifed to run on SDcard thats fine and installing from this Recovery works as would be expected...
I extended the size of the boot partition to have ~120MB free to allow for installing larger images as the prior ~100MB space was too close to currently typical installable Custom Rom packages.
The 4th /sdcard partiiton is created Very small to fit on a 2GB SDcard and really needs to be expanded using Easeus Partition Manager on Windows or an equivalent program on your OS of choice to fit your size choice of SDcard...
I will offer some experience with SDcard here... I bought 10 different manufacturers, and Class/speed cards... I ran disk benchmarks for all and then used the ones that performed best for daily use... Sandisk brand is the most generally faster than the Class it's stamped... A Class 4 beats most brand's Class-6... I wanted the fastest... and settled on buying 8 cards as KingMax Class-10 SDcards, 4 4GB and 4 8GB, from buy.com... these aren't the cheapest cards by far, BUT in this case you DO get what you pay for...
So for daily use I'd reccommend the KingMax 8GB Class-10 cards as I've gotten better than 2000 Quadrant scores running these cards for Froyo, Honeycomb, and CM7 Gingerbread installs... this is as good or better performance than most scores I've seen from folks running the same installs on Internal/eMMC...
Even 400M seems excessive for mostly zero filled card.
Basically your target compressed size should be the size of all real files on the card + a little bit.
Make sure you zero the extra fat partition and boot partition free space too as plenty of random data might be there.
verygreen said:
Even 400M seems excessive for mostly zero filled card.
Basically your target compressed size should be the size of all real files on the card + a little bit.
Make sure you zero the extra fat partition and boot partition free space too as plenty of random data might be there.
Click to expand...
Click to collapse
THANX...
I did think of that... after the fact... but the free space on those 2 partitions is <150MB which at the expected 4 to 1 compression I'm seeing would only save another ~35MB... so I didn't bother try and re-upload.... as less than 10% expected improvement... IF I need to upload another version I will include this in that version though...
I'd tend to agree with you on "your target compressed size should be the size of all real files on the card + a little bit." but the actual Used space is ~100MB, Total Space = 2GB, Unused space is thus around 1.9GB... so compression (1/5-1/4) really STINKS on this... but I'm not sure why as I've tried winzip and gzip with multiple levels of compression...
Thank you so much for the explanation, jtbnet, but it's hurting my noob brain!
It seems that most people like CM7 with Tablet Tweaks by mad-murdock. Could someone detail for me (step by step) the simplest way to get that in a bootable 2 GB SD card, preferably without involving a second card, and without touching the eMMC at all? I can't tell whether this project does that or not (and if so, how) or whether I should stick with racks11479's approach, or what. My apologies; I'm not usually this far behind.
Edit: I forgot that mad-murdock's Tablet Tweaks were already merged. So I guess just make that "CM7".
xdabr said:
Thank you so much for the explanation, jtbnet, but it's hurting my noob brain!
It seems that most people like CM7 with Tablet Tweaks by mad-murdock. Could someone detail for me (step by step) the simplest way to get that in a bootable 2 GB SD card, preferably without involving a second card, and without touching the eMMC at all? I can't tell whether this project does that or not (and if so, how) or whether I should stick with racks11479's approach, or what. My apologies; I'm not usually this far behind.
Edit: I forgot that mad-murdock's Tablet Tweaks were already merged. So I guess just make that "CM7".
Click to expand...
Click to collapse
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v5)
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Once the card is written place the cm7 zip in the root of the boot filesystem. (Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
4. Place the gapps zip of your choice in the same "boot" filesystem.
5. Place sdcard in nook.
6. Turn on nook.
7. Hit N button when it says Press any key for menu.
8. Choose SD and Alternate as your boot option
9. Let it finish.
10. Boot into CM7
I did not provide you all the links but the CM7 nook image in mad murdocks Tablet Tweaks thread or the latest nightly for the nook (next nightly build should have Tablet Tweaks) should work. The gapps zip is also available at the CM site.
FYI - This image is based off the work of verygreen's thread: http://forum.xda-developers.com/showthread.php?t=1000957
Hopefully this will get you going.
Perfect recipe; thank you, stilger! Just what I (and likely lots of others) needed to know. I'll probably try this tonight.
I love this place.
stilger said:
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v5)
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Once the card is written place the cm7 zip in the root of the boot filesystem. (Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
4. Place the gapps zip of your choice in the same "boot" filesystem.
5. Place sdcard in nook.
6. Turn on nook.
7. Hit N button when it says Press any key for menu.
8. Choose SD and Alternate as your boot option
9. Let it finish.
10. Boot into CM7
I did not provide you all the links but the CM7 nook image in mad murdocks Tablet Tweaks thread or the latest nightly for the nook (next nightly build should have Tablet Tweaks) should work. The gapps zip is also available at the CM site.
FYI - This image is based off the work of verygreen's thread: http://forum.xda-developers.com/showthread.php?t=1000957
Hopefully this will get you going.
Click to expand...
Click to collapse
THANX...
I'd add one step which is to use something like Easeus Partition Manager to extend the /sdcard partition to fill your larger than 2GB card between #2 and #3... as if only using the 2GB card image /sdcard is Only ~30MB big ... mostly just a Fat32 FS placeholder to allow extending...
jtbnet said:
THANX...
I'd add one step which is to use something like Easeus Partition Manager to extend the /sdcard partition to fill your larger than 2GB card between #2 and #3... as if only using the 2GB card image /sdcard is Only ~30MB big ... mostly just a Fat32 FS placeholder to allow extending...
Click to expand...
Click to collapse
You should take and add this step by step process to the first or second post.
Maybe even add links etc... Dunno. Up to you.
stilger said:
You should take and add this step by step process to the first or second post.
Maybe even add links etc... Dunno. Up to you.
Click to expand...
Click to collapse
THANX... Added your steps as an example in the Second post...
Hello all,
Is it possible to create 2 partitions on your sd card? One for WinMo and one for Android. To keep it all separated.
It doesn´t have to be partition it may also be a trick or something. For the root in android begins in /sdcard and in winmo /sdcard/winmo. As long the 2 different systems are separated.
But a lot of searching, read something about linux swap and ext2 partitions(but i believe it's for real roms not ports). And that winmo won't see any multi partition sd cards.
Thx in advance
Answer in the 5th post
You can simply create a folder called andboot and put all the android stuff in that folder and keep "winmo-stuff" in the root of your sd
wavesshock said:
You can simply create a folder called andboot and put all the android stuff in that folder and keep "winmo-stuff" in the root of your sd
Click to expand...
Click to collapse
I know that, but a lot android apps are also creating folders in the root.
Christiaan91 said:
I know that, but a lot android apps are also creating folders in the root.
Click to expand...
Click to collapse
Yea they kinda need to.
You can try to do two FAT32 partitions, but I don't think Windows/WinMo will see/understand the second partition - even if it is FAT32.
So you'd be kinda SOL trying to boot Android if WinMo can't see the partition... It might work, if you kick haret off from one partition to boot on the other... but kinda odd.
The ext2 solution isn't really a complete solution as it also depends on a FAT32 partition - I assume Android would still create folders on it in other words.
Just use separate SD's, problem solved .
Got it
It worked.
I made 2 FAT32 partitions. Primary for Android and Logical for WinMo.
WinMo recognizes them both, in file explorer as Storage card(Android) and Storage Card2(WinMo).
When you install an app in WinMo you get 3 choices, internal, SDcard and SDcard2.
The only problem you got is that Windows(PC) don't recognize the WinMo partition(it will recognize in activesync mode). So you first have to put all you WinMo apps on the android partition. And copy them to the WinMo partition in WinMo.
AFAIK everything is working fine.
Android doesn't see the WinMo partition
You can also try it. (I'm not responsible if anything goes wrong)
- Did it with this tool.
- I put my sd card in my computer (don't know if it works when you do it through your phone).
- MAKE A BACK-UP CUZ EVERYTHING IS GONE AFTER THIS!
- Delete the whole partition.
- Make a new partition, first the Android one*. Adjust the settings what you like, but put the partition primary.
- Then the WinMo partition. Adjust the settings what you like, but put the partition Logical.
- Now you're done. Put all the files on the android partition.
- SD card back in your phone and reboot.
- Now you can move the WinMo files, on your android partition, to the WinMo partition.
*When you do the WinMo Partition first and the android second, android will not boot.
Cool, glad you got it working. I'm certainly not going to do it, but perhaps others might!
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.
Hey guys im a bit frustrated right now:
ive created the partitions just like in this guide:
http://forum.xda-developers.com/showpost.php?p=22201029&postcount=43
Ive got 2x Ext4 partitions and an active primary fat32 with about 100megs on it. You can find some screenshots in the attachments.
The Problem is if i restart my nook it doesnt pop up with cwm, it just normaly boots.
Did i forget something?
To make it boot you need to active the LBA flags, but i think 7. Right click on the new Primary partition and make sure "Set Active" is selected from the Modify submenu step is the equivalent of LBA flags in gparted ubuntu but i could be totally wrong. That is an important step. That is the hint
~ Veronica
yea i have done that, next to the "Primary" it says "active" so yeah..
Try rebooting the NT with the USB cable attached to the computer. This has worked for a few people.
yea tried that to but didnt change anything :/
That being the case, I'm sorry to say that you probably have a messed up partition, flag or something else is wrong with the SD card or it's structure.
I would recommend (although it is more work) that you try the Linux Partition method. The additional work will come from having to find a bootable version of Linux.
I created a brief outline of various methods HERE. Perhaps you could one a go and use Gparted instead of Windows to partition the SD.
It's worth a shot.
thanks ill try tomorrow
EDIT: ignore post.
Sent from my BNTV250 using Tapatalk
well i tried again to put these files on, this time using ubuntu and it still doesnt boot. ive setted the flags and put the files from http://forum.xda-developers.com/showthread.php?t=1446987 into my "root" partiotion which has the boot flags and so on but it still doesnt boot cwm. Do i need to press any keys while booting?
My Nook Tablet is rooted btw, should i do a factory reset and maybe make a movie? I really dont know what more i can do
Try the following (Linux) to unzip the files and get them on the SD. This could be the problem. Simply opening them and dragging them might not properly decompress them. Thank you to CelticWebSolutions for the following steps which I copied from the CM7 Rom Thread.
Open a terminal window and issue the command:
sudo file-roller
You will be asked for your password and after that a zip software window will open up, click open open and find the file "NT-CWM-SD.zip".
Drag all the files form this archive into your newly created system partition on your sd.
This can take a couple of minutes to actually complete so be patient, often it looks like it's finished but it's still copying in the background.
Close all windows and right click on your SD card on the desktop and select to "safely remove drive" if files are still writing to the disk it will warn you and the warning windows won't disappear until the files have finished writing to you SD.
Make sure you leave the SD in there until this process has finished otherwise your card probably won't work.
do you mean system partition or boot partition?
Edit:
my created partitions are all primary:
first partition with the cwm files on it: 50MB - Primary - FAT 32 - boot and lba flag
second partition: nothing on it - 2000MB - Primary - EXT4 - no flags
third partition: nothing on it - 2000MB - Primary - EXT4 - no flags
Pain12345 said:
do you mean system partition or boot partition?
Click to expand...
Click to collapse
Boot. My bad on choice of words. Bottom line is the card should look the same as the first one you tried. I'm only trying to insure that the files get extracted properly.
Also, to eliminate possible variables that may be causing yourissue, make sure the USB cable is plugged in when you try to boot.
Fingers crossed.
yea copied the files like you said and it still doesnt work. The nook does start and instantly boots "nook reader" not cwm. I really dont know what mroe i should do, i might record a movie if im home.
While booting the nook i have connected the usb cable
Thats how my partitions look like:
first partition with the cwm files on it: 50MB - Primary - FAT 32 - boot and lba flag
second partition: nothing on it - 2000MB - Primary - EXT4 - no flags
third partition: nothing on it - 2000MB - Primary - EXT4 - no flags
Edit2:
i didnt fill the sdcard with zeros, should i do this b4 partitioning?
Also my Nook is rooted, does this matter?
Indirect's APK?
I couldn't get the SD card method to work either and then I found Indirect's APK and that worked perfectly, just a thought... It's in the development section.
Really trying to help you here. Honestly I have never used the method in the actual CWM thread but I have successfully on two occasions created bootable SD cards. It is my understanding that it is the way the card is partitioned that tells and allows the system to "boot" from it. That said I have copied the instructions from the CM7 Rom thread below which use the Linux GParted partitioning method. Not having the SD card setup properly is the only thing I can think of to help at this point besides perhaps that you have a bad card. Try the below (which it sounds like you already have) just to be 100% sure the card is setup properly.
Delete all partitions on your SD card first using GParted and use the following
------------Thanks CelticWebSolutions--------------------
Open GParted select your SDcard in the top right hand side of the window.
Select create partition table form the device menu select the empty space on the newly wiped SD card and click the paeg icon with a green plus on it, a window will appear with some boxes to fill in, change the box that says New Size (Mib) to 50, Change file system to Fat32 and write boot in the label., then click add.
Again click on the unallocated space and add another partition as around 2000(MiB) as EXT4 and label it as system (LandMaster Note: Not needed for CWM only)
Add a 3rd partition in unallocated space again of about 2000(MiB) EXT4 and label it as data. (LandMaster Note: Not needed for CWM only)
now you have three partitions waiting to be created click the green tick to apply your changes
Once changes have applied right click on boot and select the menu item 'Manage Flags', tick boot and lba and close the window, your SDCard is now ready to get it's data for it to work
-------------------------------------------------------
You DONT even need the 2nd (system) and 3rd (data) partition as outlined above if all you want is a bootable CWM. Just one (I used 74MB) MS-DOS (FAT32), Active Partition with "boot" and LBA" flags set.
Lastly, since you are rooted you could always flash the internal recovery partition with CWM using the method in This Thread and get into CWM by clicking reboot recovery from within the app.
I never did ask .... What is your ultimate goal?
I spend a few more hours to it and it still doesnt work. Via the app i can run cwm but only via the app. The goal is that i have a working recovery sd card if i brick my nook..
I installed ubuntu on my computer and i did exactly the same steps like you have posted but it wont work. Ive also tried multiple other sd card but that didnt change anything
Maybe any development settings on the nook that i should change?
As i live in germany would maybe anyone of u sell me a working sd card with cwm on it so i can test?
Pain12345 said:
I spend a few more hours to it and it still doesnt work. Via the app i can run cwm but only via the app. The goal is that i have a working recovery sd card if i brick my nook..
I installed ubuntu on my computer and i did exactly the same steps like you have posted but it wont work. Ive also tried multiple other sd card but that didnt change anything
Maybe any development settings on the nook that i should change?
As i live in germany would maybe anyone of u sell me a working sd card with cwm on it so i can test?
Click to expand...
Click to collapse
Thats what I thought and it is a good plan. Unfortunately I'm stumped.
Albert Wertz is in the SD Card "business". Check with him to see about getting one.
FYI, now that you have CWM "written" to the internal recovery partition you should be able to enter recovery even if you can't boot the tablet to android.
N+Pwr from off condition should do the trick.
Pain, sorry, I just saw this thread. I made a small update to the instructions. I left out something which I thought was obvious. This was a fault on my part. Did you label each partition correctly? It should be BOOT, system, and data.
I used this method (don't forget the ext4fsd part) and it does work. But if you're still having trouble the CD-boot version of Ubuntu will work just fine too.
i allready have ubuntu running on a cd, in the past i labeld it "boot" (case sensitiv - all small letters) so this could be the fault?
Edit:
i can see that cwm work, it pops up 4 a half second or even less if i start the nook but than it instantly disappears
after installing cwm on my NT after that (my B&N store has been disabled and it doesn't let search, download, or view anything on the store..... has anyone a solution to this issue