[ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards.

Search This thread
By:
Advanced…
DizzyDen

DizzyDen

Senior Member
Feb 7, 2011
1,301
567
vratner said:
My apologies in advance if this question has been asked before, but I can't figure out how to do a search within this topic. In any case, I've been running autonooter for a while now, and have been generally happy with it. Recently, I found out that I can put Netflix on my NC, and of course dove right in. Turned out that I need a different version of Android, so I figured I can kill 2 birds with one stone, and will try CM7. I did (created a bootable SD card, and ran it off of it), and was able to successfully install, and watch Netflix on my NC. No problems there. In fact, it's frigging awesome!!! However, in the process my 4GB SD card became a 150MB (or something like that) card. I wanted to install several other apps on CM7 that require cache to be put in Android\data folder on SD card, but can't put more than a 100MB in there. I thought that this procedure automatically partitions the SD card, and leaves space for data, etc... Or am I just misunderstanding something here? Could someone please explain? Any help is greatly appreciated... Oh, and I want to leave the current setup, i.e. I want to leave autonooter, and run CM7 off of SD card for now, since I don't want to loose any BN features, just want to have more than Netflix when I'm running CM7. Thank you...
Click to expand...
Click to collapse

To do what you want... write the original img to SD... prior to booting up in the NC.... use partition manager to resize the only partition on it at that point... something less than 2GB (bigger than 2GB and NC won't boot off it)

Then do the rest of the process... It will create partition 2,3 and 4... leaving "boot" (partition 1) the bigger size.
 
J

JohnnyDanger

Senior Member
Dec 17, 2010
336
11
henhowc said:
Did you make sure that you flashed the ext4 version?
Click to expand...
Click to collapse

So I cant find the ext4 version. Ive been looking and dont see that. Where do I get it?

And I need to claify, is there a stable cm7 release that says ext4 of it or just the kernel. I have the kernel that says ext4 in the title.
 
Last edited:
D

Deleted member 3767071

Guest
Sorry I meant the kernel. Did you flash the ext4 version of the oc kernel?

Sent from my HTC Vision using Tapatalk
 
D

Deleted member 3767071

Guest
JohnnyDanger said:
Yeah, I did flash the ext4 kernel. I just copy the uimage file to the root directory on the card, put it back in and turn on the nook, right?

Sent from my MB860
Click to expand...
Click to collapse

That method from the OP never worked for me. I always flash the kernel using the same method as when updating the cm7 build. Copy the update.zip kernel file into the boot partition and go to recovery mode using power + n button.

Sent from my NC using Tapatalk
 
P

pryonix

Senior Member
Apr 24, 2011
65
9
Mandaluyong
www.flickr.com
okay this is driving me crazy... :confused:

i installed the latest nightly (87 i think) and the 5/23 OC kernel of dalgrin without any problems.

however, i want to be able to install clockwork recovery (the one that lets you backup, restore, wipe cache, dalvik cache, etc etc) but i cannot figure out how.

also, is this installer compatible with either jammer's multiboot menu or the multiboot from this thread? (http://xdaforums.com/showthread.php?t=947698)

thanks
 
J

JohnnyDanger

Senior Member
Dec 17, 2010
336
11
henhowc said:
That method from the OP never worked for me. I always flash the kernel using the same method as when updating the cm7 build. Copy the update.zip kernel file into the boot partition and go to recovery mode using power + n button.

Sent from my NC using Tapatalk
Click to expand...
Click to collapse

That worked. Thanks a bunch. I appreciate your help.

Sent from my MB860
 
cfrock

cfrock

Senior Member
Feb 13, 2008
296
29
pryonix said:
okay this is driving me crazy... :confused:

i installed the latest nightly (87 i think) and the 5/23 OC kernel of dalgrin without any problems.

however, i want to be able to install clockwork recovery (the one that lets you backup, restore, wipe cache, dalvik cache, etc etc) but i cannot figure out how.

also, is this installer compatible with either jammer's multiboot menu or the multiboot from this thread? (http://xdaforums.com/showthread.php?t=947698)

thanks
Click to expand...
Click to collapse

Me either. Posted a question on how to a few days ago on this thread but never got a response. I understand the process as I've flashed, wiped, nandroid countless times on my evo and a few others. However, no dice here.
 
D

Deleted member 3767071

Guest
cfrock said:
Me either. Posted a question on how to a few days ago on this thread but never got a response. I understand the process as I've flashed, wiped, nandroid countless times on my evo and a few others. However, no dice here.
Click to expand...
Click to collapse

I don't use it so don't quote me on this but I think it comes preinstalled under your apps. Check out the app labeled rom manager.

Sent from my Nook Color
 
V

verygreen

Senior Member
Feb 13, 2011
1,305
2,637
TN
linuxhacker.ru
henhowc said:
Hey very green. Just saw the above regarding emmc install. Is the above something that can be implemented into the SD card install or is it emmc only? That loading text is kind of an eyesore. Especially that background color that doesnt blend in and sticks out like a sore thumb.

Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse

The v1.3 (hopefully tomorrow, still some testing left to do) will introduce the ability to pick u-boot from the new nightlies.
 
V

verygreen

Senior Member
Feb 13, 2011
1,305
2,637
TN
linuxhacker.ru
pryonix said:
okay this is driving me crazy... :confused:

i installed the latest nightly (87 i think) and the 5/23 OC kernel of dalgrin without any problems.

however, i want to be able to install clockwork recovery (the one that lets you backup, restore, wipe cache, dalvik cache, etc etc) but i cannot figure out how.

also, is this installer compatible with either jammer's multiboot menu or the multiboot from this thread? (http://xdaforums.com/showthread.php?t=947698)

thanks
Click to expand...
Click to collapse
the CWM is not compatible with the installer as they both kind of compete for the same "Recovery" mechanism to be called.
The altimage in practice could be compatible, but some of the two needs to be changed to go into alt image instead of the rec image.
The new nightly (after -87) will have a nice multiboot capable u-boot with menu that you'll really like, just wait for it.
 
  • Like
Reactions: poofyhairguy
C

cannondale0815

Senior Member
Apr 21, 2009
603
222
I tried the last two OC kernels (052311 and 051311), and both break WiFi. I didn't try any older kernels.

Thanks for all the hard work -- I just got my NC and tried various different ways to boot from the SD card, and your approach is by far the easiest.

Any way this could be done for Phiremod as well?

Thanks!
-J
 
D

Deleted member 3767071

Guest
cannondale0815 said:
I tried the last two OC kernels (052311 and 051311), and both break WiFi. I didn't try any older kernels.

Thanks for all the hard work -- I just got my NC and tried various different ways to boot from the SD card, and your approach is by far the easiest.

Any way this could be done for Phiremod as well?

Thanks!
-J
Click to expand...
Click to collapse

I think phiremod is slightly larger in size so you'd need a larger boot partition. You should be able to resize the boot partition and flash phiremod the same exact way though?

Sent from my Nook Color
 
D

danvee

Senior Member
Jan 3, 2009
900
195
Soggy New Jersey
cannondale0815 said:
I tried the last two OC kernels (052311 and 051311), and both break WiFi. I didn't try any older kernels.

Thanks for all the hard work -- I just got my NC and tried various different ways to boot from the SD card, and your approach is by far the easiest.
-J
Click to expand...
Click to collapse

Agreed! All of VG's and Dahingrin's work is greatly appreciated...

On the WiFi front, though, I've run both kernels with the last 6 nightllies and have no real issues other than a slow wakeup of the WiFi radio (about 30 seconds) after the NC has been asleep.
I can't complain about that all.:D
 
V

verygreen

Senior Member
Feb 13, 2011
1,305
2,637
TN
linuxhacker.ru
Ok, v1.3 update is there, first post updated.

Also a bit of an update on the new nicer u-boot.
Nightly -87 and a few after it will just have u-boot with nicer logo.
The super-nice one with menu and alt-boot is being held up while there are some investigations into the nature of premature poweroff problem.
So contrary to what I thought it's going to appear in nightlies somewhat later.
 
  • Like
Reactions: don_ernesto
D

Deleted member 3767071

Guest
verygreen said:
Ok, v1.3 update is there, first post updated.

Also a bit of an update on the new nicer u-boot.
Nightly -87 and a few after it will just have u-boot with nicer logo.
The super-nice one with menu and alt-boot is being held up while there are some investigations into the nature of premature poweroff problem.
So contrary to what I thought it's going to appear in nightlies somewhat later.
Click to expand...
Click to collapse

Performed an upgrade to v1.3 but the same "Loading..." text is there at startup. Did I mis-interpret the changelog or do I have to start from scratch to get the updated logo?
 
V

verygreen

Senior Member
Feb 13, 2011
1,305
2,637
TN
linuxhacker.ru
henhowc said:
Performed an upgrade to v1.3 but the same "Loading..." text is there at startup. Did I mis-interpret the changelog or do I have to start from scratch to get the updated logo?
Click to expand...
Click to collapse

After you update to 1.3 it still retains the old u-boot.
Now you need to install a fresh nightly (like -87, even if you already had it installed) and the new install script would pick up the updated MLO and u-boot.
 
  • Like
Reactions: Deleted member 3767071
D

Deleted member 3767071

Guest
verygreen said:
After you update to 1.3 it still retains the old u-boot.
Now you need to install a fresh nightly (like -87, even if you already had it installed) and the new install script would pick up the updated MLO and u-boot.
Click to expand...
Click to collapse

Ugly loading screen begone. Worked like a charm. Thanks again!
 
P

prehistorical

Senior Member
Mar 11, 2011
110
6
verygreen said:
Current version: 1.3
[...]
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://nook.handhelds.ru/sdimage/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)
Click to expand...
Click to collapse

Had no issues updating via recovery from fresh 1.2 with 7.0.2 stable, to 1.2.1 with update-cm-7.1.0-RC0-encore-2.6.32-beta3.1. But upgrading via recovery to this latest 1.3 with cm_encore_full-87.zip ended up with a recovery bootloop; pulling SD card and booting in emmc results in Orange recovery. :confused:
 
You must log in or register to reply here.

Similar threads

D
  • Locked
[Kernel][Stock1.3][Already included in CM7] Dalingrin's OC kernel [09/01/11]
Replies
4K
Views
1M
Divine_Madcat
Divine_Madcat
D
[DEV] CM7 Developers Thread
Replies
3K
Views
777K
newellj79
newellj79
D
[USER] CM7 General Discussion thread
Replies
6K
Views
1M
gsutton
gsutton
D
Android 3.0 Honeycomb Preview Image v04 - 2/7/2011
Replies
2K
Views
1M
fattire
fattire
D
[DEV] CM11 Work-In-Progress
Replies
4K
Views
2M
owim
owim

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 165
    V
    verygreen
    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://xdaforums.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
    View
    20
    leapinlar
    leapinlar
    I thought I would share something that I finally figured out. I have been trying to find a way to mount the sd card boot partition without removing the card or booting to emmc. I wanted to do this so that I could download the nightly on the nook and put it directly in the boot partition. I figured out a way and it works great.

    Use a root file manager to create a new folder in /data. I called mine sdboot. Then create a blank text file. I named mine 19mountsdboot (with no .txt on the end!). Then I put the following text in it and saved it:

    #!/system/bin/sh
    # mount SD boot partition
    busybox mount -t vfat /dev/block/mmcblk1p1 /data/sdboot;

    Copy that new file to the /etc/init.d folder using your root file manager. Change the permissions to match the other files there. Now reboot the nook.

    When finished booting, you should be able to use your root file manager to go to /data/sdboot. And you should see your boot files there. (Don't mess with them.)

    Now you can copy the nightly zip there. Then reboot to the verygreen recovery and your nightly should install.

    All this without taking the card out or booting to emmc or hooking up to your PC. And it should stay that way even after flashing new nightlies to the sd.

    Edit: I attached the file here in case people were having trouble getting it right. Just unrar and put in the /etc/init.d folder and change permissions. You still need to create the folder in /data first.

    EDIT 2: I just modified the file to automatically create the directory and mount it. Just unrar and put the file in /etc/init.d folder and fix permissions. No need to create the new folder. Or better yet, I created a flashable install zip that does everything for you. You only need to flash it once (for SD installs). It will survive flashing of new SD nightlies. It can also be flashed to emmc and will mount the SD boot partition, but only if an SD install SD is in the slot. It will recognize an ordinary SD and not try to mount the SD boot partition. However, if you want to keep this on emmc, reflash after every emmc nightly flash.

    EDIT 3: Just found a problem with the install zip. Needed to have the permissions set properly. Should be all fixed now. Use the rev. 1 zip

    EDIT 4 (6-13-12): Added Rev 2 of the script and install zip. Rev 2 adds a symlink to the root directory so that 'sdboot' shows up in the root directory as well as in /data/sdboot. You can manually install the script to the /system/etc/init.d folder. Just unrar it and put it in that folder and set the permissions to execute. If you do not feel comfortable manually installing the script, put the zip in the boot partition and reboot to recovery and it will install it automatically for you. And you do not have to re-flash again after a new ROM flash. (If you previously had installed a prior version to /data/local/init.d, manually remove it before you flash the new version. If you don't you will have two copies on your system and that sometimes causes Root Explorer to lock up.) This version works great to direct download your new zip to sdboot with the new Goo Manager. Just change Goo Manager's download directory to /sdboot/ and it will put it on your boot partition.
    View
    13
    leapinlar
    leapinlar
    Updated SD image for CM9/CM10

    [Update 10-17-12] Updated installation instructions for putting CM9/CM10 on SD have been posted here. And updated image to Rev 5 to fix an issue with installing CM10.

    [Update 8-21-12] Rev 4 of image and boot files attached.

    I updated the image and boot files to better accommodate CM10 and JellyBean gapp zips and provide bigger /data partitions for larger sized SD cards. The boot partition is now 300MB so the larger CM10 and JB gapps zips will fit. And now all SD cards 8GB and larger will have a 2GB /data partition to accommodate more installed apps. Thanks DizzyDen for that suggestion.

    [Update 6-13-12] Rev 3 of image and boot files attached.

    When updating Rev 2, somehow the duplication fixes got removed. Rev 3 restores the duplication fix along with the naming fixes.

    [Update 5-09-12] Rev 2 of image and boot files attached (Replaced with newer version).

    A pending change that the CM team is implementing will adversely affect verygreen SD users. They are changing the naming standard for new nightlies. They will no longer be naming the files starting with update-. That means the existing install script will no longer recognize or install a new nightly when it is copied to the boot partition. Users must rename the file to start with update- if they want the existing install script to work.

    In order to assist users I have modified the install script to now also install nightlies if they begin with the new standard (cm-). I also added to the script the ability to recognize the new prefix (diff_) that is used by the new Goo Manager program to make an incremental update to an existing ROM. (Edit: The new script will continue to recognize and install zips beginning with update- to provide backward compatibility.) I have attached new rev2 files (replaced with newer version) that are to be used as described in the original post below.

    --------

    I have made new boot files for SD install users. They have been modified to fix the Google App duplication issue with CM9 and Google Apps. The revised script in these files will look to see if you have installed the Google versions of Calendar, Gallery, and QuickSearchBox. If you have them installed it will remove the versions that come with ICS/CM9 so that two versions of those apps will no longer show in your system.

    I have attached two files.

    The first is a revised generic image file for use if you have never set up your SD. It has the new boot files in it. It also has the larger partition so that the CM9 nightlies will fit. Just follow the instructions in the first post of this thread to learn how to install it.

    The second file is the revised boot files themselves. This is for use if you have already set up your SD and you just want the new scripts to fix the duplication issue. To install these files, just go to your boot partition and rename two files, uRecImg and uRecRam. Just add .bak to each file. The attached file is a rar containing the new files. Just unrar and copy the two files to the boot partition to replace the files you renamed earlier. The next time you install a nightly, the script will do its checking and remove the duplicates if necessary.

    Enjoy
    View
    7
    V
    verygreen
    I uploaded the v1.2 update and updated the first post.
    Check the "recovery boot" instructions, they are changed and I believe together with the updated u-boot binary the triggering of it should be easier (even with older u-boot binary updated sequence of events is probably more robust).

    For those who want to upgrade I provide update zip that would do the updating, no need to replace files by hand anymore.
    I tested the upgrade and it works. Also supported is simultaneous u-boot upgrade + update to .32-kernel based image from dalingrin.

    The new image with 2.6.29 kernels is untested! But it might still work, i guess.

    Enjoy.
    View
    4
    S
    Samiam303
    Just to let everyone know, I've uploaded a fixed version of this install image that will work better with Ice Cream Sandwich builds -- it'll no longer require you to flash sneakpeek1 first, and you won't have to rename the gapps. It's available for download in the Ice Cream Sandwich Nightlies thread. Huge thanks to Verygreen for helping me get it fixed.
    View

New posts