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.
Related
Due to popular demand I have created a size-agnostic SDCard CM7 installer.
Also allows to install unmodified CM7 builds on SD card.
Current version: 1.3
Grab the installer image here:
http://crimea.edu/~green/nook/generic-sdcard-v1.3.img.gz
it's a ~9M image that would unpack into ~130M disk image.
Also note - not all SD cards are created equal. Here is a thread of interest is you have not bought one yet: http://forum.xda-developers.com/showthread.php?p=12964262
Short version: buy Sandisk-branded class 4 microSD cards.
Write the image on your SD card. I tested with 2G, 4G and 8G cards and all worked.
Any uSD card of 1G or bigger in size should work if it is recognized by your nook.
Write on Windows by using WinImage and on Linux/MacOS X by using dd (to the entire device, not one of the partitions. The device name should not have any numbers at the end. The command is something like dd if=/somewhere/generic-sdcard.img of=/dev/sdX bs=1024k)
After done with writing, eject and then re-insert the uSD card into your computer.
Download a CM nightly build from here http://download.cyanogenmod.com/?device=encore (It is recommended to choose -87 nightly or later. If you plan to use prior version for initial install, stick with installer 1.2.1 for a different u-boot version)
Or just use your own update-cm-*-KANG-signed.zip file that is produced if you do your own builds.
The image would correctly detect unmodified CM7 builds and would make necessary adjustments to make them work on SD card.
Put the file to the SD card (there is only one partition). Don't change the name of the file.
unmount the uSD card and insert it into the nook.
Boot from this SD card. It'll boot and will update you on progress.
When it's done, it'll power off.
That's it, you now have CM7 on your SD card.
How to install market and gapps:
After you have booted into the CM7 on SD card for the first time and set up wifi access (important!)
Go to http://wiki.cyanogenmod.com/index.php?title=Latest_Version and at the end there is a table with various google apps versions. Get the one suitable for your cyanogen version (CM7 is the latest for now). The file is named gapps-....zip
shutdown your nook and take the SD card out, insert it into your computer.
Copy the gapps-... file to the SD card on the first partition (titled boot) without changing the file name.
Insert the uSD card back into the NOOK and boot into "Recovery mode" (hold nook N key and then press and hold power until the "Loading..." message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the bootloader "Loading..." message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long).
Alternatively if you do not want to fight the timing, boot normally into Android, then from desktop hold power key until a poweroff menu appears, In the poweroff menu choose "reboot", in the next menu choose "recovery" and press "OK". The nook would reboot straight into recovery.
How to update to a new build:
put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)
Boot from the SDcard in the recovery mode (see above) and the new snapshot would be installed.
The partition layout would be preserved, filesystems are NOT reformatted, so your data should be safe.
Installing other stuff:
Booting in recovery mode would install all files that are named "update-..." and end with .zip The files would then be deleted! Most of the packages should work, but I only tested a subset and not entire syntax of updater script is implemented. Certainly format and delete are not implemented.
OC Kernel installation instructions:
Starting with v1.2.1 there are no special instructions, install normally as described above.
Partition layout for the SD cards depends on size:
Less than 600M - unsupported.
up to 1G cards gets: system of ~300M and data of the rest of space. No FAT partition
2G cards (more than 1G up to 1800M) gets: 300M system, 612M data, rest is FAT sdcard
more than 2G cards gets: 460M system, 975M data, rest is FAT for sdcard.
How to update if you already installed using older version of the installer and don't want to reinstall (understandably):
Get update zip from http://crimea.edu/~green/nook/update-genimage-1.3.zip
Put the zip file as is onto the first partition of your sdcard..
reboot into recovery (triggered by the keys, the reboot into recovery does not work yet).
The new version would be installed and you are done.
You can combine this installation together with updating to .32 kernel in one step. Just put the update-cm file and the update-genimage-1.3.zip to the first partition. Make sure there is still at least 1M of space left!
Changes in 1.3
Install u-boot.bin and MLO loaders if provided.
Fixed a problem that led to overwrite of recovery kernel if a nightly was installed more than once)
(only in full image) updated u-boot to ignore BCB as that was a common source of problems. (that's why this version is not recommended for initial install with older nightlies, those don't provide a more correct u-boot for later operations. It's fine to do the update from older installer release, though)
Changes in 1.2.1
Really fixed dalingrin kernel packages installation
A bit more robust handling of install scripts
Changes in 1.2
Updated to new u-boot from B&N 1.2 update
Ability to obey BCB in eMMC (allows reboot into recovery from CM7)
Hopefully simplified the timing to trigger recovery boots from keyboard
Added support for Dalingrin's kernel update packages
The v1.1 version that is known good to work with 2.6.29 kernel releases is located at http://crimea.edu/~green/nook/generic-sdcard-v1.1.img.gz
This is very cool, thanks! My father bought a nook color after seeing mine, and after hearing what I have been able to get mine to do (thanks to the efforts of all the devs here) he has wanted to play a little more with his. Thanks to you, I have an easy way to set up the SD card and then ship it up to him. I can give him a taste without having to force him to even root his yet. Thanks again!
Very nice! Thanks.
Care to share the dates and differences between your build and say CM's? or perhaps a link to your builds progress?
I know you have done great work with BT, didn't want to get off topic, but I'm curious.
Thanks again.
12paq said:
Very nice! Thanks.
Care to share the dates and differences between your build and say CM's? or perhaps a link to your builds progress?
I know you have done great work with BT, didn't want to get off topic, but I'm curious.
Thanks again.
Click to expand...
Click to collapse
I did not work on BT (other than helping with testing), so I don't claim any credits there.
The difference between standard build and my build so far is only that my build has patched init files to boot from SD right in the zip file. (CM7 checkout as of today ~12pm), it was only created for testing, before I rolled the code that could update vanilla builds to work on SD cards.
You can use unmodified CM7 nightlies with this sdcard image now. The image itself does not contain any CM7 code, you need to copy zip file with it after writing the image to the SD card, but before attempting to boot.
Verygreen, I believe you have won the game. Congratulations!
Ah yes, I stand corrected, you created the first CM7 sd bootable for testing of BT.
Thanks again for your time on this latest project!
First off, this works very well! Thanks!
Now, after getting CM7 running on the sdcard, I plug the device into the usb port on my computer and instruct it to mount the sdcard. But, instead of the sdcard partition being mounted, the emmc partition is mounted.
Was that intentional or is it a bug?
Thanks
Thanks very easy to setup!
atomclock said:
First off, this works very well! Thanks!
Now, after getting CM7 running on the sdcard, I plug the device into the usb port on my computer and instruct it to mount the sdcard. But, instead of the sdcard partition being mounted, the emmc partition is mounted.
Was that intentional or is it a bug?
Thanks
Click to expand...
Click to collapse
New code in CM7 actually should cause both internal MMC AND sdcard to be mounted.
That is unless you used 1G sdcard, 1G sdcard does not have any mountable free space and then you'd only see emmc content as mountable.
verygreen said:
New code in CM7 actually should cause both internal MMC AND sdcard to be mounted.
That is unless you used 1G sdcard, 1G sdcard does not have any mountable free space and then you'd only see emmc content as mountable.
Click to expand...
Click to collapse
I'm using an 8Gb sdcard and I can access both the emmc and sdcard partitions through ADB but only the emmc partition is mounted.
So, I just need to try this with a different nightly build until I find one where the issue is corrected?
Well, I tried it with both cm_encore_full-25 and cm_encore_full-26 and still only the emmc partition is mounted.
atomclock said:
I'm using an 8Gb sdcard and I can access both the emmc and sdcard partitions through ADB but only the emmc partition is mounted.
So, I just need to try this with a different nightly build until I find one where the issue is corrected?
Well, I tried it with both cm_encore_full-25 and cm_encore_full-26 and still only the emmc partition is mounted.
Click to expand...
Click to collapse
As long as everything is mounted internally I don't think my changes broke anything else, so if there is a bug it's in the CM7 build itself.
I don't actually mount my nook on the computer, so I don't even know how to enable it by default come think of it.
I just know there was an ongoing work in this area to allow simultaneous mounting of multiple volumes and I heard it was already included, though I am not 100% sure about that.
To verygreen:
Well, I'm certainly doing something wrong here:
1. Using Win32DiskImager release 0.2 r23, i burnt my 2 GB with your generic.... .img image.
2. Copied your update.... .zip (on a second attempt an original cm_encore... .zip, plus gapps-GB-20110307-...zip, as installer was asking for it, at least to inflate), now I suspect your "put" is not equal to my "copy".
3. Tried to boot, enjoyed the penguin and boot scroll, but after everything was finished and prepared to "really" boot the boot was executed from my eMMC instead.
aludal said:
To verygreen:
Well, I'm certainly doing something wrong here:
1. Using Win32DiskImager release 0.2 r23, i burnt my 2 GB with your generic.... .img image.
2. Copied your update.... .zip (on a second attempt an original cm_encore... .zip, plus gapps-GB-20110307-...zip, as installer was asking for it, at least to inflate), now I suspect your "put" is not equal to my "copy".
3. Tried to boot, enjoyed the penguin and boot scroll, but after everything was finished and prepared to "really" boot the boot was executed from my eMMC instead.
Click to expand...
Click to collapse
Yes, the automatic reboot boots into eMMC for now, I am looking into it.
So just reboot again with the card in.
also, don't put gapps on the card at the first try. This combination does not boot for me into the desktop for some reason that I did not get to the root of. Possibly because it want internet connection setup that still is not if you try it on your first boot.
Thanks verygreen! This is a fantastic build! I was able to quickly and easily install this on my sd card.
Thanks again!
verygreen said:
Yes, the automatic reboot boots into eMMC for now, I am looking into it.
So just reboot again with the card in.
also, don't put gapps on the card at the first try. This combination does not boot for me into the desktop for some reason that I did not get to the root of. Possibly because it want internet connection setup that still is not if you try it on your first boot.
Click to expand...
Click to collapse
Somehow I went into non-booting phase, lol. My guess is after booting into my rooted Eclair with bookmarks-and-other-stuff-to SD I've got me an SD card not really good for "second" boot. Just have no idea what Eclair might do to that EXT4.
Anyways, repeated the experiment, now with pressing Power for >5 sec. Has booted into CyanogenMod 7 without a problem.
Can't do whatever testing: missing GAPPS very mucho! Please, Mr. verygreen, compile it into your image. In any case, I'm not really interested in swapping nightlies on this card -- by the last commits they didn't change much/significantly since n18. Just a static SD image of CM7 n26 + latest (03072011) Gapps will be a very desirable "mod" of yours. In any case you did exactly that (minus Gapps) for n17. Sure, there's a complete procedure of building SD image, but it's obviously much better followed when with a Linux box, and I don't have it.
aludal said:
Somehow I went into non-booting phase, lol. My guess is after booting into my rooted Eclair with bookmarks-and-other-stuff-to SD I've got me an SD card not really good for "second" boot. Just have no idea what Eclair might do to that EXT4.
Click to expand...
Click to collapse
Supposedly nothing. I routinely boot into eclair and then insert CM7 sdcard and it's fine.
aludal said:
Can't do whatever testing: missing GAPPS very mucho! Please, Mr. verygreen, compile it into your image. In any case, I'm not really interested in swapping nightlies on this card -- by the last commits they didn't change much/significantly since n18. Just a static SD image of CM7 n26 + latest (03072011) Gapps will be a very desirable "mod" of yours. In any case you did exactly that (minus Gapps) for n17. Sure, there's a complete procedure of building SD image, but it's obviously much better followed when with a Linux box, and I don't have it.
Click to expand...
Click to collapse
I can't distribute gapps, like I said
Well, until I figure out why recovery boot does not work what you can try to do is this:
after initial install was successful (and you setup your wireless), power off the nook, get the sd card.
Download gapps-gb-...zip and put it on the first partition.
move the uImage file to uImage.bak and uRamdisk to uRamdisk.bak.
Copy uRecImage to uImage and uRecRam to uRamdisk.
boot with the resulting image. It should say that it found the gapps archive and unpack it.
After it flushes caches and reboots, power off, put the sd card back into the computer
move uImage.bak to uImage and uRamdisk.bak to uRamdisk
boot off the card again, hopefully the gapps are working after that.
Please let me know if any problems arise.
verygreen said:
Supposedly nothing. I routinely boot into eclair and then insert CM7 sdcard and it's fine.
I can't distribute gapps, like I said
Well, until I figure out why recovery boot does not work what you can try to do is this:
after initial install was successful (and you setup your wireless), power off the nook, get the sd card.
Download gapps-gb-...zip and put it on the first partition.
move the uImage file to uImage.bak and uRamdisk to uRamdisk.bak.
Copy uRecImage to uImage and uRecRam to uRamdisk.
boot with the resulting image. It should say that it found the gapps archive and unpack it.
After it flushes caches and reboots, power off, put the sd card back into the computer
move uImage.bak to uImage and uRamdisk.bak to uRamdisk
boot off the card again, hopefully the gapps are working after that.
Please let me know if any problems arise.
Click to expand...
Click to collapse
I just tried following your directions for installing the gapps zip file. After renaming the uImage and the uRamdisk files the nook boots to your recovery with the penguin shows up with the follow:
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir (2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skipping format
Mounting /dev/mmcblk1p1 as /boot
Looking for the install images....
Initial Install files not found
Please download it from nook.linuxhacker.ru
and put on first partition of this SD card
the name should start with updatei-cm and end with .zip
Then the cursor just sits. No installation of the .zip file. Do I have to have the original cm zip file on the sd card with the gapp zip file? I thought it was posted that doesn't work.
Also thanks for the great work on this so far.
Absolutely Fantastic and pain free. You have done a great service.
Thanks
verygreen -
Would this work with an Android 3.0 Honeycomb Preview build, instead of a CM7 build ?
Modra76 said:
I just tried following your directions for installing the gapps zip file. After renaming the uImage and the uRamdisk files the nook boots to your recovery with the penguin shows up with the follow:
Populating /dev using udev: done
Initializing random number generator....done
modprobe: chdir (2.6.32.9): No such file or directory
Starting network...
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skipping format
Mounting /dev/mmcblk1p1 as /boot
Looking for the install images....
Initial Install files not found
Please download it from nook.linuxhacker.ru
and put on first partition of this SD card
the name should start with updatei-cm and end with .zip
Then the cursor just sits. No installation of the .zip file. Do I have to have the original cm zip file on the sd card with the gapp zip file? I thought it was posted that doesn't work.
Also thanks for the great work on this so far.
Click to expand...
Click to collapse
Seeing the same. Also tried naming the gapps file "update.zip", to no avail.
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...
My cousin and I want to get Nook Tablets 16GB to mess around with, but we don't have the time anymore to (sorry, *I* don't have the time anymore, she can't figure out technology whatsoever) to figure out if we're always doing things right via the forums at this point and stay updated.
I still want to support the community as I've utilized a lot of information (namely for my old HTC TP2) here. I was thinking about buying an N2A card for the both of us, but wanted to make sure that I can copy the files from one card to another SD card so that we can use them in our respective tablets. And I rest easier knowing that I was able to make a small contribution to the community.
Is this possible? We'd both like to access the Google Play market.
Use the link in my sig. It literally takes 5 minutes after you make the cards, and you can get screaming deals on cheap cards (you can probably find 2 2gig cards for about $10) and then you'll both have full access to the market and still have access to the stock interface if you so choose (note that you will not be able to use apps downloaded from the Play store on the stock interface if you're on firmware 1.4.3, only on an aftermarket launcher).
rebelx said:
My cousin and I want to get Nook Tablets 16GB to mess around with, but we don't have the time anymore to (sorry, *I* don't have the time anymore, she can't figure out technology whatsoever) to figure out if we're always doing things right via the forums at this point and stay updated.
I still want to support the community as I've utilized a lot of information (namely for my old HTC TP2) here. I was thinking about buying an N2A card for the both of us, but wanted to make sure that I can copy the files from one card to another SD card so that we can use them in our respective tablets. And I rest easier knowing that I was able to make a small contribution to the community.
Is this possible? We'd both like to access the Google Play market.
Click to expand...
Click to collapse
If you are really wanting to go the N2A route (I personally would not), use Win32diskimager to READ the image (for backup purposes). Safely eject card. Insert new card and WRITE image. Safely eject card. Backup done!
Or do the $20 download only and buy your cards yourself. In any case, let us know what you do!
rebelx said:
My cousin and I want to get Nook Tablets 16GB to mess around with, but we don't have the time anymore to (sorry, *I* don't have the time anymore, she can't figure out technology whatsoever) to figure out if we're always doing things right via the forums at this point and stay updated.
I still want to support the community as I've utilized a lot of information (namely for my old HTC TP2) here. I was thinking about buying an N2A card for the both of us, but wanted to make sure that I can copy the files from one card to another SD card so that we can use them in our respective tablets. And I rest easier knowing that I was able to make a small contribution to the community.
Is this possible? We'd both like to access the Google Play market.
Click to expand...
Click to collapse
You can use the method/tools posted here and here to build an SD card version of blogpost author's CM10 ROM, or the current version of some other CM10 ROM varieties such as "CM10 "Jelly Bean" 0.08.x", "CM10 PURE AOSP 4.1.2 JBV06.1-Hashcode", and "SGT7+CM10+Cherry Picks" which are posted and discussed on XDA Barnes & Noble Nook Tablet Dev. Forum.
digixmax said:
You can use the method/tools posted here and here to build an SD card version of blogpost author's CM10 ROM, or the current version of some other CM10 ROM varieties such as "CM10 "Jelly Bean" 0.08.x", "CM10 PURE AOSP 4.1.2 JBV06.1-Hashcode", and "SGT7+CM10+Cherry Picks" which are posted and discussed on XDA Barnes & Noble Nook Tablet Dev. Forum.
Click to expand...
Click to collapse
It took me a few hours of trial and error but I sat down with my 4gb sandisk card and the second link up there and am now typing on my NT running CM10 off the SD card. There are a few glitches in the guide above, but I can walk you through them if you like.
Building a CM10 SD card for NT
FWIW, here the process I follow to build a CM10 SD card for my 16GB Nook Tablet:
1. Get 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/
2. Create 4 partitions using MiniTool Partition Wizard Home Edition per the instructions at http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/: boot, system, data, and sdcard. Make sure that you 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]).
3. 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.
4. 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.
5. 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 (obtained http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/).
6. Replace updater-script in folder META-INF\com\google\android of gapps-jb-20121011-signed.zip (obtained from http://goo.im/gapps/gapps-jb-20121011-signed.zip) with the updater-script in folder CM10_Jelly_Bean\p2\gapps of SD_Boot.zip.
7. 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 (which cause the CM10 ROM and JellyBean Google Apps to be installed on the SDcard rather than on your NT itself).
You should now have a bootable SD card with 7 files on it, ready for the phase of “installing ROM and gapps” described at http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/.
A few additional points worth noting:
If your NT is like mine, you will have to plug in the powered USB cable to the NT in its power-off state -- in order for the NT to boot from the SDcard.
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.
[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.1 builds by XDA Developer Succulent which is posted at his blog http://iamafanof.wordpress.com and which I have used to build a CM10.1 (version dated 20130629) SD card for my Nook Tablet. Thanks to Succulent for this great CM10.1 build!!!
[Note that Succulent provides at his blog (http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/) pre-made images of his CM10.1 builds that can simply be burn to SDcard (using DiskImage_1_6_WinAll or Win32DiskImager) after which the SD card would be immediately ready-for-use. The process in this post is meant for those folks who would like to build the SDcard image "from scratch" – so as to avoid downloading the large-size (420+MB) pre-made images, or to have a bit more flexibility in sizing the various partitions on the card].
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]).
Download boot.zip from http://goo.im/devs/succulent/acclaim/boot.zip (or alternatively from http://www.mediafire.com/download/000wv0dmfwqpvzi/boot.zip).
Extract and copy to the boot partition of the SD card the following files from boot.zip: MLO, u-boot.bin, and flashing_boot.img. (These 3 files can also be found in the /boot partition of any of Succulent's pre-made CM10.x SD card images).
Download the pair of files cm_acclaim_10.1_[ddmonthyear]_HD_SDC.zip and gapps-jb-20130301-signed-SDC.zip from http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Copy to the boot partition of the SD card cm_acclaim_10.1_[ddmonthyear]_HD_SDC.zip and gapps-jb-20130301-signed-SDC.zip.
Extract and copy to the boot partition of the SD card the following files from cm_acclaim_10.1_[ddmonthyear]_HD_SDC.zip: boot.img and recovery.img.
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.
Select "Install zip from SD card" and install the cm_acclaim_10.1_[ddmonthyear]_HD_SDC.zip file.
Select "Install zip from SD card" and install the gapps-jb-20130301-signed-SDC.zip file.
Press and hold power button to turn off the NT.
Boot the NT from its power off by inserting a powered USB cable; the NT will boot into Cyanoboot which will load (CM10.1) boot by default, after about a couple of minutes you should see boot animation lasting for a few minutes followed by initial wifi network and google account setup process, after which your CM10.1 on SD is ready for use.
A few additional points worth noting:
The two most common symptoms of failed SD boot (on insertion of a powered USB cable) and their likely causes are:
The NT boots straight to stock -- most likely the boot partition's type and/or flags are not correctly set, or the NT cannot find the MLO in the boot partition (see comment re: the ordering in file copying above).
The NT screen stays dark for minutes then eventually boots to stock -- most likely the MLO or u-boot.bin are corrupted. I have had this happen to me a few times in the process of extracting them from archive zip files and also in ftp transfers between machines (need to use "binary" instead of "auto" mode). When in doubt, check the exact size of the files in bytes, they should be respectively 38,356 and 179,812.
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. See this thread http://forum.xda-developers.com/showthread.php?t=1005633 for extensive discussion of SD card makes/models' comparative performance for use in hosting ROM.
To update the SDcard when Succulent posts a new build, simply repeat steps 4 through 12.
Thanks for this. I have an old SD card for CM7 that I did months ages ago so this will be good.
Sent from my Barnes & Noble Nook Tablet using xda premium
Booting always requires powered USB cable connection?
digixmax said:
Boot the NT from its power off by inserting a powered USB cable...
Click to expand...
Click to collapse
After initial installation and setup, is the powered USB cable connection required for all subsequent boots? I won't bother if booting always requires tethering to a PC.
b3rt0h said:
After initial installation and setup, is the powered USB cable connection required for all subsequent boots? I won't bother if booting always requires tethering to a PC.
Click to expand...
Click to collapse
It doesn't ... I was confused by this also. I went ahead and did the SD card and now I can boot to CM7 or CM10. I'm really liking CM10, works great !
You're one of the lucky ones to have an NT which can boot off SD un-tethered.
digixmax said:
You're one of the lucky ones to have an NT which can boot off SD un-tethered.
Click to expand...
Click to collapse
It's definitely something to do with more than the device itself. I formatted a Samsung 8gb class 6 and it wouldn't boot without being tethered. I then formatted a SanDisk 16gb class 10, same device, and it boots fine without usb tether.
Sent from my Nexus 10 using Tapatalk HD
Neither of the two Tablets I have had need the cable to boot.On those occasions when I have had problems booting to the card (or to internal CWM) what I've done is press and hold the "n" button right after I pressed power.
asawi said:
Neither of the two Tablets I have had need the cable to boot.On those occasions when I have had problems booting to the card (or to internal CWM) what I've done is press and hold the "n" button right after I pressed power.
Click to expand...
Click to collapse
This is exactly how mine is doing. I have found that a power down is the best way to go between OS's. I really like CM10.1 so much I'm ready to bite the bullet and go with it. I think it's just as stable as my CM7 OS The guys and gals writing this stuff are GREAT :good:
ps: When I go into CM7 with the boot SD card it takes around 2 mins to boot. It is slower but it works.
Partition sizes on larger micro SDXC card.
Hope this helps others... I followed OPs procedure to install cm-10.1-20130117-acclaim-HD-SDC.zip and cm-10.1-20121212-gapps.zip. At first I had a bad experience because I used gapps-jb-20121212-signed.zip from the google website ( IE would not let me download the "cm" version.) I then used Foxfire to download the "cm" version from iamafanof and everything seems to work fine. Followed OPs directions exactly. I'm using a SanDisk Ultra 64GB sdxc card with partition sizes: BOOT (2GB) , SYSTEM (2GB), DATA1 (16 GB), SDCARD (all the rest).
success! boots without PC tether
b3rt0h said:
After initial installation and setup, is the powered USB cable connection required for all subsequent boots? I won't bother if booting always requires tethering to a PC.
Click to expand...
Click to collapse
I successfully built a working CM10.1 SD card. It boots without PC tether just fine.
Data point: Nook Tablet 16GB. SanDisk 16GB Class 6 microSDHC Card. cm-10.1-20130117-acclaim-HD-SDC.zip.
Thanks to all the developers for making this possible. And thanks to digixmax for posting the instructions.
First, thank you for the well-written instructions.
I'm trying to learn how to build an SD card that would just have CyanoBoot, CWM (as main recovery), and TWRP (as alternate recovery), and default by default into Internal eMMC Normal. I've done steps 1, 2, 3, and 6. I then grabbed flashable_TWRP_2.4.3.0.zip from http://goo.im/devs/succulent/acclaim/recovery, extracted it's recovery.img and put it in the Boot partition as altboot.img.
It boots to CyanoBoot, and I can run CWM, but when I try to select SDC ALTBOOT, it just flashes back to the CyanoBoot screen for a few moments and then I just a blank screen.
Question 1: Am I doing something incorrect in my method to get TWRP as an alternate recovery?
Question 2: How do I configure it to boot to eMMC by default? fattire has this instruction:
To Make Default Always Boot To EMMC
$ echo -n “1” > /bootdata/u-boot.device
Click to expand...
Click to collapse
Being on a Windows pc, I tried creating a file (with Notepad++) in the BOOT partition called u-boot.device, with just the number 1 in it, but it still attempts to boot from SDC.
Thanks in advance.
InUrKitchin said:
First, thank you for the well-written instructions.
I'm trying to learn how to build an SD card that would just have CyanoBoot, CWM (as main recovery), and TWRP (as alternate recovery), and default by default into Internal eMMC Normal. I've done steps 1, 2, 3, and 6. I then grabbed from http://goo.im/devs/succulent/acclaim/recovery, extracted it's recovery.img and put it in the Boot partition as altboot.img.
It boots to CyanoBoot, and I can run CWM, but when I try to select SDC ALTBOOT, it just flashes back to the CyanoBoot screen for a few moments and then I just a blank screen.
Question 1: Am I doing something incorrect in my method to get TWRP as an alternate recovery?
Click to expand...
Click to collapse
flashable_TWRP_2.4.3.0.zip is meant for flashing into /recovery on emmc; you need to use instead twrp_2.4.3.0_acclaim_recovery_sdcard.img, just rename it to altboot.img and copy the renamed file to SDcard /boot.
Question 2: How do I configure it to boot to eMMC by default? fattire has this instruction
To Make Default Always Boot To EMMC
$ echo -n “1” > /bootdata/u-boot.device
Click to expand...
Click to collapse
...
Click to expand...
Click to collapse
I believe fattire's instruction is meant only for booting and running on emmc.
Thanks, that worked. I assumed that since it didn't say "internal" or "external" that it was for either.
Sent from my Acclaim using xda app-developers app
Thanks for the well laid out guide OP. I used it to flash CM10.1. Somehow I ended up flashing CM10 to emmc but all is well . This guide was a tremendous help.
lrs421 said:
Thanks for the well laid out guide OP. I used it to flash CM10.1. Somehow I ended up flashing CM10 to emmc but all is well . This guide was a tremendous help.
Click to expand...
Click to collapse
You must have picked up the ROM and Gapps zip file versions that are built for EMMC. The versions compiled by Succulent (http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) for SD have filenames ending with SDC.zip suffix.
digixmax said:
You must have picked up the ROM and Gapps zip file versions that are built for EMMC. The versions compiled by Succulent (http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) for SD have filenames ending with SDC.zip suffix.
Click to expand...
Click to collapse
Yup. That's exactly what I did. I flashed the SDC zips first then flashed CM10 and matching gapps.
Sent from my Barnes & Noble Nook Tablet using xda premium
Hi, I've followed the instructions in the OP but my NT stays blank when I plug in the USB cable and then boots to stock. The only thing I've changed is the partitions (0.5GB/0.5GB/8GB/remainder) on a 32GB micro SD card. It has worked before so I don't think my card is the problem. Does anyone have any advice?
SDragon64 said:
Hi, I've followed the instructions in the OP but my NT stays blank when I plug in the USB cable and then boots to stock. The only thing I've changed is the partitions (0.5GB/0.5GB/8GB/remainder) on a 32GB micro SD card. It has worked before so I don't think my card is the problem. Does anyone have any advice?
Click to expand...
Click to collapse
See note under "The two most common symptoms of failed SD boot" in OP.
If you have re-sized the partitions of a previously working CM10 SD image, I'd suggest checking to make sure the boot partition is still of the correct type 0x0C FAT32 LBA and with Active flag set. In my experience, the partition re-sizing operation occasionally messed up the partition table causing the first partition to become not bootable (even when it was not the partition that got re-sized).
I've checked the two most common problems in the OP and verified the sizes of both the MLO and u-bin files and I've ensured that I've copied the necessary files in the order required by the OP. I've also set the boot partition to active and the ID to 0x0C FAT32 LBA but the NT stays blank when I plug in the USB cable.
FWIW I'm using cm_acclaim_10.1.1-RC0_07JUL2013_HD_SDC.zip.
I am new at rooting, this is the first device I have tried to root. I followed the thread for a triple boot CM7 , CM9 and CM10 (also stock OS) from Malloneem. I decided to only flash CM7 and CM10 to NT 1.4.3. Everything worked great, except during the initial setup of both CM7 and CM10 it will not recognize my WiFi. I have tried twice, after first time I wiped NT and reformatted the sd card and started from scratch. same result both times.
I read through the replies and noticed that someone else had the same problem. the response said to wipe the cache and it should fix the dalvik. I wiped both the cache then tried and then wiped the dalvik and had the same results. With the CM10 it says "turning on wifi" and stays there.
I am a new member to xda so I cannot post a reply to the original thread.
Any help would be much appreciated.
If I cannot get this to work is there another method where you can use CM10 and stock OS? (something that is extreamly easy to follow)
Bears85 said:
I am new at rooting, this is the first device I have tried to root. I followed the thread for a triple boot CM7 , CM9 and CM10 (also stock OS) from Malloneem. I decided to only flash CM7 and CM10 to NT 1.4.3. Everything worked great, except during the initial setup of both CM7 and CM10 it will not recognize my WiFi. I have tried twice, after first time I wiped NT and reformatted the sd card and started from scratch. same result both times.
I read through the replies and noticed that someone else had the same problem. the response said to wipe the cache and it should fix the dalvik. I wiped both the cache then tried and then wiped the dalvik and had the same results. With the CM10 it says "turning on wifi" and stays there.
I am a new member to xda so I cannot post a reply to the original thread.
Any help would be much appreciated.
If I cannot get this to work is there another method where you can use CM10 and stock OS? (something that is extreamly easy to follow)
Click to expand...
Click to collapse
You can use this:
http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/
Write the image file to an SD card and you'll be good to go. You can use a repartitioning software to expand the partitions on your SD if you want. Use the instructions on the link I provided.
The SD card image will contain CM10.1 4.1.2. If you want to use a different ROM you can download the SDC version of any ROM ( has to be SDC!), place the zip on your SD card or internal storage. Boot into SDC recovery and installed the zip file. You'll need the GAPPS zip also (which has to be SDC also.)
Thank you for the help. My appologies for the redundant question but when I flash this ROM I will be able to bounce between CM10 and the stock B& N OS correct?
Bears85 said:
Thank you for the help. My appologies for the redundant question but when I flash this ROM I will be able to bounce between CM10 and the stock B& N OS correct?
Click to expand...
Click to collapse
Yes. Because CM 10 will be on your SD card. Stock will be on your internal. If your internal partitions or anything is messed up ( maybe the reason you can't boot stock) you can tell from CM.
datallboy said:
Yes. Because CM 10 will be on your SD card. Stock will be on your internal. If your internal partitions or anything is messed up ( maybe the reason you can't boot stock) you can tell from CM.
Click to expand...
Click to collapse
Thank you again. I have read throught the instructions on the link you provided and I am a little confused on the partitioning part. As I mentioned before this is my first time rooting anything. The instructions on the triple boot regarding the partitioning of the sdc were clear giving sizes for the newly created partitions etc., I didn't see that on this link (unless I missed it). Could you explain it so a newbie can understand it?
Thanks.
Bears85 said:
Thank you again. I have read throught the instructions on the link you provided and I am a little confused on the partitioning part. As I mentioned before this is my first time rooting anything. The instructions on the triple boot regarding the partitioning of the sdc were clear giving sizes for the newly created partitions etc., I didn't see that on this link (unless I missed it). Could you explain it so a newbie can understand it?
Thanks.
Click to expand...
Click to collapse
Well is there any reason why you would like triple boot? You need a fairly good size SD card if you want three systems. I just provided the simplest way to run cm on the nook. Write the image to your SD card and it will make it boot able. If you want to triple boot then setup your SD card partitions like you had before, but you only need to install the zips as alt boots.
Again, you probably don't need triple boot. Cm10+ has everything you'll need.
datallboy said:
Well is there any reason why you would like triple boot? You need a fairly good size SD card if you want three systems. I just provided the simplest way to run cm on the nook. Write the image to your SD card and it will make it boot able. If you want to triple boot then setup your SD card partitions like you had before, but you only need to install the zips as alt boots.
Again, you probably don't need triple boot. Cm10+ has everything you'll need.
Click to expand...
Click to collapse
No, I dont need the triple boot. Being a newbie I may have misread something (probably the case) but the link you gave me directed me to partition the sd card. it was this portion that was not clear to me. I was referencing the directions for partitioning on the triple boot thread as a comparison. The site you gave me said to partition the card but gave reference as to how big to make each partition. I don't need the triple boot.
My kid uses the NT to help read (read to me, etc...) I wanted something to get more of a tablet feel while keeping the stock system as well.
Thank you again. I appreciate the help. I will look at it again.
Bears85 said:
No, I dont need the triple boot. Being a newbie I may have misread something (probably the case) but the link you gave me directed me to partition the sd card. it was this portion that was not clear to me. I was referencing the directions for partitioning on the triple boot thread as a comparison. The site you gave me said to partition the card but gave reference as to how big to make each partition. I don't need the triple boot.
My kid uses the NT to help read (read to me, etc...) I wanted something to get more of a tablet feel while keeping the stock system as well.
Thank you again. I appreciate the help. I will look at it again.
Click to expand...
Click to collapse
On the iamafanof site you can scroll down there will be an SDC image. There is a difference between the image and the zips. All you need to do is download the SDC image, write it go your SD card using an file writer ( win32 disk writer will do) and your SD card will be ready to boot. Put it in your nook and and it will boot cyanoboot and should automatically do a SDC boot. It takes a little bit for the first boot to start ( usually 2 or 3 minutes)
Once you get your nook to boot cm I can tell you how to expand your SD partitions to hold more apps.
If you still have problems with WiFi it may be a different problem ( shouldn't happen).
If you need help or need a step by step guide I can find one or make one for you.
datallboy said:
...
If you need help or need a step by step guide I can find one or make one for you.
Click to expand...
Click to collapse
Just in time, "hot off the press" (almost) step-by-step guide: http://iamafanof.wordpress.com/2013...-2-jellybean-sdcard-img-for-nook-tablet-0416/.
For a more stable ROM build, use the CM10.0 image dated 12/31 in cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img.rar posted at http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/.
datallboy said:
On the iamafanof site you can scroll down there will be an SDC image. There is a difference between the image and the zips. All you need to do is download the SDC image, write it go your SD card using an file writer ( win32 disk writer will do) and your SD card will be ready to boot. Put it in your nook and and it will boot cyanoboot and should automatically do a SDC boot. It takes a little bit for the first boot to start ( usually 2 or 3 minutes)
Once you get your nook to boot cm I can tell you how to expand your SD partitions to hold more apps.
If you still have problems with WiFi it may be a different problem ( shouldn't happen).
If you need help or need a step by step guide I can find one or make one for you.
Click to expand...
Click to collapse
Thank you for your help. I worked and was simple. If you could explain the partitioning that would be great. If not, its working just the way I want it.
Thank you again!!
Bears85 said:
Thank you for your help. I worked and was simple. If you could explain the partitioning that would be great. If not, its working just the way I want it.
Thank you again!!
Click to expand...
Click to collapse
You have 4 partitions on your SD card: boot, system, data, sdcard. Your boot partition holds the files the boot CM. This is where recovery, mlo, uboot, etc is. System holds files essential for the ROM to work.
The only two you need to worry about are data and SD. Your data partitions holds apps. That is when you download an app the files in the apk file are put there. This would be like your internal storage for any phone or tablet. SD card is like an external SD card for your phone or tablet. Its where extra data files, photos, music etc go.
Depending on what size of SD card you have determines how big you can expand your data or SD partition.
Using a partitioning software ( like GParted) you can change the partitions and expand them to the side you want. I have a 16 GB SD card. So I expanded my data partition to 4 GB, and the rest went to SD card. Its okay to delete data or SD partition to expand it, but don't delete boot or system because you'll have to reformat the card and write the image file to the card again ( and ain't nobody got time for that.)
datallboy said:
You have 4 partitions on your SD card: boot, system, data, sdcard. Your boot partition holds the files the boot CM. This is where recovery, mlo, uboot, etc is. System holds files essential for the ROM to work.
The only two you need to worry about are data and SD. Your data partitions holds apps. That is when you download an app the files in the apk file are put there. This would be like your internal storage for any phone or tablet. SD card is like an external SD card for your phone or tablet. Its where extra data files, photos, music etc go.
Depending on what size of SD card you have determines how big you can expand your data or SD partition.
Using a partitioning software ( like GParted) you can change the partitions and expand them to the side you want. I have a 16 GB SD card. So I expanded my data partition to 4 GB, and the rest went to SD card. Its okay to delete data or SD partition to expand it, but don't delete boot or system because you'll have to reformat the card and write the image file to the card again ( and ain't nobody got time for that.)
Click to expand...
Click to collapse
This worked great!! thanks for all your help!!