Post Reply

[REF] Customize ANY ROM install

OP DizzyDen

2nd March 2012, 09:12 PM   |  #1  
DizzyDen's Avatar
OP Senior Member
Thanks Meter: 564
1,301 posts
Join Date:Joined: Feb 2011

The files in this archive are for use with Barnes and Noble's stock Nook Color firmware, but can be easily modified to work with any ROM.

It is important to note that if you are not using this on the stock B&N firmware you should extract the updater-script from the ROM you are customizing and append the section further down that states compatibe with any ROM before the lines to unmount the partitions.

To use this you must:
1. Extract the rar file... I recommend using extract to and not extract here.. since it does not include an additional base folder within.
2. Decide which of the included features you wish to use and remove the others (see below notes regarding files and differences to stock)
3. Add any additional modifications you wish. DO NOT delete ANYTHING from the ROM you are customizing.
4. Edit ROM's updater-script to include the extraction of /modboot and /modsys as noted further down.

NOTE: when you are done... the zip file should contain the following ADDITIONAL folders in the base:

The modifications are as follows:
\META-INF\com\google\android\updater-script has 3 modifications:
Line 1 changed to:
assert(getprop("ro.product.device") == "zoom2" || getprop("") == "zoom2" || getprop("") == "NOOKcolor" || getprop("ro.product.device") == "encore" || getprop("") == "encore") ;
This facilitates installs B&N stock via CWM and on devices already utilizing "encore" in product or device descriptions and matches parenthesis up correctly for CWM.

This change can be ommitted for any other ROM.

For any other ROM... you only need the information below.

The following can be used for ANY ROM but there are some files included that are geared at FROYO that should be removed for other bases.
Added the following to updater-script prior to unmounting system and boot:
ui_print("User Mods...");
package_extract_dir("modboot", "/boot");
package_extract_dir("modsys", "/system");
This facilitates placing modifications to boot in \modboot and mods to system in \modsys

This works fine even if modboot and/or modsys is empty or non-existant... look at the original updater-script... it has references to \recovery that does not exist.

The \modboot folder has the following files:
uAltImg	- uImage from CWM for use as alt-boot kernel
uAltRam - uRamDisk from CWM for use as alt-boot Ram Disk
u-boot.bin - fattire's CyanoBoot u-boot.bin for boot menu and to allow booting with vol buttons to alt-boot
uImage - kernel file from Dalagrin's 09/01/11 Overclock
The \modsys folder has the following files:
etc\vold.fstab - edited stock vold.fstab to mount partition 4 of SD as "SDCARD" this corresponds to verygreen's SASD structure.
etc\wifi\tiwlan_drv.ko - this is the wireless driver update from Dalagrin's 09/01/11 Overclock
The base folder of the rar contains u-boot.bin GPL along with this readme. It will not be copied to the device.

To use any or all of this you must at least append the above ADDITIONS to updater-script via a suitable text editor (NOT Windows standard notepad). These additions MUST be prior to the script unmounting the partitions.

You can remove any of the mod's you don't want by deleting the files... you can also ADD what you want by placing the files in the appropriate folder, just remember modboot goes to boot, modsys goes to system and you must include entire folder path.
Attached Files
File Type: rar nookcolor_CWM-OC-SASDmod.rar - [Click for QR Code] (7.48 MB, 314 views)
The Following 5 Users Say Thank You to DizzyDen For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes