yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] rajendra82:
1. Do you envision this to be an uprooted stock 1.3 update ROM (either as primary or the only boot option) ? I just don't see the need for this to be CWM flashable. It is very easy to get there by resetting the device to stock, and then updating the device to 1.3.0 using the B&N file, and restoring dual boot as need be. If one has any older stock ROM running on primary, the B&N update will get them to 1.3 while losing root. There is no need to apply 1.2 update first.

2. Do you envision this to be for already rooted single or primary booting 1.1/1.2 users? There is once again no need to create any file for this. One can simply apply the B&N update, and then rerun manual nooter, and restore dual booting to the secondary.

3. The only users with no clear upgrade path are those who have already moved the B&N ROM to secondary. That's why I fixed up the zip file, and shared it. I am glad the original file worked for you despite the script errors. I can see other setups where it would have failed though.

I am not trying to make this more complicated than it needs to be. The Nook Color is just capable of being set up in so many ways, there isn't simply going to be a single update method that will work in all scenarios.
[Nook Color Android Development] Taosaur:
I'm envisioning it as a one step, starting-point-agnostic means of establishing a 1.3 stock install, whether for setting up a dualboot or for any other purpose. Its usefulness is made evident by the three-page thread devoted to CWM-flashable 1.2 images: http://xdaforums.com/showthread.php?t=1050520
[Nook Color Android Development] rajendra82:
Then the best bet is two step process:

1. Wipe device and restore to factory stock.

2. Download B&N 1.3 update file from website and place it on the root of SD card. Let the device recognize it, and apply it.

Once the 1.3 update gets applied, you are free to reroot, install CWM, set up dual booting, or whatever the next step may be.

It is the only method that will work in all circumstance as it involves starting from scratch regardless of setup. If want to preserve any of your current setup, no one step file will work for all circumstances. Some people have the stock firmware rooted, others do not. Some have the stock as the only internal boot, others have it as primary option of a dual booting configuration, while others have it as a secondary option. Some have stock recovery and run CWM off the sdcard when needed and want to update their recovery to the latest stock version, others want to keep the CWM recovery, and not update the recovery. There simply is no way file to cope with all these options.
[Nook Color Android Development] yelloguy:
You lost me at mount :-)

Seriously, I am trying to see if what I have is compatible with your update before I apply the update. I have a couple of useful apps on my CM7 and I have lost the password. I don't want to be stuck without CM7 or start over again. I can live without the 1.3 update though. So I want to make sure I am up to the task of finding and renaming these files if I have to.

With that said, how do I mount the /boot partition? I go into terminal emulator and give the su command. Then I tried mount /boot but that didn't work.

Thanks for your help.
[Nook Color Android Development] Taosaur:
...the only means of doing so "that will work in all circumstance" and in any way resembles a single step is flashing a stock zip via CWM. Why not use an up-to-date zip? The usefulness of such files is demonstrated by the fact that:

such files exist for past stock versions

those files are in use

files like yours are used to work around the non-existence of up-to-date stock zips

If you're so comfortable working with update files, you very likely could have produced such a file in less time than you've spent rationalizing away the clearly demonstrated need for them. Tell you what, in all likelihood I can just swap a few files from B&N's 1.3 zip into the existing CWM-flashable 1.2 zips, correct? Which files do I replace?

Anyone?

---------- Post added at 02:15 PM ---------- Previous post was at 01:58 PM ----------

I don't know for sure, but wouldn't rajendra's update create properly-named boot files alongside the old, improperly named ones? Wouldn't the multiboot built in to recent CM7 builds then look for and boot from the more recent, properly named files? I can't confirm that's how it would work, but it's what I would expect.
[Nook Color Android Development] yelloguy:
Yes they would create properly named boot files. But I suspect my nook looks for improperly named files since I updated my u-boot after the CM7 nightly update.

The fix is simple: to rename the files. But I need to know how before I take the plunge.
[Nook Color Android Development] Taosaur:
Right, but if you run a CM7 update, it would replace your uboot again. I'm not saying do it, just wondering out loud if it would work.
[Nook Color Android Development] rajendra82:
In order to rename the files, you can do the following:

1. Boot into CM7 (or any other place where you have command line root access)

