yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] candre23:
Apparantly my problem was a combination of a slow SD card (class2), a large /media folder (650mb), and impatience.

I deleted the backup tar.gz and tried the backup again. I got the same result, but decided to let it sit a while just to be sure. About 10 min later, it finally completed and I noticed the tar.gz backup was about 630mb. I deleted that backup and cleaned everything but the dualboot folder. Ran the script again with a bit more patience and everything worked. Total time was almost 15 minutes. Thanks again to the OP.

Now to get gapps working in nookie froyo.
[Nook Color Android Development] DiscoPh3v3r:
I keep getting an erro on the first command saying it cant change the directory to /sdcard/dualboot

I can change it to sdcard but not sdcard/dualboot

Any suggestions?

I am using the rooted 1.1.0 update BTW
[Nook Color Android Development] candre23:
This is proving to be harder than I thought. The instructions on nookdevs are tailored to installing on stock, but NF for dualboot is using different partitions, no? Any guide for gapps on dualboot?

Do you have a dualboot directory on your card?
[Nook Color Android Development] DiscoPh3v3r:
Yes I do, I have even tried changing it to other directories I have ob the sdcard and nada. I still get the message. Do I need anything besides adb for this to work? Do I need to change permissions or anything? Thanks :)
[Nook Color Android Development] x-ravin:
I just followed the guide on NF tips:

http://nookdevs.com/NookColor:_Nookie_Froyo_Tips

Worked like a charm.
[Nook Color Android Development] newsted33:
I was having this issue too. I fixed it by opening up Nook Color Tools -> Development and turning off Auto Mounting so that it wouldn't mount the SD Card or Media in Windows.
[Nook Color Android Development] candre23:
I didn't have anything else besides ADB. The only thing I can think of is that android is case-sensitive, and you have to use the exact casing to get to a directory. Other than that, I don't know what to tell you. Sorry.

That worked. Thanks.
[Nook Color Android Development] DiscoPh3v3r:
Thanks I'll try this. I was wondering what he meant by eject it or "safely remove it" and it wasn't showing in adb. I'll post later if it worked. :D
[Nook Color Android Development] candre23:
Adding the rookie1's softbutton framework borked the froyo boot, so now I can only boot into stock. Does anyone know if I can just re-run the script to get back to a working dual-boot, or will that mess things up further?
[Nook Color Android Development] Canadoc:
Have no clue what you did here but thanks!!!

After borking my froyo sd card adding something that modded the frameworks to give software buttons I figured it was an opportunity to try to get the dual boot going. Did not notice your post here about it causing endless reboots in 1.1.

I copied what you did here and now I can reboot back into 1.1 eclair again.

Could you explain to a more layman type, what you did above and what effects I can expect? in both froyo and eclair
[Nook Color Android Development] DiscoPh3v3r:
Sweet, thanks newsted33 that did the trick.

And to anyone who gets the error: "tar remove '/' before member names" or something along that lines, just ignore that for about 10-30minutes and it will complete afterwards

You know that it is not finished because it doesnt put the "#" back. So just be patient and it will work :) thanks for the help and for this! this is awesome! :D
[Nook Color Android Development] Divine_Madcat:
Basically, it blows away the previously created Froyo partitions, the broken media partition, and then recreates the original /media partition with all of its size. I have to admit i reverse engineered it from the OP's script, not knowing that he had included his own undo script which should end up with the same result.
[Nook Color Android Development] Canadoc:
I tried his script it didn't work.

What you did, did work and thx but some things are not as before:

1)On boot instead of getting the "future of reading" it says loading

2)If I hold down the nook home button I get it trying to boot into froyo and stopping at the blue android logo.

