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...
Related
I am not sure if this is the best place to post, if not mods please feel free to move it as needed.
I have version of CM7, Nookie FroYo and NookHoney. I am trying to figure out how to unpack and repack the these images so I can make a custom CM7 that boots from SD Card as I don't want to write to eMMC to try CM7. I know CM7 is still in late Alpha/early Beta but I would love to be able to run in from SD. I understand people wanting to make things run from eMMC but there are those of us who don't want to constantly rebuild our Nooks just because we want to try new things. I have looked online and played around with different ways to try and extract these things and nothing seems to work. I know there has to be a way to get it working or these custom ROMs would not exist. Can someone point me directions for unpacking, modifiy and repacking these items so they can be turned into an SD bootable image? Something that works.
As a side note I would also like to know how I can mount these IMG files under ubuntu as they are multiple partitions and I can't get them to mount.
Thanks
For the CM7 bootable SD, you'll need to create 5 partitions in the following order: boot (fat32), system (ext4), data (ext4), cache (ext4) and sdcard (fat32). Give /boot the boot flag. Use gparted, round to cylinder and 1mb space at the beginning of each partition except boot.
Then you need to edit the uRamdisk (boot), (see nookdevs nookie technical page) to mount the previously created partitions. For instance, change mmcblk0p5 to mmcblk1p2.
Then copy CM system files to /system. Data and cache will stay blank before first boot.
Use loop mount to access your img file. Google It..
You'll also need to change vold.fstab (/system/etc) to mount sdcard on mmcblk1p5.
Use stock mlo and u-boot.bin for /boot.
Regarding partition size, I guess 50mb is enough for boot, 500mb for system, 1 or more gb for data, 400mb for cache and as much as possible for SD..
Sam
Sent from my HTC Desire using XDA App
Yowza. If anyone manages to pull this off, how about posting an IMG for the rest of us?
Awesome! Thanks for all the details. One more details question, about the *.bin files. What format are they in? I've tried opening them to explore them; but I haven't had any luck. The best I could do was a binary/hex editor, but it was still mostly garbage to my untrained eye.
Thanks!
Dave
You can't simply edit .bin files. They're compiled from source.
You'll have to build it yourself it you want to change anything..
NullP said:
Yowza. If anyone manages to pull this off, how about posting an IMG for the rest of us?
Click to expand...
Click to collapse
That would be the most efficient way... instead of everyone doing the same thing, one person does it, and then the other people contribute something else.
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.
Hi again everyone,
I've noticed that some people have been inquiring about getting their Stock Nook Color rom onto an SDcard. And due to legal issues with distributing the B&N rom. It would not be wise to just "dd" the stock partitions to an .img file and post it for everyone to share. On top of the fact that each Nook has the /rom and /factory partition which stores each devices unique id's. So to work around that, here's an image file with a flashable .zip that will move your stock partitions to your SDcard via a modded CWM that is preinstalled with the .img file. Hope I'm not confusing anyone?!
**DISCLAIMERS: Please read and accept all that is noted below in red**
1-I do not take responsibility for whatever happens to your Nook Color. You are doing this at your own risk. If you are unsure about what's going on here. Then I'd suggest leave your Nook how it is!
2-I tried not to mess with the /rom partition because it stores very important unique device identifiers in that partition. But no matter what I did, it kept stalling on boot. However, I did leave the /factory partition alone. Which stores a rombackup.zip of your device id's. So I would suggest backing up these two very important partitions and store it somewhere safe!
3-On the above note. This is very important. Do not try and use this SDcard on any other nook than your own. I'm not sure what will happen. But I really don't want to find out.
4-Never, ever have the same Nook Stock rom running at the same time for any reason. This will intefere with the B&N servers and send a signal to De-authorize and wipe your nook. On top of that. It might just brick your nook from ever registering again!
5-This is mounting your internal partitions to copy over to the SDcard partitions. So again, if you are unsure or hesitant or not brave enough to touch your EMMC partitions. Please drop your SDcard that you were about to burn and walk away, slowly...
6-I assume you accept all the above. If so, please continue reading for the fun stuff!
Credits:
Rookie1 (for the initial eclair2dualboot script)
Nemith (for CWM Recovery used)
NOOK Stock to SD v0.1
What we have here is an .img file with partitions already created and ready for you to transfer your Stock Nook rom over to your SDcard. I would like to thank rookie1 for his initial script for moving Stock Eclair to Dualboot. I just took that and modified the script to work with the SDcard install. The script will still make use of your internal 5gb emmc Media partition as well. This will also modify all the necessary files on the fly to work with your Nook SDcard Rom (eg. uRamdisk, vold.fstab...etc).
I made the .img file around 7.4 gb so that people won't have issues burning it to an 8gb card. If you want to get use of the full 8gb or 16gb card. Use EASUS partition tool to extend the /sdcard (8th) partition.
FYI: I still for some reason or another can't grasp the CWM Recovery progress bar! Totally lost when it comes to inserting the correct values in the edify script. It extends past where it should end. I'm sure it's something very simple and maybe my mind is just too tired or better yet lazy to figure it out. So if anyone can advise me on the issue, please do.
Instructions and Pre-requisites:
**Backup your NOOK!!!!!**
1-You need a Nook Color with stock rom on EMMC already registered (root it now if you wish)
2-An 8gb uSDcard or larger
2-Download Nook Stock 2 SD v0.1
3-Unzip and follow directions from Nookdevs.com to burn the .img file to your SDcard
4-Power off Nook
5-Place the SDcard that you just burned stock2sd_v0.1.img to in your Nook and power on
6-It will boot to CWM Recovery. Now choose to "install zip from sdcard"
7-Now select "choose zip from sdcard"
8-Choose "stock2sd_v0.1.zip" and confirm "yes"
9-Sit back and wait... be patient! This will take a while.
10-When finished it will say "Can you believe it! It's stock Nook on your SDcard!"
11-Leave SDcard in Nook and go back to CWM main menu and choose to "reboot system now"
12-Enjoy your Stock Nook rom on your SDcard! Now go flash all the other roms to your EMMC!
Edit 5/9: I noticed that some people have issues with the .img file when uncompressed. So I've uploaded an alternative file to try if the first didn't work. The new file is a 7zip file. It offered better compression so the file size is much smaller as well. Hope this helps out the few that had issues.
Download:
stock2sd_v0.1a.zip
MD5-4aecd4f8fc4d7c40bbe392d8cb970853
4shared | Rapidshare
Update: 5/9 stock2sd_v0.1.img.7z
MD5: b72dd3cc0413b6fdadf899cfdf48b24e
4shared | Rapidshare
Click to expand...
Click to collapse
For anyone that has an alternative rom on your EMMC already. Mr_fosi wrote a nice write up on how to backup your current rom, restore to stock, copy stock to SD, and then revert back to your original setup on EMMC. Don't forget to give him a thanks for the great write up!
Mr_fosi's Guide
Hey, if I've helped in someway. Please show your appreciate with a thanks in one way or another!
Thanks,
Racks
Will try this as soon as I get a new SD card... have been wanting to be able to do this for a while, thanks!
Thanks for this!
Sent from my NookColor using XDA Premium App
Would this be the correct steps for getting rooted Stock Rom 1.2 to run from sd card if we are using Phiremod V6.2 OC 4/24 from the EMMC and want to restore it when we are done. Would sometimes boot from rooted stock sd card and other times boot from Phiremod V6.2 EMMC with a 16GB data sd card containing movies and music.
First of all thanks for making this.
1) Use Titanium Backup "Batch" option to "Run Backup all user apps + system data".
2) Have ClockworkMod 3.0.1.0 (or higher) in EMMC. Use ROM Manager v4.2.0.2 (or higher) to "Backup Current ROM". I like to append a PhV6.2 to the end of the file name. This procedure is referred to as making a Nandroid backup.
3) Mount your current sd card on a pc and copy the folder TitaniumBackup to it. Open the folder clockworkmod on the sd card and copy the Nandroid backup folder made in step 2) to the pc. This is for backup purposes. Not used in the procedure.
4) Use the procedure in thread "[UPDATE ZIP] Stock 1.2 update.zip flashable from CWM" to change your EMMC ROM back to stock. There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot). Not sure which one to use? Perfer the doesn't replace CWM, will this work with the procedure in this thread to move "Nook Stock to SDcard Image[5/3]"?
5) Use the procedure in thread "ManualNooter 4.5.2 (For Stock 1.2)" to root your nook.
6) Use the procedure in this thread "[ADV][DEV][CWM]Nook Stock to SDcard Image[5/3]" to move the rooted 1.2 to the sd card.
7) Install original sd card. Manually Boot into EMMC Recovery (ClockworkMod 3.0.1.0 or higher - hold Power button + n button for 6 seconds). Restore the Nandroid backup folder made in step 2).
OP udated with download link.
Thanks,
Racks
Will buy an SD and give this a shot.
Quick confirmatory questions:
- Having read the OP, it seems as though you are not intentionally modifying the partitions or their contents on the EMMC, correct?
- I haven't looked at the script, but what you wrote here says that they are only mounted and copied, yes?
- Finally, this does not change the read/write flag on any of the partitions on the EMMC?
Thanks for the work on this, I sure hope it works when I try it!
lschroeder said:
... Stock Rom 1.2 to run from sd card if we are using Phiremod V6.2 OC 4/24 from the EMMC ... Would sometimes boot from rooted stock sd card and other times boot from Phiremod V6.2 EMMC with a 16GB data sd card containing movies and music...
.
Click to expand...
Click to collapse
Eventual goal is to replace Phiremod V6.2 EMMC with a ROM based on CM7.1.x that has sleep fixed, wifi staple, bluetooth range extended - bluetooth keyboard functioning with wifi, hardware accelerated with over clocking at 1200/1300 and a rooted Stock 1.2 for the magazine and other reader features. Guess I am asking for a lot but I have faith in you developers!
mr_fosi said:
Will buy an SD and give this a shot.
Quick confirmatory questions:
- Having read the OP, it seems as though you are not intentionally modifying the partitions or their contents on the EMMC, correct?
- I haven't looked at the script, but what you wrote here says that they are only mounted and copied, yes?
- Finally, this does not change the read/write flag on any of the partitions on the EMMC?
Thanks for the work on this, I sure hope it works when I try it!
Click to expand...
Click to collapse
1-Not modifying anything on EMMC
2-Yes mounted then copied
3-It shouldn't change any or the read/write flags on your EMMC
Thanks,
Racks
Awesome.
This looks to be worth undoing my nice CM7 install, reverting back to 1.1 (then upping to 1.2) for. I would very much like to get some of the stock functionality back and this looks like a great way to do it without having to modify my EMMC partition table.
The dual-boot option looked promising as well but I really don't want to mod the partitions on this thing, especially since I use CM7 most of the time.
lschroeder said:
Would this be the correct steps for getting rooted Stock Rom 1.2 to run from sd card if we are using Phiremod V6.2 OC 4/24 from the EMMC and want to restore it when we are done. Would sometimes boot from rooted stock sd card and other times boot from Phiremod V6.2 EMMC with a 16GB data sd card containing movies and music.
First of all thanks for making this.
1) Use Titanium Backup "Batch" option to "Run Backup all user apps + system data".
2) Have ClockworkMod 3.0.1.0 (or higher) in EMMC. Use ROM Manager v4.2.0.2 (or higher) to "Backup Current ROM". I like to append a PhV6.2 to the end of the file name. This procedure is referred to as making a Nandroid backup.
3) Mount your current sd card on a pc and copy the folder TitaniumBackup to it. Open the folder clockworkmod on the sd card and copy the Nandroid backup folder made in step 2) to the pc. This is for backup purposes. Not used in the procedure.
4) Use the procedure in thread "[UPDATE ZIP] Stock 1.2 update.zip flashable from CWM" to change your EMMC ROM back to stock. There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot). Not sure which one to use? Perfer the doesn't replace CWM, will this work with the procedure in this thread to move "Nook Stock to SDcard Image[5/3]"?
5) Use the procedure in thread "ManualNooter 4.5.2 (For Stock 1.2)" to root your nook.
6) Use the procedure in this thread "[ADV][DEV][CWM]Nook Stock to SDcard Image[5/3]" to move the rooted 1.2 to the sd card.
7) Install original sd card. Manually Boot into EMMC Recovery (ClockworkMod 3.0.1.0 or higher - hold Power button + n button for 6 seconds). Restore the Nandroid backup folder made in step 2).
Click to expand...
Click to collapse
I don't think it matters which restore to stock .zip you use. This script will basically copy what ever setup you have on your EMMC to your SDcard. Your steps are correct as I see it. Please advise if the steps you took worked or not.
Thanks,
Racks
I am getting a corrupt error when unzipping img with winrar. I have download 3 times different download places.
patgnds said:
I am getting a corrupt error when unzipping img with winrar. I have download 3 times different download places.
Click to expand...
Click to collapse
Thanks for advising. I'm checking the download now. Anyone else have the same issue?
The problem seems to be in the reported size of the original file within the zip.
In mine (downloaded from the hated Rapidshare):
- Compressed size: 120,494 kb
- Original size: 807,167,488,681,452 kb
Maybe a corrupt compression?
Same issue...corrupt, download size is 4k.
Sent from my HTC Vision using XDA Premium App
mr_fosi said:
The problem seems to be in the reported size of the original file within the zip.
In mine (downloaded from the hated Rapidshare):
- Compressed size: 120,494 kb
- Original size: 807,167,488,681,452 kb
Maybe a corrupt compression?
Click to expand...
Click to collapse
Thanks for the advise. I'll take down the link until further notice. Sorry for this everyone.
Thanks,
Racks
Edit: I've just downloaded it to my mac at work and used Stuffit Deluxe to unzip it. And it unzipped and mounted fine for me. I'll see if I can rezip this one and reupload.
The MD5 of the file I have matches the one posted in the OP, so I am fairly sure the download wasn't corrupted. It seems to be a problem with the original file uploaded.
A quick re-zip might fix the issue.
I did burn the rom and installed the zip from cwr it worked.
So you must have been able to unzip the IMG? Can you share the zip file you used and post it's MD5?
Dual boot setup.
Does this copy all partitions on the emmc or just the first boot partitions? I have dual boot setup with stock on the second boot. If I could just copy the whole setup to an sd card it would be pretty slick. Thanks for your hard work.
1CF71B239DB860A36CD70C3FB8F70FEC
partitions
boot
rom
factory
system
data
cache
sdcard
NOTE: to build CM10.1 SD card, see http://forum.xda-developers.com/showpost.php?p=36685310&postcount=1.
[Caveat emptor: adopt/follow this guide at your own risk].
FWIW, below is a digest of the process to create a SD card running CM10.0 builds by XDA Developer Succulent which is posted at his blog http://iamafanof.wordpress.com and which I have used to build a CM10.0 SD card for my 16GB Nook Tablet:
Download the pair of files cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip and cm-10-yyyymmdd-UNOFFICIAL-acclaim_sd_hd.zip from http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/, and SD_Boot.zip from http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/.
Download gapps-jb-20121011-signed.zip from http://goo.im/gapps/gapps-jb-20121011-signed.zip.
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create 4 partitions: boot (Primary, FAT32), system (Primary, Ext4), data (Primary, Ext4), and sdcard (Primary, FAT32). Set the partition ID type for the boot partition to 0x0C FAT32 LBA and set its Active flag (otherwise the SDcard will not be bootable). Once this is done, the boot partition should appear as a (read/write accessible) drive under Windows. (Note that you can adjust the suggested sizes of the partitions upward to fill up the entire SDcard; FWIW the sizes I use on my 8GB card for the 4 partitions are, respectively: 0.5GB/0.5GB/2GB/[remainder of SDcard]).
Copy to the boot partition of the SD card the following files from cm-10-yyyymmdd-UNOFFICIAL-acclaim_sd_hd.zip: boot.img (in folder p2), flashing_boot.img, MLO, recovery.img, u-boot.bin.
Modify the zip files using drag and drop with winrar/winzip (do not extract and repack the zip files):
Replace updater-script in folder META-INF\com\google\android of cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip with the updater-script from in folder p2 of cm-10-yyyymmdd-UNOFFICIAL-acclaim_sd_hd.zip.
Replace vold.fstab in folder system/etc of cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip with the vold.fstab from folder CM10_Jelly_Bean\1_os of SD_Boot.zip.
Replace updater-script in folder META-INF\com\google\android of gapps-jb-20121011-signed.zip with the updater-script in folder CM10_Jelly_Bean\p2\gapps of SD_Boot.zip.
Copy to the boot partition of the SD card cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip (that get modified with the replacement updater-scripts and vold.fstab files in the above steps).
Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display.
Select SDC Recovery.
[Optional but recommended step, in case you accidentally forget to replace the updater-script file(s)] Select Backup to backup your current NT config (/boot, /recovery, /system, and /data).
Select "Install zip from SD card" and install the modified cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip file.
Select "Install zip from SD card" and install the modified gapps-jb-20121011-signed.zip file.
Select "Power off" to turn off the NT.
Boot the NT from its power off by inserting a powered USB cable; after about a minute you should see boot animation lasting for a few minutes followed by initial wifi network and google account setup process, after which your CM10 on SD is ready for use.
A few additional points worth noting:
If you plan to backup your NT current ROM config then add to the boot partition size at least 600MB for each backup (to save space you can copy/archive backup data folders to your PC and remove their copy from the boot partition).
Generally the lower rating (and also cheaper) class 4 SD cards are more suitable for running a ROM than the higher classes 6 and 10 cards (since the latter are optimized for large & sequential block read/write at the expense of random read/write). So if you happen to use a class 10 or 6 card and your apps frequently crash or freeze, consider switching to a lower class SD card.
Did you ask succulent if it was OK to post his work here? Someone already did it in the dev section and he was a little upset that he wasn't even consulted about it.
Sent from my CM 10 SD nook tablet. Thanks devs.
Thanks for the tutorial. I've used XDA for a long time and loaded lots of custom ROM's, but I'm finding this Nook Tablet situation ridiculously complicated. I'm having trouble understand your step number 8.
"Copy to the boot partition of the SD card and gapps-jb-20121011-signed.zip..." doesn't make grammatical sense. Is there a typo here?
sanjosanjo said:
Thanks for the tutorial. I've used XDA for a long time and loaded lots of custom ROM's, but I'm finding this Nook Tablet situation ridiculously complicated. I'm having trouble understand your step number 8.
"Copy to the boot partition of the SD card and gapps-jb-20121011-signed.zip..." doesn't make grammatical sense. Is there a typo here?
Click to expand...
Click to collapse
I just looked at it and it appears you are failing to read it. There are clear and concise instructions as provided by Succulent and cut and pasted by digimax.
It clearly says to copy the ROM and the gapps.
Sent from my CM 10 SD nook tablet. Thanks devs.
SlowCobra96 said:
I just looked at it and it appears you are failing to read it. There are clear and concise instructions as provided by Succulent and cut and pasted by digimax.
It clearly says to copy the ROM and the gapps.
...
Click to expand...
Click to collapse
There were indeed typos in the cited paragraph (thanks to sanjosanjo for spotting them), and I already fixed them.
digixmax said:
There were indeed typos in the cited paragraph (thanks to sanjosanjo for spotting them), and I already fixed them.
Click to expand...
Click to collapse
Did you reword them from succulents site because those are what I used when I did my SD card and I had zero issues following them.
Sent from my CM 10 SD nook tablet. Thanks devs.
On Step 8, did you mean to copy the cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip to the boot partition instead of the cm-10-yyyymmdd-UNOFFICIAL-acclaim_sd_hd.zip because in step 12 you say to install cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip? I've followed your steps for replacing the files, but did not put the sd_hd.zip on the SD card, only the normal acclaim.zip.
I'm going to try it now and see what happens.
Edit: says installation aborted. This was when trying to install the cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip that has had the files replaced from the sd_hd.zip
LucasMN said:
On Step 8, did you mean to copy the cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip to the boot partition instead of the cm-10-yyyymmdd-UNOFFICIAL-acclaim_sd_hd.zip because in step 12 you say to install cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip?
...
Click to expand...
Click to collapse
Yes (I corrected it).
LucasMN said:
...
Edit: says installation aborted. This was when trying to install the cm-10-yyyymmdd-UNOFFICIAL-acclaim.zip that has had the files replaced from the sd_hd.zip
Click to expand...
Click to collapse
I had neglected to indicate in step #3 that the partition type of /system and /data is (Primary, Ext4).
digixmax said:
FWIW, below is a digest of the process to create a SD card running CM10 builds by XDA Developer Succulent which is posted at his blog http://iamafanof.wordpress.com and which I have used to build a CM10 SD card for my 16GB Nook Tablet (caveat emptor: adopt/follow it at your own risk):
Click to expand...
Click to collapse
thanks for this great thread digixmax. what is the difference between your method and just directly writing succulent's IMG file to a card?
his post looks like it was updated 12/25, although perhaps the image file is from 12/08. is yours updated since then?
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
zeiss74 said:
thanks for this great thread digixmax. what is the difference between your method and just directly writing succulent's IMG file to a card?
his post looks like it was updated 12/25, although perhaps the image file is from 12/08. is yours updated since then?
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Click to expand...
Click to collapse
First off, just to be clear: I did not invent this process, rather my post is intended to be a streamlined digest of Succulent's blogs on how-to build CM SDcard -- including in particular the blog http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/. This process gives you the maximum flexibility at the outset in sizing the partitions, creating extra partitions, etc. This process has also worked for some of the other CM10 builds that are available on XDA such as ChrisHoffman's and Hashcode's builds, as well as the Paranoid Android build posted on Succulent's blog.
Succulent's pre-made SD card image is the simplest/quickest way to create a bootable SDcard of his CM10 builds: you just download and write the image to SDcard and it's ready to go. It's possible to adjust the partition sizes after the image is written to the card but with some risks of messing up the partition table which could make the SDcard not bootable. There have also been reports that NTs running these images appear to have same identical MAC address, thus any two of these NTs will not be able to get on the same LAN (e.g., in the same household WiFi LAN) at the same time.
Re: Succulent's v12/25: I just flashed it (internally on emmc) today and it works great, but he has not posted cm-10-xxxxxxxx-UNOFFICIAL-acclaim_sd_hd.zip for it so you'll have to wait a bit if you want to build the image from scratch.
digixmax said:
First off, just to be clear: I did not invent this process, rather my post is intended to be a streamlined digest of Succulent's blogs on how-to build CM SDcard -- including in particular the blog http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/. This process gives you the maximum flexibility at the outset in sizing the partitions, creating extra partitions, etc. This process has also worked for some of the other CM10 builds that are available on XDA such as ChrisHoffman's and Hashcode's builds, as well as the Paranoid Android build posted on Succulent's blog.
Succulent's pre-made SD card image is the simplest/quickest way to create a bootable SDcard of his CM10 builds: you just download and write the image to SDcard and it's ready to go. It's possible to adjust the partition sizes after the image is written to the card but with some risks of messing up the partition table which could make the SDcard not bootable. There have also been reports that NTs running these images appear to have same identical MAC address, thus any two of these NTs will not be able to get on the same LAN (e.g., in the same household WiFi LAN) at the same time.
Re: Succulent's v12/25: I just flashed it (internally on emmc) today and it works great, but he has not posted cm-10-xxxxxxxx-UNOFFICIAL-acclaim_sd_hd.zip for it so you'll have to wait a bit if you want to build the image from scratch.
Click to expand...
Click to collapse
thanks!
also, dumb question but if you "remove SD card" in step 14, how is "CM10 on SD ready for use" in step 15? do you reinsert it?
zeiss74 said:
also, dumb question but if you "remove SD card" in step 14, how is "CM10 on SD ready for use" in step 15?
Click to expand...
Click to collapse
Mistake on my part, leave the card in the NT.
ok, worked great (the second time). the first time i used 7zip to change the zip files, but then i read a readme.txt from succulent that said to only use drag and drop with winzip/winrar to change the zip files, so i downloaded winrar and it worked. the first time i got the "installation aborted" error.
thanks again, i'm super excited to try CM10. been wanting to update this NT for some time now.
Just an FYI it isn't the pre-made image file that causes the repeating MAC Address it is something in the CM 10 build. I have 2 NT 16's running different build dates of CM 10 SD and both have identical MAC Addresses. Somewhere in the build of CM 10 it appears that it is taking the MAC Address from a developer unit and applying it to everyones NT. Or so it would appear.
SlowCobra96 said:
Just an FYI it isn't the pre-made image file that causes the repeating MAC Address it is something in the CM 10 build. I have 2 NT 16's running different build dates of CM 10 SD and both have identical MAC Addresses. Somewhere in the build of CM 10 it appears that it is taking the MAC Address from a developer unit and applying it to everyones NT. Or so it would appear.
Click to expand...
Click to collapse
My NT has the same MAC address regardless of whether it's running stock, running CM10 internally or off SD card.
I think there is something wrong with your build images or possibly with your NTs (you can look up the NTs' MAC addresses in /rom/devconf/MACAddress on their emmc).
digixmax said:
My NT has the same MAC address regardless of whether it's running stock, running CM10 internally or off SD card.
I think there is something wrong with your build images or possibly with your NTs (you can look up the NTs' MAC addresses in /rom/devconf/MACAddress on their emmc).
Click to expand...
Click to collapse
So I have 2 broken NT's that despite the stock os showing the correct MAC Addresses and even the Mac config files showing the correct to the individual NT Mac address, when I load CM 10 despite not doing anything to change the configuration files other than updater-script, I broke it? Really?
And on top of that the pre-made images are known to have the same Mac address. Though the exact same files, sans imager program, couldn't possibly be problematic?
Somehow I doubt your stock os, if your using the succulent build for cm10, has the same Mac address.
Does your MAC end in 9f:fd ?
Sent from my CM 10 SD nook tablet. Thanks devs.
SlowCobra96 said:
So I have 2 broken NT's that despite the stock os showing the correct MAC Addresses and even the Mac config files showing the correct to the individual NT Mac address, when I load CM 10 despite not doing anything to change the configuration files other than updater-script, I broke it? Really?
And on top of that the pre-made images are known to have the same Mac address. Though the exact same files, sans imager program, couldn't possibly be problematic?
Click to expand...
Click to collapse
If your two NTs running stock OS still show two distinct MAC addresses then I don't think you have broken the NT per-se. Most likely you simply didn't properly build one or both of CM10 SDcard images. Your problem is the type Succulent often refers to as "residue" problems.
Somehow I doubt your stock os, if your using the succulent build for cm10, has the same Mac address.
Click to expand...
Click to collapse
It is the same MAC address, but believe whatever you want.
Does your MAC end in 9f:fd ?
Click to expand...
Click to collapse
Nope.
Then im a ****ing idiot and you are a god. Shrug. I am an not adverse to admitting when I am wrong, however in this situation I don't believe I am. Apparently my 2 NT's are completely special. Oh wait, anyone running the Image files have the same issues. There is nothing shared between the two NT's. SD cards arent shared. Not a single file is shared. Not even the build date of the CM 10 files is shared. So again I say, there is a problem with the SD version of CM 10 not reading the correct MAC. How you got lucky with your mac reading correctly from SD and EMMC I don't know, especially considering anyone else that has multiple NT's in the same house suffers the same issue.
i have two followup questions to help me better understand this setup.
1. what are the different partitions on the card? and why wouldn't we make the boot partition as large as can be? i went to back up my NT apps (about 100) to bring them to my CM10 card, and they are 800MB, and the only partition i can copy them to from my PC is boot. so i'm out of luck with 500MB (250 MB free). also, since boot is the only partition i can access from my PC, it means that's where all my videos and music will have to be copied. so it seems like i should make boot 4+ GB. i don't own any large apps (like those 2 GB racing games) so i would guess my other partitions don't need to be huge. am i missing anything? with the tablet up and running but few apps, the 0.5GB boot partition is about 50% full, the 0.5 GB system partition (no longer labeled such) is 64% full, while 2GB data and 4.5GB sdcard are 5% and 0% used (per minitool)
2. if this doesn't change the stock NT, then what are steps 10 and 11 doing? where are they installing something? from the SD card to the SD card, maybe in another partition? do i need to keep those zip files on the boot partition once they are installed?
thanks for any assistance to help my understanding.
Beware, this guide is more or less untested, it will interfere with stuff like memory encryption and OTA or other firmware updates. You have been warned, I assume no warranties for bricked phones, SD cards or lost data.
Many cheap-ass Mediatek phones ship with Android 4.4.2 or later and only ridiculous amounts of internal storage (2GB in my case, CAT B15Q). That may be enough for basic apps, but as soon as you install Navigon or other data-heavy apps (or WhatsApp with a load of videos) you're going to run out of space in no time - and because Google is a bunch of fools, they disallowed app installations to SD cards entirely in 4.4!
So, we're going to move /data in its entirety to our nice huge SD card and be able to use even bigger apps on small phones. It might be possible that this guide works on other phones, but that depends on how they boot and where the fstab and init.rc reside!
Prerequisites:
Mediatek-based 4.4.2 or later phone with root access in recovery (boot it in recovery, run adb shell, therein run id. If it says root, all fine. If not, install CWM)
A large enough SD card (I chose a 32GB card with a 50:50 split between /data and the "external sd card")
Solid Linux knowledge, one Linux PC and one Windows PCs. I urge you to NOT use any kind of VM unless you have experience with USB passthrough.
spFlashTool and the Mediatek drivers from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774, for a flashing guide see http://forum.xda-developers.com/android/help/howto-firmware-flashing-cat-b15q-t2989627
mtkdroidtools from https://www.androidfilehost.com/?fid=23501681358558543 on the Windows PC
mtk-tools from https://github.com/bgcngm/mtk-tools on the Linux PC (no, Cygwin does not work, it messes up the permission bits), cloned on an ext4 partition (not sure if ext2/3 can handle the extended permission bits...)
a network connection between the PCs or a USB stick to transfer files
Take the sd card out of the phone and insert it into your computer. Many laptop SD slots don't like SDXC (>4GB), you might need e.g. a Huawei 3G stick or a SDXC-compatible USB dongle.
Repartition the SD card using Acronis Disk Director, gparted or whatever you're familiar with. The first partition must only be resized (this is the FAT partition), the second partition is a ext4 (!) partition. Both MUST be primary partitions. Acronis and other tools on Windows might require a reboot to repartition SD cards. I recommend a 50:50% split, but if you're heavy on apps or their data, you might go for a 25% FAT: 75% EXT4 split.
Boot your phone into recovery, connect to it with adb in a root shell.
Assuming your data partition is at /dev/mmcblk0p8 (look in /fstab to find it out, followed by mount /data and ls /data to verify), execute the command "dd if=/dev/mmcblk0p8 of=/dev/mmcblk1p2", wait until it is finished. This can take up to ten minutes or more, depending how much data there is.
Shut down the phone, take out battery and SD card.
Insert the SD card into your Linux machine, run resize2fs /dev/sdb2 (or wherever the ext4 sd card partition ended up, check it in dmesg) as root so that the filesystem grows; then eject the SD card and put it back into your phone
Readback your BOOTIMG partition, transfer it to the linux PC (or, if you already have a boot.img for your current firmware, use this one)
On the Linux PC, open a rootshell (to avoid permission issues when building the ramdisk).
Run "./unpack-MTK.pl /path/to/bootimg"
"cd boot.img-ramdisk" (directory might be named different, depending on how you named the bootimg dump file)
Using a text editor, edit the "fstab" file(s) (there might be multiple, with suffixes): From (adjust if needed)
Code:
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,encryptable=footer
to:
Code:
/dev/block/mmcblk1p2 /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,encryptable=footer
Now, edit the init.rc file (beware, other .rc files in the ramdisk root might also contain mount commands!).
Search for "on fs_property:ro.mount.fs=EXT4" and again replace /[email protected] (or whatever the node for /data had been) with /dev/block/mmcblk1p2 in the commands in this block (should be fsck, tune2fs,ext4_resize and mount).
Repack the boot image: ./repack-MTK.pl -boot boot.img-kernel.img boot.img-ramdisk/ /path/to/newboot.img
Transfer newboot.img to the Windows PC and flash it using spFlashTool
boot your phone, look in Settings->Memory to see if it went OK!
If the memory view didn't change, also modify the other blocks of on fs_property, in case your device does not use an ext4 rootfs (but yaffs or ubifs instead).
Functionality
It is a good idea, but
Are I still have part of it as external storage?
If yes, it means I can not remove it because there are some apps used it.
If no, it means I will not have external storage anymore!
e.ahmedmahfouz said:
It is a good idea, but
Are I still have part of it as external storage?
If yes, it means I can not remove it because there are some apps used it.
If no, it means I will not have external storage anymore!
Click to expand...
Click to collapse
The SD card is now both internal and external storage! You are not able to remove it because else your system will not boot anymore.
harddisk_wp said:
The SD card is now both internal and external storage! You are not able to remove it because else your system will not boot anymore.
Click to expand...
Click to collapse
what if the sd card is damaged ?
Can my phone boot again..or will booltloop
madthinker said:
what if the sd card is damaged ?
Can my phone boot again..or will booltloop
Click to expand...
Click to collapse
If you manage to kill your sdcard while you have my sdcard hack installed, then the phone will bootloop until you insert a new sd card partitioned just like the old one. Then it will act like you had factory-resetted it.
Alternatively you can always reflash original boot.img/recovery.img and use the phone with limited internal memory.
harddisk_wp said:
If you manage to kill your sdcard while you have my sdcard hack installed, then the phone will bootloop until you insert a new sd card partitioned just like the old one. Then it will act like you had factory-resetted it.
Alternatively you can always reflash original boot.img/recovery.img and use the phone with limited internal memory.
Click to expand...
Click to collapse
i see, thanks to explain me :good:
There is another way to get more space: Link2SD (2.- euros) with a second partition on your external SD-card exactly like shown above (ext4 partition, primary).
The advantage is, that if the sdcard is faulty the system still runs, just the apps which are symlinked to the ext4 partition won't run.
So I use this for all these not absolutely important apps which needs lots of internal memory, e.g. kindle bookreader, Amazon, WhatsApp etc. I dont use it for all apps, most importantly not for any app, where there is no alternative. Last week my two years old 64 GB MicroSD card (SanDisk, with warranty 10 years) in my SGS4 stopped working and this could happen all the time. They are not that reliable I think, that I would put my system on it.
I did this now with the Cat B15Q of my friend.
EDIT: and she has now more than 1 GB free internal space
I think this is the best solution, 2 GB for the pure ROM and the system apps is more than enough and all user apps go to the external sd-card (2nd partition).
good day!
hope you can help me.
what if i want vice versa? because my phone's default storage (0) is sd card.and i want my default storage will be its internal since it is 32gb rom. tried all ways but i think the answer is its boot.img. thank you..hoping for a help