2. Create a temporary directory at a location where you have read write access.

3. Type su in a terminal session to gain root access and then mount mmcblk0p1 at the temporary location you created using the command:

mount /dev/block/mmcblk0p1 <full path to the directory you created>

4. Now use Astro to go over to the directory you created and mounted mmcblk0p1 into. You should see:

u-boot.bin which is the bootloader

u-boot.bin.stock which is the backup of the old stock bootloader

uImage and uRamdisk which are your primary kernel and ramdisk

uFImg and uFRam which are your secondary kernel and ramdisk (and whose names are mismatching the CM7 bootloader protocol)

u-boot.altimg and u-boot.altram, which are text files per the old bootloader method containing names of uFImg and uFRam

5. Rename uFImg to uAltImg, uFRam to uAltRam. And edit the contents of u-boot.altimg and u-boot.altram to match the new file names.

6. Reboot as usual into primary or secondary.

Now if an CM7 update ever replaces your u-boot.bin, you will not lose dual boot, as you have it set up as uAltImg and uAltRam per the new protocol.

---------- Post added at 03:24 PM ---------- Previous post was at 03:06 PM ----------

I am sorry if you think I am rationalizing, but that was not my intention. I just wanted to point out that the files you linked to do not meet your own criteria.

Take for example the file update-nc-stock-1.2-keepcwm-signed.zip that you point to as missing in an up to date 1.3 version. That file will update a Nook Color to 1.2, but will keep CWM recovery. It however will make someone whose Nook Color 1.1 was rooted using autonooter lose root. A person that has been dualbooting to CM7 on secondary will lose that ability as well after applying that update. So unlike what you think, this is not a file to update stock 1.2 update under all circumstances regardless of what the starting point is. It has a specific use (update fro, a pre 1.2 stock primary eMMC boot, no dualboot, CWM recovery installed). Creation of an all situation stock restore file is impossible IMO, and the best you can do is wipe and apply 1.3 B&N stock update. You or I could technically create another equivalent file with update-nc-stock-1.3-keepcwm.zip /system files, kernel, ramdisk, etc., but this file would be subject to the same side effects as the original.

---------- Post added at 03:30 PM ---------- Previous post was at 03:24 PM ----------

It would work. If you apply my zip, there will be a uAltImg and uAltRam in /boot (in addition to uFImg and uFRam). If you apply another update that pushes the CM7 bootloader, it will then look for these files with trying to do an alternate boot, and would boot into a unrooted stock 1.3.
[Nook Color Android Development] yelloguy:
I get an error:

mounting <paths> failed: Device or resource busy

Any ideas?
[Nook Color Android Development] rajendra82:
I see a typo in my command (stupid Swiftkey X). It should be:

mount /dev/block/mmcblk0p1 <some directory>

Also try typing just mount in terminal to see if /dev/block/mmcblk0p1 is already mounted somewhere else.
[Nook Color Android Development] Taosaur:
Riiiiight... it would install stock 1.3 to the device. That's the intended behavior. The point is to avoid the unnecessary step of updating in any process that includes flashing stock to the sole or primary partition. One example of such a process would be a fresh dual boot setup. That it does not update or otherwise rely upon an existing install is the point.

Granted, such a file would not repartition the device, but it would install up-to-date stock in one step regardless of how a device is partitioned (1/5, 2/5, 5/1 or dual boot).
[Nook Color Android Development] rajendra82:
That 1.2 file you have does rely upon an existing pre 1.1 being on the primary boot partitions, and it wipes out the primary /system and puts in new files. It also pushes the stock 1.2 bootloader, so it is a bad idea to apply it after setting up dual boot. If fact the file is almost exactly the same as the B&N 1.2 update file you could get from their website, with the main exception of change in the script that installs CWM recovery instead of the stock recovery. You can already get the real 1.3 update file from B&N website and apply it on a stock boot, which will make you lose CWM recovery. After you do this, boot into an sdcard and flash CWM recovery. Two steps instead of one, but same effect. Neither the file you listed nor the 1.3 B&N update does anything to /media, so the paritioning of that as 1/5, 2/5, 5/1 is irrelevant.