3)I suspect this means his remapped buttons for getting into recovery are still different too. (I haven't verified yet). Any idea how toget those things back?
[Nook Color Android Development] chhaggerty:
I was having the same problems trying to add B&N 1.1 rooted to dual boot because of the lack of functioning media partition. I was however able to setup the partitions manually using rookie1's script as a guide. And now I do have a well functioning rooted 1.1 dual booting with NF both at 1.1 GHz. Isn't life grand? :-)
[Nook Color Android Development] rookie1:
To get back to stock u-boot.bin, do the following from adb shell,

mkdir /data/tmpboot

mount -t vfat /dev/block/mmcblk0p1 /data/tmpboot

cd /data/tmpboot

mv u-boot.bin.stock u-boot.bin

rm uFImg

rm uFRam

cd /

umount /data/tmpboot

rmdir /data/tmpboot

then reboot.
[Nook Color Android Development] Divine_Madcat:
What he said. Answering you questions on why -

My instructions only repaired the media partition. What was happening with yours, is that the modified u-boot piece in the /boot partition was still there,and that was what was modified to support dual booting. HIs instructions allow you to send it back to stock B&N u-boot, which makes everything normal. The rm commands provide cleanup, removing the non-used Froyo kernel and Ramdisk.
[Nook Color Android Development] Canadoc:
Thanks a bunch!!!

I see here someone got 1.1 working on dual boot......
[Nook Color Android Development] Pinesal:
Ok I skimmed through this thread and I think I have come to an understanding.

So dual booting worked fine when we were on 1.0.1 but with 1.1.0 the media partition doesn't get mounted properly and now the thread is mostly about how to undo the dual boot?

So this is got a good option for right now?
[Nook Color Android Development] Canadoc:
Could you detail your fix here for us 1.1 folk?
[Nook Color Android Development] Starfire-1:
Personally, I'm not sure that there really is a problem here. I don't doubt the observation that the pre-rooted sideload to 1.1 has a problem if the media partition does not exist. But the dual boot script does actually re-create partition #8 (albeit a little smaller and at the end of the physical drive). There may be some subtlety that the media partition must start at 2311MB into the eMMC, but I doubt it.

I actually set my system up through adb line by line (from a Linux host) so that I could verify the steps. I really just wanted to make sure that parted didn't hose my partitions by overlapping cylinders or sectors or something silly. In any case, the media partition was recreated and restored from the temporary archive, everything else went smoothly. I looked through decad3nce's 1.1 upgrade script and he only transfers over the kernel to the /boot partition, so the modified u-boot.bin that allows dual booting should be ok.

All that said, I have not run the upgrade after setting up the dual boot. I ran it before, but had problems with USB debugging "sticking" and the functionality of the softkeys, so I nandroid-ed back to 1.0.1.

I do have one question however - I noticed that the cache partition (7) is mounted by nookie froyo and I'm guessing is shared with the stock system. Is this a problem if you boot back and forth between systems? I noticed that the touchscreen performance for nookie froyo is not very responsive. One of the "fixes" apparently is to remount the cache partition. Could this be related?

@rookie1 Thanks for your dual boot work!
[Nook Color Android Development] rookie1:
If I'm not mistaken, nookie froyo creates its own cache directory on cache partition. /cache should be a symlink in nookie froyo
[Nook Color Android Development] Divine_Madcat:
Well, i don't know WHAT caused the problem on my end, but i will say for sure that the scripts did NOT sucessfully recreate my /media partition, as the damn thing has 0 bytes allocated to it. Manually deleting and recreating the partition worked, which reinforces the idea that the partition was broken before hand.
[Nook Color Android Development] jasoraso:
hmm - I had updated to 1.1 using Decadence's v.1 script.

I then ran the dual-boot script posted - and although I did have a few runtime errors noted in my previous post, it did install for me and ran quite well. So I think that this dual-boot script DOES work on B&N 1.1. One thing to note is that there are many reports of flakey USB debugging w/ the 1.1 updated through decadence's script. I know that I have experienced many funky issues w/ USB debugging.

