Source code is up at https://github.com/rookie1/u-boot-nc1.2
May 15 - Thanks to verygreen, I've modified multi u-boot to solve SD booting problem. Version bumped to 0.4.
It's reported the previous version has compatibility issues with 2.6.32 kernel. I've updated multi u-boot base on B&N 1.2 source. Now it's flashable using CWM. Boot message should show "(multi)U-Boot v0.4 loading..." after flashing this. Note this zip is for flashing to EMMC. For people using this on SD card, you need to manually copy the u-boot.bin in this zip file to your SD card boot partition.
Download link - http://dl.dropbox.com/u/20480343/multi-uboot-v0.4.zip
Looks like people are requesting different boot orders. I've created this multi-boot capable u-boot for you all
Install instructions
1. If you plan to use a bootable sd card to control the boot, replace u-boot.bin on 1st partition of the sd card with my (multi)u-boot.bin. Remember to make a backup of your original u-boot.bin just in case.
2. If you do not plan to use a bootable sd card, replace the u-boot.bin on 1st partition of the eMMC. Again remember to make a backup.
How to configure boot
normal boot is booting up without pressing any key. alternate boot is booting up with Home key ('n' key) pressed. recovery boot is booting up with both Vol+ and Vol- key pressed.
1. Boot device order
Which device to boot from is controlled by a file called u-boot.order in the same partition as (multi)u-boot.bin. Only the 1st 2 bytes of this file are significant. The first byte tells (multi)u-boot.bin where to look for kernel/ramdisk in normal boot. 2nd byte tells (multi)u-boot.bin where to look for kernel/ramdisk in alternate boot.
Value '0' means sd card, value '1' means eMMC.
For example, if you do "echo 10 > u-boot.order", you are telling (multi)u-boot.bin to load kernel/ramdisk from eMMC in normal boot, and load from sd card in alternate boot.
If this file is not present, both normal and alternate boot will load from the device where u-boot.bin is.
2. Alternate boot kernel/ramdisk file name
In the same partition as (multi)u-boot.bin, you can create 2 new files, u-boot.altimg and u-boot.altram to specify the kernel image and ramdisk file name to load in alternate boot.
In normal boot, (multi)u-boot.bin loads default kernel image (uImage) and default ramdisk (uRamdisk) from the device specified by the 1st byte in u-boot.order.
If either file is not present, the default value (uImage or uRamdisk) will be used.
Example configuration
1. eMMC stock eclair, sd card froyo or hc, and you want to boot normally into eMMC, and press 'n' key to boot into sd card
- put (multi)u-boot.bin into sd card 1st partition
- create a text file named u-boot.order in you sd card 1st partition, which contains 10
2. eMMC stock eclair, sd card froyo or hc, and you want to boot normally into sd card, and press 'n' key to boot into eMMC
- put (multi)u-boot.bin into sd card 1st partition
- create a file named u-boot.order, which contains 01
3. eMMC contains dual boot eclair and froyo (see my dual-boot post), boot normally into stock, press 'n' to boot into froyo
- put (multi)u-boot.bin into eMMC 1st partition
- if you have setup dual boot using my script, create a text file named u-boot.altimg, which contains the word "uFImg" (without quotes), and another text file named u-boot.altram with content "uFRam" (without quotes).
There are other combinations possible, e.g. creating a dual boot froyo and hc sd card without touching stock eMMC, using oc kernel as normal boot and stock kernel as alternate boot, etc.
Awesome, thanks!
Thanks for this! Looking forward to giving it a go this afternoon.
Thanks, this is going to be fun. Much easier than lilo
Works great!
I was going to try my hand at this but didn't know exactly what files to modify when making u-boot.bin. Any pointers on what you modified? Thanks!
ver2go said:
Thanks, this is going to be fun. Much easier than lilo
Click to expand...
Click to collapse
Does anybody even use lilo anymore? Civilized people use grub =P
criley said:
Does anybody even use lilo anymore? Civilized people use grub =P
Click to expand...
Click to collapse
Yes, but grub2... now there is the wrench in the monkey works. Back to lilo is easier than dealing with grub2.
Awesome, thanks.
Sent from my LogicPD Zoom2 using Tapatalk
Ok, what about running NF or HC and stock Eclair on the eMMC, with Stock being the Alternate boot?
fwdixon said:
Ok, what about running NF or HC and stock Eclair on the eMMC, with Stock being the Alternate boot?
Click to expand...
Click to collapse
Sure. Just do the following (assuming you have already got dual boot set up correctly)
- rename uImage (stock kernel) to uImage.stock
- rename uRamdisk (stock ramdisk) to uRamdisk.stock
- rename uFImg (NF kernel) to uImage
- rename uFRam (NF ramdisk) to uRamdisk
- u-boot.altimg should contain "uImage.stock"
- u-boot.altram should contain "uRamdisk.stock"
Btw, my modified u-boot only reads 16 characters from u-boot.altimg and u-boot.altram. So limit your kernel image and ramdisk file name length to less than 16 chars. Otherwise unexpected things can happen.
i would love to do this, but can we get step by step retard noob instructions for windows please? i would like to boot emmc froyo default and sdcard HC with the n key held.
rookie1 said:
Sure. Just do the following (assuming you have already got dual boot set up correctly)
- rename uImage (stock kernel) to uImage.stock
- rename uRamdisk (stock ramdisk) to uRamdisk.stock
- rename uFImg (NF kernel) to uImage
- rename uFRam (NF ramdisk) to uRamdisk
- u-boot.altimg should contain "uImage.stock"
- u-boot.altram should contain "uRamdisk.stock"
Btw, my modified u-boot only reads 16 characters from u-boot.altimg and u-boot.altram. So limit your kernel image and ramdisk file name length to less than 16 chars. Otherwise unexpected things can happen.
Click to expand...
Click to collapse
Awesome! That's what I was thinking, but jsut wanted to get confirmation. Also, good to know on the character limit in the names.
DomSim said:
i would love to do this, but can we get step by step retard noob instructions for windows please? i would like to boot emmc froyo default and sdcard HC with the n key held.
Click to expand...
Click to collapse
rookie1 said:
Example configuration
1. eMMC stock eclair, sd card froyo or hc, and you want to boot normally into eMMC, and press 'n' key to boot into sd card
- put (multi)u-boot.bin into sd card 1st partition
- create a text file named u-boot.order in you sd card 1st partition, which contains 10
Click to expand...
Click to collapse
I'm assuming you already have froyo on the emmc, but the above is all you have to do.
In simple steps
1. Put your HC sdcard in your card reader on your Windows machine.
2. Make a copy of the existing u-boot.bin and save it to your hard-drive somewhere in case you don't like this.
3. Open a text editor and type "10" without the quotes and save the file as u-boot.order
4. Copy the u-boot.bin file out of the zip in the OP over to the sdcard (this will overwrite the original but we backed it up already in step 2)
5. Copy the u-boot.order file to the sdcard
6. Unmount sdcard from Windows and put it in your Nook and boot it up
Enjoy
well, that sounds way easier than i thought. i thought i had to create and move a file onto the emmc portion of the phone, not the sdcard. also, wasnt clean on editing the the order file, thought i needed to hex edit it or something. trying now!
soonereng said:
I'm assuming you already have froyo on the emmc, but the above is all you have to do.
In simple steps
1. Put your HC sdcard in your card reader on your Windows machine.
2. Make a copy of the existing u-boot.bin and save it to your hard-drive somewhere in case you don't like this.
3. Open a text editor and type "10" without the quotes and save the file as u-boot.order
4. Copy the u-boot.bin file out of the zip in the OP over to the sdcard (this will overwrite the original but we backed it up already in step 2)
5. Copy the u-boot.order file to the sdcard
6. Unmount sdcard from Windows and put it in your Nook and boot it up
Enjoy
Click to expand...
Click to collapse
worked! just one question. when booted into emmc froyo, if i mount sd card by dragging down the notifiction menu and select mount, it mounts the "boot" partition for the HC build on the sdcard. im pretty sure that if i load up files in that area for the emmc froyo to use, it will keep HC from booting right? can this be changed so both the emmc froyo build and the sdcard honeycomb build can share the same sdcard partition?
Sweet, a way for us NF users to get a recovery. Thanks for putting this together.
You can switch the partition that is loaded as sdcard by edition the file "vold.conference" in the /etc directory. Add "partition 4" in the second block, similar to what is in the first block. This will enable the emmc and the sdcard o/s yo share the same SD card files yassuming partition 4 is the SD card partition
Sent from my LogicPD Zoom2 using XDA App
Edit: that should be "vold.conf" not conference ... Darn auto-correct.
jasoraso said:
You can switch the partition that is loaded as sdcard by edition the file "vold.conference" in the /etc directory. Add "partition 4" in the second block, similar to what is in the first block. This will enable the emmc and the sdcard o/s yo share the same SD card files yassuming partition 4 is the SD card partition
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
i do not have a vold.conference in my /etc directory. at lease according to root explorer.
DomSim said:
i do not have a vold.conference in my /etc directory. at lease according to root explorer.
Click to expand...
Click to collapse
Yeah, I'm only finding a "vold.fstab" in my /etc.
I'm trying to do the exact same thing as DomSim.
Maybe the vold.conf file is only on eclair. I have eclair on emmc and hc on sd. This trick works c for eclair
Related
Edit edit edit edit: I sold my Nook Color in the summer of 2012. If there is anything you need me to edit into this top post I am happy to. Thanks!
Edit edit edit: I still own a Nook Color but I will not be actively editing this thread anymore. Here is the gist of it: You take any bootable Clockwork SD card, paste over the uRecImg and uImage files as needed for newer versions of CWM, and now you have an updated card. I was advised to warn you guys that the 3.0.x.x versions of CWM are not compatible with newer NC devices that have different partition tables. I was also asked to post the following:
eyeballer said:
Download 1gb CWM 3.2.0.1 sdcard image from here. MD5 of .zip: 1319739d33642ed860e8044c3d55aa56. (I made this based on work in this thread. credit: to cmstlist and DizzyDen, and kevank for hosting). You really only need the 1gb image ... no matter what the size of your card is. A smaller image will burn faster, and when you're done with the guide you can reformat the card anyway.
Click to expand...
Click to collapse
But I do want to point I disagree with the statement that "you really only need the 1GB image"... I use my CWM SD to make nandroid backups before major changes, so it makes a difference to have the full size of your SD available.
---- end of edit. Happy hacking!
I just wanted to report that I was able to take files from two different threads and use them to create a bootable SD card with ClockworkMod 3.0.1.0 and now 3.0.2.8. The advantage of this version is that it works for both ext3 and ext4 ROMs. I successfully flashed an ext4 version of Honeycomb and then restored back to my nandroid backup of auto-nooted Eclair.
EDIT: Direct links to 3.0.2.8 bootable images here: http://mrm3.net/nook-color-updated-clockwork-recovery-bootable-sd/
Source of those files is this post: http://forum.xda-developers.com/showpost.php?p=13283643&postcount=34
Credit to DizzyDen.
Image writer here: https://launchpad.net/win32-image-writer
NEW INSTRUCTIONS
1) Obtain the image for your SD card size here, containing any version of CWM:
(This link is now broken.)
http://legacyschool.us.to/nookdev/clockwork/0.7/
(source: http://forum.xda-developers.com/showthread.php?t=922870)
2) Obtain the correct uImage and uRamdisk files for CWM 3.0.2.8. The way I did this was to flash CWM 3.0.2.8 from ROM Manager and then mount my /boot partition to copy out the files uRecImg and uRecRam. But for the benefit of those of you here who can't flash CWM successfully, I've attached the files here.
3) Burn the SD card as instructed. Leave the SD mounted in your computer afterwards.
4) Rename your copy of the new uRecImg to uImage and replace the uImage file on the SD.
Rename your copy of the new uRecRam to uRamdisk and replace the uRamdisk file on SD.
5) Eject the SD from your computer, pop it into your Nook Color, reboot and verify that you indeed manage to boot into the new desired version of ClockworkMod. Upon completion I had a bootable 3.0.2.8 SD card.
OLD INSTRUCTIONS BELOW
I haven't seen anyone here post an SD image for 3.0.1.0, so here is what I did instead:
1) Obtain the image for your SD card size here, containing CWM 3.0.0.5 at time of writing:
http://legacyschool.us.to/nookdev/clockwork/0.7/
(source: http://forum.xda-developers.com/showthread.php?t=922870)
2) Also get the newer version of ClockwordMod in .zip format:
3.0.1.0 is here: http://muffinworld.net/android/nookcolor/clockwork/cwmr_3.0.1.0.zip
(source: http://forum.xda-developers.com/showthread.php?t=971197)
3) Burn the SD card as instructed. Leave the SD mounted in your computer afterwards.
4) Unzip the files uRecImg and uRecRam from the newer CWR zip.
Rename uRecImg to uImage and replace the uImage file on the SD.
Rename uRecRam to uRamdisk and replace the uRamdisk file on SD.
5) Eject the SD from your computer, pop it into your Nook Color, reboot and verify that you indeed manage to boot into the new desired version of ClockworkMod.
Enjoy!
EDIT: Post #4 below contains IMG files created using this method for ClockworkMod 3.0.1.0. Thanks to DizzyDen.
http://forum.xda-developers.com/showpost.php?p=11999569&postcount=4
Thanks, I will be trying this out later today probably.
Nice post and great info. I just did this as a test run last night myself and was going to make a thread explaining what to do but you have now saved me the time in doing that.
I can say this works great as I have flashed and restored backups between ext4 and ext3 builds. I went from Nook OS, to HC, back to Nook, over to CM&, back to Nook all wiht no issues.
Updated SD IMG files
NOTE: 3.0.2.8 images in POST 34 of this thread... ALL credit still goes to OP
All credit goes to OP... all I did is updated the original SD *.0.7.img files with OP's results....
I renamed them to *.3.0.1.0.img to distinguish which version of CWR image and ramdisk files are being utilized. I also compressed to rar to distinguish these are not CWR flashable zip files.
NOTE: 4 gig fixed 03/18/11... My apologies for my initial mistake... thank you for those who caught it and reported.
M5 Checksums:
RAR's:
Code:
128mb_clockwork-3.0.1.0.rar
049C0B4437473100FB294968CAC08CF9
1gb_clockwork-3.0.1.0.rar
D95324AE63DDAEC713B30A69CEE61C9B
2gb_clockwork-3.0.1.0.rar
4E8F088D17246750DA628133F177F91F
4gb_clockwork-3.0.1.0.rar
EA6C8FA2B7932113E59EF61448425B0C
8gb_clockwork-3.0.1.0.rar
5C80CBCFC09E47A50D9EC04EFA70DE9C
GZ's (only available on RapidShare due to file type):
Code:
128mb_clockwork-3.0.1.0.img.gz
C2531B8AF258C06BD794A3EC08ABC2D1
1gb_clockwork-3.0.1.0.img.gz
26ABB66BFEEA76C8AD0ABBA97EDC964E
2gb_clockwork-3.0.1.0.img.gz
3D8F05F0F6FF39271F5F82DBCC4403A3
4gb_clockwork-3.0.1.0.img.gz
8A13A55E045F23F3D3BE5354EDEC26B5
8gb_clockwork-3.0.1.0.img.gz
48D8CB4B93E57FC121C8082CB23FD98F
IMG's:
Code:
128mb_clockwork-3.0.1.0.img
297793ED7B371BB116F4B27AF095E18D
1gb_clockwork-3.0.1.0.img
D104AE6297662664C339D08BDFAED858
2gb_clockwork-3.0.1.0.img
B2EB4B7C24C1D8A1414BE9FE6BF697F4
4gb_clockwork-3.0.1.0.img
147A648D285815C7C175E42612B5E4A2
8gb_clockwork-3.0.1.0.img
8AD83B4ED74541AAB75103843E990088
RapidShare mirrors (folder includes .gz files):
RapidShare mirrors (folder includes .gz files)
NOTE: there's also a 16 GB version on RS... just can't upload that large file here.
Thank you!
You are very welcome... and thank you!
I suppose I could compress the img's to gz for those with linux exclusively... if anyone would like this... just let me know.
Awesome many thanks for the effort Dizzy. Will make life alot easier for many folks I'm sure.
If anyone has or is willing to flash the most current CWR ( 3.0.1.3) to there device and then pull the uRecImg and uRecRam files and post them would be great. Then we can update our current 3.0.1.0 sdcards to 3.0.1.3.
Ok i tried but it still saying 3.0.0.5 on the screen, is that just wrong and it truly is 3.0.1.0
hellomynameis said:
Ok i tried but it still saying 3.0.0.5 on the screen, is that just wrong and it truly is 3.0.1.0
Click to expand...
Click to collapse
I'm assuming you are seeing 3.0.0.5 as the version on the internal mem and not a bootbale sdcard. If it is from the internal mem then yes you are a bit behind on the most current version of CWR. and should get updated to the most current version. To get more current you will need to check this thread out first to get to 3.0.1.0. from there you should be able to use Rom Manager to update to 3.0.1.3.
http://forum.xda-developers.com/showthread.php?t=971197
I tried updating... but ROM Manager says 3.0.1.0 is still the newest.
Has anyone modified a Recover Ramdisk (uRecRam) that maps the FS to allow CWR to flash/install files to the SDcard vs. EMMC partitions? If so would you be willing to share as I suspect a good number of folks would be very grateful as would simplifiy greatly installing things like Gapps to SDcard installs...
hellomynameis said:
Ok i tried but it still saying 3.0.0.5 on the screen, is that just wrong and it truly is 3.0.1.0
Click to expand...
Click to collapse
Getting the same thing... and I haven't installed CWM to the internal memory. At least not that I know of
I'm going to try burning the image again.
hellomynameis said:
Ok i tried but it still saying 3.0.0.5 on the screen, is that just wrong and it truly is 3.0.1.0
Click to expand...
Click to collapse
Curious did you happen to use the 4Gb image file. If so you would be correct I just saw a post from someone else saying they used the 4Gb file and it installs 3.0.0.5 still
@Dizzy if you happen to see this any chance you can look into and correct the 4Gb file you posted. It is still installing 3.0.0.5 supposedly. Here is a link to the person who ran into the prob
http://forum.xda-developers.com/showthread.php?p=12192636#post12192636
4 gig files fixed....
4 gig files still having old uimage files reported and fixed... my apologies for any inconvenience....
Post 4 fixed with new files and MD5's
cmstlist said:
http://muffinworld.net/android/nookcolor/clockwork/cwmr_3.0.1.0.zip
Click to expand...
Click to collapse
This URL does not work. Anyone able to provide an alternate?
swapdotavi said:
This URL does not work. Anyone able to provide an alternate?
Click to expand...
Click to collapse
You'd get better response asking in the muffin thread... this thread is about updating your CWR SD's... with images pre-made in post 4.
swapdotavi said:
This URL does not work. Anyone able to provide an alternate?
Click to expand...
Click to collapse
Swapped webhost....was down for about 24 hours. I wanted everyone to know the files are fine now.
Sorry fellas, I'm a little behind the power curve here. So why would i need a bootable CWM-SD? Would it be useful for flashing and restoring a backup if your NC accidentally got zapped with the 1.2 update, then you could pop in your CWM-SD and restore back to 1.1? I'm just running Auto-nooter stock rom right now, will it work with stock? I turned off Wi-Fi for now, but would like to turn it back on. Would be nice if I could revert back to 1.1 if I got the OTA accidentally.
Can we get the files to make a bootable SD card with CWR 3.0.2.8?
Thanks,
Andy
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...
Hi again everyone,
I've noticed that some people have been inquiring about getting their Stock Nook Color rom onto an SDcard. And due to legal issues with distributing the B&N rom. It would not be wise to just "dd" the stock partitions to an .img file and post it for everyone to share. On top of the fact that each Nook has the /rom and /factory partition which stores each devices unique id's. So to work around that, here's an image file with a flashable .zip that will move your stock partitions to your SDcard via a modded CWM that is preinstalled with the .img file. Hope I'm not confusing anyone?!
**DISCLAIMERS: Please read and accept all that is noted below in red**
1-I do not take responsibility for whatever happens to your Nook Color. You are doing this at your own risk. If you are unsure about what's going on here. Then I'd suggest leave your Nook how it is!
2-I tried not to mess with the /rom partition because it stores very important unique device identifiers in that partition. But no matter what I did, it kept stalling on boot. However, I did leave the /factory partition alone. Which stores a rombackup.zip of your device id's. So I would suggest backing up these two very important partitions and store it somewhere safe!
3-On the above note. This is very important. Do not try and use this SDcard on any other nook than your own. I'm not sure what will happen. But I really don't want to find out.
4-Never, ever have the same Nook Stock rom running at the same time for any reason. This will intefere with the B&N servers and send a signal to De-authorize and wipe your nook. On top of that. It might just brick your nook from ever registering again!
5-This is mounting your internal partitions to copy over to the SDcard partitions. So again, if you are unsure or hesitant or not brave enough to touch your EMMC partitions. Please drop your SDcard that you were about to burn and walk away, slowly...
6-I assume you accept all the above. If so, please continue reading for the fun stuff!
Credits:
Rookie1 (for the initial eclair2dualboot script)
Nemith (for CWM Recovery used)
NOOK Stock to SD v0.1
What we have here is an .img file with partitions already created and ready for you to transfer your Stock Nook rom over to your SDcard. I would like to thank rookie1 for his initial script for moving Stock Eclair to Dualboot. I just took that and modified the script to work with the SDcard install. The script will still make use of your internal 5gb emmc Media partition as well. This will also modify all the necessary files on the fly to work with your Nook SDcard Rom (eg. uRamdisk, vold.fstab...etc).
I made the .img file around 7.4 gb so that people won't have issues burning it to an 8gb card. If you want to get use of the full 8gb or 16gb card. Use EASUS partition tool to extend the /sdcard (8th) partition.
FYI: I still for some reason or another can't grasp the CWM Recovery progress bar! Totally lost when it comes to inserting the correct values in the edify script. It extends past where it should end. I'm sure it's something very simple and maybe my mind is just too tired or better yet lazy to figure it out. So if anyone can advise me on the issue, please do.
Instructions and Pre-requisites:
**Backup your NOOK!!!!!**
1-You need a Nook Color with stock rom on EMMC already registered (root it now if you wish)
2-An 8gb uSDcard or larger
2-Download Nook Stock 2 SD v0.1
3-Unzip and follow directions from Nookdevs.com to burn the .img file to your SDcard
4-Power off Nook
5-Place the SDcard that you just burned stock2sd_v0.1.img to in your Nook and power on
6-It will boot to CWM Recovery. Now choose to "install zip from sdcard"
7-Now select "choose zip from sdcard"
8-Choose "stock2sd_v0.1.zip" and confirm "yes"
9-Sit back and wait... be patient! This will take a while.
10-When finished it will say "Can you believe it! It's stock Nook on your SDcard!"
11-Leave SDcard in Nook and go back to CWM main menu and choose to "reboot system now"
12-Enjoy your Stock Nook rom on your SDcard! Now go flash all the other roms to your EMMC!
Edit 5/9: I noticed that some people have issues with the .img file when uncompressed. So I've uploaded an alternative file to try if the first didn't work. The new file is a 7zip file. It offered better compression so the file size is much smaller as well. Hope this helps out the few that had issues.
Download:
stock2sd_v0.1a.zip
MD5-4aecd4f8fc4d7c40bbe392d8cb970853
4shared | Rapidshare
Update: 5/9 stock2sd_v0.1.img.7z
MD5: b72dd3cc0413b6fdadf899cfdf48b24e
4shared | Rapidshare
Click to expand...
Click to collapse
For anyone that has an alternative rom on your EMMC already. Mr_fosi wrote a nice write up on how to backup your current rom, restore to stock, copy stock to SD, and then revert back to your original setup on EMMC. Don't forget to give him a thanks for the great write up!
Mr_fosi's Guide
Hey, if I've helped in someway. Please show your appreciate with a thanks in one way or another!
Thanks,
Racks
Will try this as soon as I get a new SD card... have been wanting to be able to do this for a while, thanks!
Thanks for this!
Sent from my NookColor using XDA Premium App
Would this be the correct steps for getting rooted Stock Rom 1.2 to run from sd card if we are using Phiremod V6.2 OC 4/24 from the EMMC and want to restore it when we are done. Would sometimes boot from rooted stock sd card and other times boot from Phiremod V6.2 EMMC with a 16GB data sd card containing movies and music.
First of all thanks for making this.
1) Use Titanium Backup "Batch" option to "Run Backup all user apps + system data".
2) Have ClockworkMod 3.0.1.0 (or higher) in EMMC. Use ROM Manager v4.2.0.2 (or higher) to "Backup Current ROM". I like to append a PhV6.2 to the end of the file name. This procedure is referred to as making a Nandroid backup.
3) Mount your current sd card on a pc and copy the folder TitaniumBackup to it. Open the folder clockworkmod on the sd card and copy the Nandroid backup folder made in step 2) to the pc. This is for backup purposes. Not used in the procedure.
4) Use the procedure in thread "[UPDATE ZIP] Stock 1.2 update.zip flashable from CWM" to change your EMMC ROM back to stock. There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot). Not sure which one to use? Perfer the doesn't replace CWM, will this work with the procedure in this thread to move "Nook Stock to SDcard Image[5/3]"?
5) Use the procedure in thread "ManualNooter 4.5.2 (For Stock 1.2)" to root your nook.
6) Use the procedure in this thread "[ADV][DEV][CWM]Nook Stock to SDcard Image[5/3]" to move the rooted 1.2 to the sd card.
7) Install original sd card. Manually Boot into EMMC Recovery (ClockworkMod 3.0.1.0 or higher - hold Power button + n button for 6 seconds). Restore the Nandroid backup folder made in step 2).
OP udated with download link.
Thanks,
Racks
Will buy an SD and give this a shot.
Quick confirmatory questions:
- Having read the OP, it seems as though you are not intentionally modifying the partitions or their contents on the EMMC, correct?
- I haven't looked at the script, but what you wrote here says that they are only mounted and copied, yes?
- Finally, this does not change the read/write flag on any of the partitions on the EMMC?
Thanks for the work on this, I sure hope it works when I try it!
lschroeder said:
... Stock Rom 1.2 to run from sd card if we are using Phiremod V6.2 OC 4/24 from the EMMC ... Would sometimes boot from rooted stock sd card and other times boot from Phiremod V6.2 EMMC with a 16GB data sd card containing movies and music...
.
Click to expand...
Click to collapse
Eventual goal is to replace Phiremod V6.2 EMMC with a ROM based on CM7.1.x that has sleep fixed, wifi staple, bluetooth range extended - bluetooth keyboard functioning with wifi, hardware accelerated with over clocking at 1200/1300 and a rooted Stock 1.2 for the magazine and other reader features. Guess I am asking for a lot but I have faith in you developers!
mr_fosi said:
Will buy an SD and give this a shot.
Quick confirmatory questions:
- Having read the OP, it seems as though you are not intentionally modifying the partitions or their contents on the EMMC, correct?
- I haven't looked at the script, but what you wrote here says that they are only mounted and copied, yes?
- Finally, this does not change the read/write flag on any of the partitions on the EMMC?
Thanks for the work on this, I sure hope it works when I try it!
Click to expand...
Click to collapse
1-Not modifying anything on EMMC
2-Yes mounted then copied
3-It shouldn't change any or the read/write flags on your EMMC
Thanks,
Racks
Awesome.
This looks to be worth undoing my nice CM7 install, reverting back to 1.1 (then upping to 1.2) for. I would very much like to get some of the stock functionality back and this looks like a great way to do it without having to modify my EMMC partition table.
The dual-boot option looked promising as well but I really don't want to mod the partitions on this thing, especially since I use CM7 most of the time.
lschroeder said:
Would this be the correct steps for getting rooted Stock Rom 1.2 to run from sd card if we are using Phiremod V6.2 OC 4/24 from the EMMC and want to restore it when we are done. Would sometimes boot from rooted stock sd card and other times boot from Phiremod V6.2 EMMC with a 16GB data sd card containing movies and music.
First of all thanks for making this.
1) Use Titanium Backup "Batch" option to "Run Backup all user apps + system data".
2) Have ClockworkMod 3.0.1.0 (or higher) in EMMC. Use ROM Manager v4.2.0.2 (or higher) to "Backup Current ROM". I like to append a PhV6.2 to the end of the file name. This procedure is referred to as making a Nandroid backup.
3) Mount your current sd card on a pc and copy the folder TitaniumBackup to it. Open the folder clockworkmod on the sd card and copy the Nandroid backup folder made in step 2) to the pc. This is for backup purposes. Not used in the procedure.
4) Use the procedure in thread "[UPDATE ZIP] Stock 1.2 update.zip flashable from CWM" to change your EMMC ROM back to stock. There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot). Not sure which one to use? Perfer the doesn't replace CWM, will this work with the procedure in this thread to move "Nook Stock to SDcard Image[5/3]"?
5) Use the procedure in thread "ManualNooter 4.5.2 (For Stock 1.2)" to root your nook.
6) Use the procedure in this thread "[ADV][DEV][CWM]Nook Stock to SDcard Image[5/3]" to move the rooted 1.2 to the sd card.
7) Install original sd card. Manually Boot into EMMC Recovery (ClockworkMod 3.0.1.0 or higher - hold Power button + n button for 6 seconds). Restore the Nandroid backup folder made in step 2).
Click to expand...
Click to collapse
I don't think it matters which restore to stock .zip you use. This script will basically copy what ever setup you have on your EMMC to your SDcard. Your steps are correct as I see it. Please advise if the steps you took worked or not.
Thanks,
Racks
I am getting a corrupt error when unzipping img with winrar. I have download 3 times different download places.
patgnds said:
I am getting a corrupt error when unzipping img with winrar. I have download 3 times different download places.
Click to expand...
Click to collapse
Thanks for advising. I'm checking the download now. Anyone else have the same issue?
The problem seems to be in the reported size of the original file within the zip.
In mine (downloaded from the hated Rapidshare):
- Compressed size: 120,494 kb
- Original size: 807,167,488,681,452 kb
Maybe a corrupt compression?
Same issue...corrupt, download size is 4k.
Sent from my HTC Vision using XDA Premium App
mr_fosi said:
The problem seems to be in the reported size of the original file within the zip.
In mine (downloaded from the hated Rapidshare):
- Compressed size: 120,494 kb
- Original size: 807,167,488,681,452 kb
Maybe a corrupt compression?
Click to expand...
Click to collapse
Thanks for the advise. I'll take down the link until further notice. Sorry for this everyone.
Thanks,
Racks
Edit: I've just downloaded it to my mac at work and used Stuffit Deluxe to unzip it. And it unzipped and mounted fine for me. I'll see if I can rezip this one and reupload.
The MD5 of the file I have matches the one posted in the OP, so I am fairly sure the download wasn't corrupted. It seems to be a problem with the original file uploaded.
A quick re-zip might fix the issue.
I did burn the rom and installed the zip from cwr it worked.
So you must have been able to unzip the IMG? Can you share the zip file you used and post it's MD5?
Dual boot setup.
Does this copy all partitions on the emmc or just the first boot partitions? I have dual boot setup with stock on the second boot. If I could just copy the whole setup to an sd card it would be pretty slick. Thanks for your hard work.
1CF71B239DB860A36CD70C3FB8F70FEC
partitions
boot
rom
factory
system
data
cache
sdcard
[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.