By the way, every B&N update so far has been pretty much using the same script. They all fully replace what is on /system, pplus the bootloader, ramdisk, kernel, recovery, and the restre to stock script. As a result you do not need to update 1.0 to 1.1, then 1.2, and then 1.3. Any Nook Color can go straight to 1.3 using the latest update.
[Nook Color Android Development] yelloguy:
Excellent, I see that of the following:

"

uFImg and uFRam which are your secondary kernel and ramdisk (and whose names are mismatching the CM7 bootloader protocol)

u-boot.altimg and u-boot.altram, which are text files per the old bootloader method containing names of uFImg and uFRam

"

My Nook contains uEimg and uERam and the text files point to these. If I understand it right, I can flash the file in your first post and then the alternate images will be called uFImg and uFRam and I just have to modify the text files to point to these.

Thanks SO much.
[Nook Color Android Development] rajendra82:
When people set up dual boot during the time we had Eclair, the scripts from that time copied the stock kernel to uEImg, and patched the stock ramdisk and copied it to uERam. When we got Froyo, new scripts came out, and they named the copied files uFImg and uFRam respectively. Under both of those versions of dual booting, the u-boot.bin was not interactive and relied on the u-boot.altimg and u-boot.altram to point to the correct files. The new CM7 builds push their own version of a u-boot.bin, which is very nice, because it interactively allows you to boot into either primary, alternate, or recovery modes from either eMMC or sdcard. These u-boot.bin versions do not rely on the u-boot.altimg and u-boot.altram files at all. They expect the secondary kernel and ramdisk to be named uAltImg and uAltRam respectively. The file I posted pushes a stock kernel and a patched ramdisk to /boot and names them uAltImg and uAltRam. I don't try to push a u-boot.bin or the two text files. Since you got access to what was in /boot (i.e. mmcblk0p1), just rename uEImg and uERam to the new protocol, and edit those two text files to point to uAltImg and uAltRam instead of uEImg and uERam. That way you can dual boot using either the old u-boot.bin or the new one. If you apply both my update and CM7 with the bootloader, you won't need to do anything manually unless you want to get rid of a few unnecessary files left over from the old setup. In such a case, just gain access to /boot again and delete the now useless files uEImg, uERam, u-boot.altimg, and u-boot.altram.
[Nook Color Android Development] yelloguy:
Went exactly as you said. Renamed and edited the text first. Dual boot (still) worked.

Then I updated using your zip and got 1.3 working with dual boot.
[Nook Color Android Development] rajendra82:
I am glad it worked out for you. Setting this up was a learning process for me too. You can bet that when B&N sends out the 1.4 update, I'll be ready to fix that up. And no CM7 update is ever going to stop me from dual booting now.
[Nook Color Android Development] Taosaur:
False. Your description of B&N's update files, "They all fully replace what is on /system, pplus the bootloader, ramdisk, kernel, recovery, and the restre to stock script. As a result you do not need to update 1.0 to 1.1, then 1.2, and then 1.3." also applies to nemith's CWM-flashable 1.2 files. They constitute the full stock ROM and can be flashed over any other ROM or no ROM at all.

I flashed the 1.2-keepcwm.zip over CM7 three different times while setting up my dual boot, and had to update it to 1.3 on the second partition using jaso's file each time, which is still fewer steps/reboots than flashing the B&N update while stock was on the primary partition, which wouldn't have worked anyway because I have CWM on eMMC. Without some form of CWM-flashable 1.3, I would have had to backup my lone SD card, flash it with CWM, flash the 1.2 zip that nukes CWM, complete the process that way and restore the card afterward.

Most ROM updates replace the bootloader; you either flash updates with an appropriate uboot, or reflash uboot after each update.

To clarify, I assume you mean the script is changed to be installed by CWM rather than stock recovery.