Maybe it would be better to run through terminall on the NC when in 1.1 so the script won't get have errors from USB issues; as well as making sure that the drives stay disconnected (another problem I've experienced).

Just for informational purposes, after installing the dual-boot, I updated the kernel to 1.1ghz (manually renaming the uimage); and then changed the framework w/ SamHalfs framework to get rid of the no-service icon.

I did experience some random reboots, but before I could trouble shoot too much; I switch the framework again w/ Rookie's files to get the softkeys on the notification bar; and now I'm in a reboot. I have tried erasing dalvik from my 2.1 installation; but it hasn't worked yet ....
[Nook Color Android Development] Starfire-1:
Just for clarity - did you replace the 2.1 kernel or 2.2 kernel? I replaced the 2.2 kernel with the froyo 1.1 GHz model, but named it uFImg on the boot partition.
[Nook Color Android Development] ellopr:
receiving the error

/sbin/sh: newfs_msdos: not found

please help

someone please attach the file if you have it.
[Nook Color Android Development] rumitg2:
i really wanna try this out but whenever i try to run the script i get an error the adb shell

~ # cd /sdcard/dualboot

/sbin/sh: cd: can't cd to /sdcard/dualboot

i followed all the instructions but im trying this in CWR because ADB shell for some reason wont work if my nook is powered on. is there any thing i could do?

also i tried running this form a terminal app and i think it may have bricked my nook because it doesnt even turn on. any advice? or should i try to get my nook exchanged at a B&N?
[Nook Color Android Development] carbonfiber1:
How would i install an overclock kernel to the froyo partition? do i just flash it through clockwork recovery? any help?
[Nook Color Android Development] aho43:
Got this working on rooted 1.1 w/o having to do anything manually. Thanks to rookie1, this is great!

Had to run the script twice.

The first time I ran the script I ran it from Terminal. The inherent problem with this is that at some point the Nook gives you a message about needing to reboot and the screen is stuck and unresponsive. So you have no idea what the script is doing in Terminal. I waited a while and rebooted.

The dualboot did not install properly. It had gotten to the point where it repartioned the eMMC, but hadn't done the rest. Also when I checked the phone storage it had shrunken from 5gb to 3.x gb and the media hadn't been restored.

Fortunately the media_backup was still on my sdcard and I was able to verify that everything was backed up. It wouldn't have been a big deal if it was all lost, it was just a few books which I had backups of on my desktop.

Didn't feel like restoring media. ran the script again, this time using adbwireless, regular adb hasn't been cooperative w/ 1.1 for me, and let it run to completion ignoring the Nook telling me that it needs a restart. Rebooted once ADB gave me

>>>>>>>>Done.

Booted into Froyo and 1.1 fine.

So this definitely works w/ 1.1. Here are my tips if you're having trouble w/ 1.1.

If you're having problems w/ adb, use adbwireless, its free on the market. People seem to be having trouble keeping /sdcard and /media from mounting anyways. If you use adbwifi make sure you're plugged in charging or have something installed to keep the wifi from kicking out when the screen goes off. If you're using regular adb you might want to set your Nook not to automount.

If you want to save time on the /media partition being backed up, move stuff to your sdcard or your computer.

BE PATIENT, let the script run to completion.

Don't press the reboot button even if the Nook is prompting you to, wait until the script is finished

Don't run the script on a Terminal -_-

Thanks again to rookie1, now I just have to google apps and market installed and I'll be good to go.
[Nook Color Android Development] sbddude:
Can this Dualboot setup work with Honeycomb?
[Nook Color Android Development] JimSP:
Ok. I can also confirm that this does work with 1.1, but it is not exactly straightforward.

I started by updating my autonootered 1.01 install with Decad3nces clockwork mod zip file. Once it was up and running and I confirmed that everything (youtube, gmail, etc.) was working I moved on to installing the dual boot.

Following an earlier post by aho43 I ran rookie1's dual-boot.sh through adbwireless... this is where the problems started.

First I made the mistake of hitting okay to the reboot required error that shows up on the screen while the script is running (don't do this!). After reboot I continued to get the same message and it would reboot after pressing okay. So 8 reboots to recovery and a nandroid restore later I was back to 1.01 and everything was working fine.

I flashed Decad3nces clockwork zip again. This time I was greeted with the same error message about requiring a reboot. So I nandroided back to 1.01 again and started playing around and realized my market was broken and I downloads would seem to start and then die... hmmmm.

So I read through the forum and tried rookie1's script to fix the partitions and ended up with errors. Then I followed a post by Divine_Madcat in this thread to repartition from adb shell line by line. I realized that it took 3 times running the command /data/dualboottmp/parted -s /dev/block/mmcblk0 rm 8 before it would take. Finished typing rest of script in adb and my partitions were back to normal.

Updated to 1.1 again and this time no error messages. Proceeded to run dual-boot.sh through adb wireless again and got same error when booting eclair (nookie froyo booted up fine). So I went ahead and plugged in usb cable while error message was on screen and ran the dual-boot.sh in adb for a second time. This time when I booted back into eclair no error message. Success! Dual boot with 1.1 and Froyo.

It's strange, but it seems like partitioning through adb and busybox leads to problems with creating and/or removing partitions. Running the commands multiple times until they take seems to be the key (at least in my case).

Thanks to rookie1, Decad3nce, Divine_Madcat, and aho43 for all the posts that helped me out.
[Nook Color Android Development] mellopete:
Customized Nookie Froyo 0.5.9 by brianf21

Nice script. I'm trying to use it with brianf21's Customized Nookie Froyo 0.5.9 and it hangs on the "Android_" screen. I extracted the boot, system, and data partitions with winimage and zipped them as tar.gz. The script finished fine. Any idea why it doesn't work? Using the original nookie froyo and 1100Mhz kernel works great though. Nice job.

Edit: The problem was using winimage and permissions. I used Ubuntu, logged in as root, and it worked.

Edit 2: Spoke too soon. Now it gets to the boot screen, but the screen flashes every 2 seconds and it's been trying to boot for 15 minutes.
[Nook Color Android Development] weavin42:
I used the custom froyo build script on emmc from http://xdaforums.com/showthread.php?t=922324 after I installed the standard dual boot. I did this by changing the partitions in copy2emmc.sh from 5 and 6 to 9 and 10 and it worked great.

I have two questions:

One, I can't seem to triple boot with honeycomb on SD (might have been a problem with download...will re-burn sd card and see) is that behavior to be expected?

Two, I rarely boot into the stock eclair, is it possible to format partitions 5 and 6 and copy 9 and 10 into them, remove 9 and 10 and revert back to original u-boot and ramdisk and change uFimg to uImage? Is that the best way to only boot NF?

EDIT: Got honeycomb to triple boot, must have been a bad burn or dl.
[Nook Color Android Development] ver2go:
Anyone else have problems with the Nookie image in this thread? I loose the screen everytime I have a Appointment Notification from ActiveSync.

I'm not sure where to report it, since the link for the image wasn't to a thread.

Are there other Froyo Images that can be used with dualboot?

Here is the stack trace from the screen crash:

Pid: 905, comm: SurfaceFlinger
CPU: 0 Tainted: G W (2.6.29-omap1 #1)
PC is at 0xafd0fc50
LR is at 0xab90c617
pc : [<afd0fc50>] lr : [<ab90c617>] psr: 00000010
sp : 47f6ed70 ip : ab9144bc fp : 00125ab0
r10: 47e6f000 r9 : a811c319 r8 : 8090b210
r7 : 00000000 r6 : 00142900 r5 : 00144038 r4 : 00143fb8
r3 : 00000002 r2 : 001428f8 r1 : 00000001 r0 : 0014403c
Flags: nzcv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Control: 10c5387d Table: 9fdc4019 DAC: 00000015
[<c0051908>] (show_regs+0x0/0x50) from [<c0080c1c>] (__schedule_bug+0x54/0x60)
r5:c04bb490 r4:dfffdfb0
[<c0080bc8>] (__schedule_bug+0x0/0x60) from [<c03b81d4>] (schedule+0x32c/0x420)
r5:c04bb490 r4:0018cf7a
[<c03b7ea8>] (schedule+0x0/0x420) from [<c03b88c0>] (schedule_timeout+0x80/0xdc)

[<c03b8840>] (schedule_timeout+0x0/0xdc) from [<c03b874c>] (wait_for_common+0x17
0/0x1a8)
r7:00000002 r6:dfffc000 r5:dfa12e14 r4:00000080
[<c03b85dc>] (wait_for_common+0x0/0x1a8) from [<c03b87f8>] (wait_for_completion_
timeout+0x14/0x18)
[<c03b87e4>] (wait_for_completion_timeout+0x0/0x18) from [<c0281e24>] (omap_i2c_
xfer+0x240/0x3b0)
[<c0281be4>] (omap_i2c_xfer+0x0/0x3b0) from [<c027e850>] (i2c_transfer+0x94/0xb8
)
[<c027e7bc>] (i2c_transfer+0x0/0xb8) from [<c027f534>] (i2c_master_recv+0x48/0x5
8)
r7:0000003e r6:c04e46ac r5:df01e9c0 r4:00000001
[<c027f4ec>] (i2c_master_recv+0x0/0x58) from [<c0320204>] (dac3100_read+0x5c/0x6
8)
r4:df01e9c0
[<c03201a8>] (dac3100_read+0x0/0x68) from [<c0320298>] (AudioRecovery_dump+0x58/
0x7c)
r4:000000a4
[<c0320240>] (AudioRecovery_dump+0x0/0x7c) from [<c006fbc0>] (omap_mcbsp_tx_irq_
handler+0x2c4/0x2e0)
r5:000002fd r4:df9aa6c0
[<c006f8fc>] (omap_mcbsp_tx_irq_handler+0x0/0x2e0) from [<c00bad60>] (handle_IRQ
_event+0x3c/0x74)
r7:0000003e r6:00000000 r5:00000000 r4:d84c4d40
[<c00bad24>] (handle_IRQ_event+0x0/0x74) from [<c00bc5a8>] (handle_level_irq+0xa
c/0x158)
r7:00000001 r6:d84c4d40 r5:0000003e r4:c04bd468
[<c00bc4fc>] (handle_level_irq+0x0/0x158) from [<c004f04c>] (__exception_text_st
art+0x4c/0x74)
r7:00000001 r6:00000000 r5:c05114c0 r4:0000003e
[<c004f000>] (__exception_text_start+0x0/0x74) from [<c004fd84>] (__irq_usr+0x44
/0xa0)
Exception stack(0xdfffdfb0 to 0xdfffdff8)
dfa0: 0014403c 00000001 001428f8 00000002
dfc0: 00143fb8 00144038 00142900 00000000 8090b210 a811c319 47e6f000 00125ab0
dfe0: ab9144bc 47f6ed70 ab90c617 afd0fc50 00000010 ffffffff
r7:00000001 r6:00142900 r5:fa200000 r4:ffffffff
#
[Nook Color Android Development] weavin42:
You could try the custom image method I mentioned above. You burn the image to SD card, modify copy2emmc.sh in system/bin of the SD card for the system and data partitions for dualboot (9 and 10). Next just boot the SD card run the script and reboot. You will lose everything you have installed but there are some nice features and it might be worth it and if you are really lucky it might fix your problem!
[Nook Color Android Development] mellopete:
You were right! I used the copy2emmc script and all is well. Thank you.
[Nook Color Android Development] rookie1:
Yes it works with HC. You need to do it manually though. Since deeper-blue only uploads a SD image, it's difficult to automate the process by scripting. And I'd prefer not to repackage and distribute deeper-blue's work.
[Nook Color Android Development] carbonfiber1:
im having problems reverting the dual boot i get errors saying reformat-media.sh: line 9:/data/dualboottmp/parted: not found all the way to line 12

any help?
[Nook Color Android Development] trentmaynard:
What method might that be?
[Nook Color Android Development] flak0:
@Op how do we update this for the new versiob of nookie froyo 0.66. Thanks

edit: I just changed one line in the dual-boot.sh to reflect the updated base, seems like it worked.
[Nook Color Android Development] sec6:
Madcat,

I tried this script in this thread with 1.1 installed first. Everything looked as though it was going smoothly. But it did hose my media partition--0 of 0 bytes. Tried all the fixes here, but no luck. I tried doing a factory restore, but now have a factory restore with 0 of zero bytes for my storage. The drive is unreadable. You say that you were able to get it back. Could you give me a hint of what I should try. I in good faith tried this dual boot, thinking that it was at least as reliable as other things on the nook color board--it obviously isn't and with some not so great consequences. So could you give some instructions. I'm in Win7 64 bit. I have adb. My restored stock is now 1.0.1 autonootered.

Disregard Madcat: Tried the manual restore instructions in the thread and recovered the partition.
[Nook Color Android Development] flak0:
I also noticed that i have 0 out of 0 available on the Nook Stock Eclair. When I connect to CPU it tells me Drive K must be formated.
[Nook Color Android Development] Novarider:
Would it be possible to dual boot Froyo and Honeycomb? What would be great is fi I could run this script to get dual boot on my NC of Eclair and Froyo. Then I would boot into Eclair and run a Honeycomb to emmc script to replace Eclair. Would that work?
[Nook Color Android Development] flak0:
@ OP I attempted to unpack the Ramdisk to make the edits to reflect the changes in Nookie Froyo .66 however when issuing commands:

i get: uRamdisk not in gzip format

premature end of archive.

Can you please tell me how you packed the RamDisk. Thanks. I am trying to modify init.rc
[Nook Color Android Development] nookierookie:
I'd like to know if your script differentiates which you have running as your base system, eclair or Froyo. I've been running Froyo off my emmc for a while, and with its update to 0.6.6, I wonder if I can run this script from within FROYO -- since I don't retain a 1.0.1 environment any more.

The result would be ending up with a dualboot Froyo 0.6.6/Froyo 0.5.8 system, at which point I could probably manually push/dd/flash the system/data/ramdisk and uBoot from Honeycomb (as per the fast-out-of-the-starting-gate OP's to the appropriate *new* partition locations -- changing the proper names, of course, to uFBoot (and so on...).

That is, are the partitions in c-man's Froyo build the same layout as the *stock* one?

And does your modify .init file for boot only care which buttons are pressed and which it boots from -- uF or uB?
[Nook Color Android Development] rookie1:
Refer to http://nookdevs.com/NookColor:_Nookie_Froyo_Technical_Page#Modifying_init.rc for unpacking instruction, and this http://nookdevs.com/NookColor:_Build_the_Original_Kernel#Create_your_uRamdisk_file for packing.
[Nook Color Android Development] rookie1:
My script does not care what's running as base. The only changes are modify u-boot.bin, add uFImg and uFRam, and modify partition 8 to create space for partition 9 and 10.

I'd recommend not use dd. You can use 'cp -a' or tar to copy the files over and preserve file permissions.

The modified u-boot.bin checks whether home key is pressed. If not, it will boot using uImage and uRamdisk. If it's pressed, it will boot using uFImg and uFRam. You can put whatever you want as uFImg and uFRam, as long as they are in the right format.
[Nook Color Android Development] Novarider:
I'm already running froyo on my emmc. Could I just replace the froyo image your supposed to download with a honeycomb image and run your script? That way I would have a dual boot of froyo and honeycomb