False. The presence of CWM prevents the update from installing at all, as many people who pushed the shiny button in ROM Manager on their CM7 SD cards learned the hard way when the 1.3 update rolled out.
[Nook Color Android Development] rajendra82:
Since you seem to continue to indicate the need for a CWM flashable 1.3 update file, which would be the equivalent to the update-nc-stock-1.2-keepcwm, here is my attempt at such a file. This does not contain any 1.2 parts, and should get you close to perfect 1.3 stock when applied, with the the exception of the eMMC recovery, which will be left as CWM for the sake of easy reversal. I unfortunately have no way to test it personally, as my Nook Color has Phiremod as the primary partition, and the stock ROM is on the secondary partition. Feel free to try it, and let me know how it works out. Just make sure to keep a Nandroid backup of your existing ROM, just in case you need to restore back to it. If this works, I can create the other file, which wipes the recovery as well. It should be just a few small changes to make that. I just don't feel comfortable putting that up until the safer of the two files has been tested.

http://www.mediafire.com/?mchkv6xckp06rhx

MD5 Sum: e44fe34e24547b6cfd8148736e16b6a1
[Nook Color Android Development] Taosaur:
My plate's a bit full the next couple days and I don't *need* the file right now (I'm already set up), but there are a couple other things I want to test anyway, so I will give it a go by the weekend.
[Nook Color Android Development] Taosaur:
CWM initially rejected it as (bad), so I re-downloaded in case it got corrupted, but noticed the corresponding 1.2 file I have is "...signed.zip," so I changed your file name to match and it went through just fine. I doubt nemith's files were in any sense "signed" either--he was probably also getting around CWM naming conventions by naming them that way.

I poked around stock and did a bit of browsing, and everything seems great. I undid dualboot first, so I just have your 1.3 right now--I'll put everything back together later on today.

I'm thinking about rooting stock, just because I haven't done it before :D

Thanks again for the image. If you get a chance to make a complete back-to-stock image, I'm sure people would appreciate it, though I wouldn't be able to test that one without considerable image juggling on my SD card.
[Nook Color Android Development] rajendra82:
I took out "signed" from the name because CWM does not require the zips to be signed, and I had deleted the files containing the signature information from the original version. Having those files and signed in the name should have nothing to do with the update being rejected. When it says "bad", that means a corrupted zip file that CWM can't decompress. The other reason it rejects the file is because there is an error in the script. In this case it will stop on a specific line number.

Here is a link to the other file, which will give you complete stock 1.3 (with the exception of wiping user data) upon flashing from CWM, and including replacing the recovery with stock.

http://www.mediafire.com/?jpmyhd5d5e6p6vh

I should have posted MD5 Sums of all files to avoid the issue of corrupted download, like you had. I will edit the older posts for the other files. This file has an MD5 sum of: aa6442a0ae365ffa9221df65913fbd8b

If the MD5 Sum of your download does not match, redownload and recheck before flashing.
[Nook Color Android Development] Taosaur:
Aaaaand I'm back to my dualboot setup, quite painlessly. I have no interest in nuking CWM on my NC at present, so I won't be testing that last file unless I get the urge to be a real completist and tuck away a bootable CWM SD image with all my zips.

The keepCWM zip let me boil down my dualboot guide considerably, too, and get it better organized to address pretty much any starting point.
[Nook Color Android Development] spdsl:
Thank you. I setup my Nook dual boot emmc using this guide. Cm7 on emmc1 and stock bn 1.2 on emmc2. After updating cm7 to the latest nightly (177) my dual boot option was disabled. I followed the instructions here and fixed my boot files. I then used your zip file and updated my stock BN to 1.3 with no issues. The wife can read her magazines and dual boot works again.

Any noobs, like myself, needing to enable ADB in windows follow this link.
[Nook Color Android Development] Taosaur:
For those looking to go from zero to dual boot in considerably fewer steps, I just dropped my up-to-date dual boot guide in the dev forum, including rajendra82's 1.3 files: [eMMC]Updated Dual Boot Guide[CM 7.1+][Phiremod 7+][Stock 1.3]
[Nook Color Android Development] arda99:
I'm currently on dualboot CM7+rooted 1.2 and about to upgrade to CM7+1.3. I know I can do the upgrade by flashing the zip file OP provided but how to root the stock 1.3 then? I think MN will apply to first partition only.
[Nook Color Android Development] Taosaur:
AFAIK there is currently no way to root stock on the secondary partition, nor anyway to backup and restore /data from the secondary partition. Whether MN could be successfully modded to root the secondary partition, I don't know, but basically if you want rooted 1.3, you'll have to start from scratch.
[Nook Color Android Development] Windsor1959:
1.3 zip file experiment

This isn't a dual-boot question (sorry), but it's about one of the files referred to in this thread, so I'll try my question here. I decided to try installing rajendra82's update-nc-stock-1.3.zip file from a CWM sd card to see if I could go directly to stock 1.3 on the emmc. (I had MIUI on emmc before, and all properly backed up.) It installed smoothly and seems to work fine. As a little experiment, I slipped in the Kindle and Zeam apks into the system/app folder, and they are also working.

The one little concern I have is that when I went to the settings page to check the software version, it said 1.2. Why would it not show 1.3?
[Nook Color Android Development] carguy88:
Mirror?

Rajendra82's file links are now dead. Anyone willing to post a mirror?
[Nook Color Android Development] Taosaur:
Here's 1.3-keepcwm: http://www.multiupload.com/V3V6NBXU2X

1.3-full-restore: http://www.multiupload.com/BW8FIEJ2GH

I'm not sure if the 1.3-to-alt-boot I have is the one from this thread or not, so someone else will have to cover that one.

ETA: The "full restore" zip does take you back to clean stock, but it's 1.2. I'm thinking maybe rajendra made the changes and then renamed and uploaded nemith's old file instead of the updated one.
[Nook Color Android Development] rajendra82:
I have uploaded files to mediafire and updated the links. Didn't know that dropbox had a traffic limit.
[Nook Color Android Development] joej:
I have also uploaded them here just in case

https://rapidshare.com/files/3996191696/update-nc-stock-1.3.zip

https://rapidshare.com/files/1907156045/update-nc-stock-1.3-keepcwm.zip
[Nook Color Android Development] Windsor1959:
1.3, or 1.2?

In a previous post, I mentioned that I had installed rajendra's 1.3 full-restore on my emmc. It installed just fine, and runs just fine. But, when I looked at the version number in Settings, it said I had 1.2. Well, is it 1.3 or 1.2? I have just had my answer. I see the little green Nook icon on the lower left of my screen, telling me that I've just been upgraded to 1.3!
[Nook Color Android Development] Taosaur:
I just ran that zip for the first time and can confirm it's 1.2 :/ The keep-cwm version does indeed take you to 1.3. I suppose it's no big deal, given that running the full restore will set you up for an OTA update anyway.
[Nook Color Android Development] rajendra82:
No point troubleshooting the old file any more, because I am working on creating the 1.4.1 files as we speak. Hopefully this time there will be no issues with not taking you all the way to the full experience.
[Nook Color Android Development] Taosaur:
On a down note, people are reporting (and I also experienced) that they're unable to install apps from B&N's market with 1.4.1 on secondary. I don't know if the same is true for books and magazines.
[Nook Color Android Development] rajendra82:
Can you tell me how you installed the 1.4.1 on secondary. If you fully restored primary to stock and then moved it to secondary can you point me to the CWM zip you used to do the moving. If you directly updated the secondary from 1.3 to 1.4.1, can you point me to the zip you used to do the update. I would like to troubleshhot this issue if I can. No promises, but let me try to figure out why it might be happening.
[Nook Color Android Development] Taosaur:
Actually, looking at comments on my blog, I notice someone reported the same thing with 1.3.

What I did was use the 1GB CWM 3.2.0.1 image linked in my dual boot thread to flash your 1.3-full-restore (which was probably just nemith's 1.2 mislabeled), then used B&N's 1.4.1 update. I ran prep-dualboot, froyo-to-dualboot, and installed CM9 + ICS gapps. Both partitions worked just fine, but when you try to confirm a B&N market install, it gives you an error that maybe there's not enough room and you need to archive some things. Obviously on a fresh install w/ 1GB /system, that's not the case.

What I'm trying to do now is move CM9 to secondary and run CM7 primary, but froyo-to-dualboot doesn't seem to get it done. CM7 works fine, but alt-booting just loops the CM7 boot animation (should be showing the ICS construction-paper-whirlwind).

ETA: if you're really curious, I also documented the whole process (up to getting CM9+B&N1.4 installed) in a video: http://www.youtube.com/watch?v=5owXz6fgyjM