yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] BugsBunny891:
I agree. the random reboot has only happened to me while on eclair, nookie froyo hasn't given me a single one.

Congratz to the OP for getting dual boot to work.
[Nook Color Android Development] jasoraso:
Does this affect Clockwork Recovery at all?
[Nook Color Android Development] spyz88:
Can you still use the stock e-reader stuff if you put Nookie Froyo on it or do you have to dual boot in order for it to work? I mean the being able to read magazines and books and all that good stuff. Thanks
[Nook Color Android Development] samuelhalff:
Maybe someone here can give me a hint.

I've managed to get a stable version of NF on eMMC. But I can't manage to mount sdcard. And if I mount media, it's corrupts my boot partition, as if it mounted on mmcblk0p1, which is maybe the case...

Any advice on how to edit my init.rc?

Thank you
[Nook Color Android Development] BugmanXDA:
Another thread claimed that the reboots people were having were the Java run time service rebooting, not an actual OS reboot.
[Nook Color Android Development] eyecrispy:
It's not always just the JVM crash "reboots". I've had actual reboots. Sometimes, it's just JVM. Other times, it's an actual device reboot. I took care of the device reboot by using the Settings Profile method.
[Nook Color Android Development] runhopskipjump:
Once i put the wifi sleep policy back to Default my reboots stopped. I recommend people use waketimer to keep wifi alive while the screen is off. It was mentioned in the wiki.

Great job on the dual booting!
[Nook Color Android Development] chhaggerty:
Excellent work. How large did you make the mmcblk0p9 and 0p10 partitions and could you provde a link to android gparted? Thanks much.
[Nook Color Android Development] yossarian229:
^This.

solution worked for me as well.
[Nook Color Android Development] khaytsus:
Nope, I've never seen my NC have a Java VM halt, it's full OS reboots. My phone's ROM cook says that's generally a kernel panic, but I've never gotten any logs from the event.
[Nook Color Android Development] samuelhalff:
If anyone is interested, I've managed to get NF on eMMC with mounting uSD.

Thought you should know.

Sam
[Nook Color Android Development] jasoraso:
Now that there is a stable o/c kernel for Froyo, I would like to do a dual boot installation; but the instructions (especially the packing ramdisk part) are still a little over my head. That probably means I shouldn't attempt it, but if anyone has any more tips, I'd appreciate them!
[Nook Color Android Development] rookie1:
I'm creating a script to do the installation. Will update the 1st post once I tested it.
[Nook Color Android Development] jasoraso:
That would be great!
[Nook Color Android Development] Canadoc:
Wow fascinating work. Will this still work with clockwork recovery installed ?

What about with eclair 1.1?

Will both nookie and eclair be able to read from the sd card?

Sent from my Nook Color
[Nook Color Android Development] rookie1:
The script does not touch recovery, besides changing the keycombo. So it will work with CWR installed. But CWR is not aware of the additional partitions (9 and 10), so I guess it won't backup and restore them.

Both eclair and froyo can access the sd card. In froyo /media is not automatically mounted. Not sure whether this is a nookie 5.9 bug.
[Nook Color Android Development] aztigen22:
i already did it as you can see, that code in the terminal is what displayed.Meaning i already deleted the partition 9 and 10..however, my NC now is in stock, but my media partition is 3.72mb only.

Edit: i was snipping around the dual-boot.sh and found the answer! i was installing a renamed nfroyo 5.9 not the base. I edited a little part in the script and added the 6.7 and tried to repartition again. It worked. Now on dualboot eclair and nfroyo6.7.Thanks Rookie1!

PS. i think that answers my question, the DD command i did only restored boot and system not media.
[Nook Color Android Development] Novarider:
I had to run the code by hand line by line to get my media back to 5gb. The script didn't work
[Nook Color Android Development] aztigen22:
oh! so thats why i was wondering it seem like when i was running the reformat script it was like just echoing.. i could just reflash the system boot and media, but ill be back to start registering my device. nah, ill stick with you advice. ''Line for Line'' command. Thanks Novarider!
[Nook Color Android Development] DFu:
Has anyone modified the Honeycomb v4 RAMDisk to enable dual booting Eclair and HC on eMMC? I'd be happy to do this if I could figure out how to modify the RAMDisk. Posts I've seen elsewhere have talked about using gzip and cpio for the RAMDisk, but those fail (the Windows versions at least) when used on the uRamdisk files from Froyo/HC.

Alternatively, what about moving Eclair from eMMC to SD so that we can use eMMC just for Honeycomb (or Froyo), yet boot to Eclair when needed/desired?
[Nook Color Android Development] fwdixon:
Ok, well, I finally got ADB working correctly on my old Win XP x86 laptop and was able to restore the original eMMC partitions via adb. Now that that's out of the way...let me see what's next :D
[Nook Color Android Development] Novarider:
This will get you both Froyo and Honeycomb on the emmc.

http://xdaforums.com/showthread.php?t=943724
[Nook Color Android Development] numus:
Does this work with any version of Nookiefroyo 0.6.7 or only 0.5.9?

basicallly... http://edencomputing.com/nookcolor/nookie-froyo-base-0.6.7.tar.gz will that base work?!?
[Nook Color Android Development] aho43:
you can install this w/ 6.7 but you will have to modify the script and install a customized uFram built for 6.7.

Settting up dual-boot partitions and installing 6.7:

http://xdaforums.com/showpost.php?p=11226071&postcount=139

Installing customized 6.7 uFram, scroll down a bit for the uFram file:

http://xdaforums.com/showthread.php?p=11289860#post11289860

Some advice for running the script, if you have a lot of content in your /media partition i recommend backing it up manually to your computer, and then deleting that data off your nook color. The script will back up /media for you, but if there is a lot of stuff there it will take a while, and the backup could potentially be larger than your sdcard. You can always add the content back once you are finished w/ setting up dual boot.

I would also open up the script and look at it line by line and get an understanding of what it is actually doing.
[Nook Color Android Development] numus:
Ya already looked at it line by line... didn't understand 100% (still reading up on the differences between B&N android structure and everything vs what samsung uses).

Thanks for the info
[Nook Color Android Development] Canadoc:
[QUOTE

Both eclair and froyo can access the sd card. In froyo /media is not automatically mounted. Not sure whether this is a nookie 5.9 bug.[/QUOTE]

/media is the internal media partition on eclair? What would normally be on it?

Sent from my Nook Color
[Nook Color Android Development] Bandage:
Any idea what I'm doing wrong here? Followed your instructions...and here's what's going on:

Microsoft Windows [Version 6.1.7600]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\4>adb shell

# cd /sdcard/dualboot

cd /sdcard/dualboot

# busybox sh dual-boot.sh

busybox sh dual-boot.sh

>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>Create working directory

>>>>>>>>>>>>>>>>>>>>

mkdir failed for /data/dualboottmp, File exists

dual-boot.sh: line 5: tar: not found

Unable to chmod /data/dualboottmp/parted: No such file or directory

>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>Back up /media to sdcard

>>>>>>>>>>>>>>>>>>>>

dual-boot.sh: line 11: tar: not found

Backup failed. Exiting.

#
[Nook Color Android Development] rookie1:
Can you run just 'busybox' alone on adb shell command line? what is the version of busybox? and do you have 'tar' listed in 'Currently defined functions:'?

You might want to try update your busybox following this link,

http://nookdevs.com/NookColor_Installing_Busybox

Scratch that, it seems busybox from the above link has some issues. I've updated my script. Please download dualboot0.2.zip from the 1st post again.
[Nook Color Android Development] 4x9:
my 0.1.zip is ok!!haha
[Nook Color Android Development] Divine_Madcat:
Two quick questions -

Is this compatible with the 1.1.0 Update?

If we do want to try this, is there an easy way to "uninstall"? Or, a way to update when a newer build of Froyo (or even Gingerbread) comes out?
[Nook Color Android Development] rookie1:
Yes, this should work with 1.1.0. I'm thinking of creating an uninstall script. If you want to do it manually, basically you need to restore u-boot.bin, delete partition 9 and 10, then resize partition 8 back to original size.

To update a new build of Froyo, you will need to overwrite the system and data partition. As well as modify init.rc to mount the right partition to /system and /data. This is a bit tricky because it means you need to repack the ramdisk.
[Nook Color Android Development] rookie1:
Just reboot and see whether your media partition is intact. If you did not lose any data from media, you can run the script again. If your /media is empty, you will need to restore your data from /sdcard/media_backup.tar.gz, before re-run the script.

I'm surprised the script is not able to umount /media. Do you have anything else running in the background that uses /media?
[Nook Color Android Development] pezhore:
I'm in the process of getting my data backed up just in case it doesn't come back... if the /media is empty, and that tar file is missing - any suggestions? Start over from scratch?
[Nook Color Android Development] rookie1:
I hope that situation does not happen. The script aborts if /media backup is not successful. You should have a /sdcard/media_backup.tar.gz once the script has run. But it's always prudent to have your own backup.

/media is not necessary for either eclair (other than B&N apps using /media) or froyo to function.
[Nook Color Android Development] pezhore:
That's good to hear. My backups are nearly done, so I'll try rebooting afterwards.

Quick clarification - does the dualboot folder go on the microsd or on the internal drive?
[Nook Color Android Development] rookie1:
Put the dualboot folder on your SD. It's easier that way.
[Nook Color Android Development] pezhore:
Awesome! looks like the script is working after a reboot - I'm thinking that something may have still been mounted - perhaps the nook didn't realize that I had umounted from linux.

I'll update once the script completes to let you know the result.
[Nook Color Android Development] jasoraso:
Could this script be run while the nc is booted into cwr? Would that help make sure that nothing else is running?
[Nook Color Android Development] trentmaynard:
Question

I'm sorry if this sounds like a stupid question, but is this script only for linux? is there a way to get this to work on windows? cause any time I try typing adb shell into command prompt I get this message 'adb' is not recognized as in internal or external command, operable program or batch file.
[Nook Color Android Development] pezhore:
Works great! I think the key for me was I unplugged the NC after I umounted, then locked the nook and plugged the cable back in - this made sure the drives didn't automount.
[Nook Color Android Development] jasoraso:
I recently installed the update to 1.1 using CWR and the .zip file available here on XDA; now I wanted to try this script.

After several attempts, I finally got USB debugging to stay on; and I get into the ADB shell from my windows 7 machine; I have root # access; but when I attempt to run the script after cd'ing to /sdcard/dualboot (where I can see the script) ... I get an error: "busybox: permission denied"

I've tried reinstalling busybox from from both TiBu; resetting permissions from CWR; and installed a busybox installer app from the Market

Any suggestions?

EDIT: I ininstalled TiBu; and reinstalled; then had it reinstall busybox ... script is running and my fingers are crossed ...

2nd edit: while script is running, NC just gave me an error: Restart required: Your Nookcolor encountered a problem that requires a system restart. If this problem persists, please contact Customer Service. OK.

I'm not going to hit "OK: for a little > don't wnat it automatically reboot in the middle of the script

3rd EDIT: Done # ****woot****

I got another error on NC during the script about Palmary Weather not responding - I wonder I had apps running that were trying to access cache or data or sdcard or something during the script processing ...

and I kept getting email notifications - probably should turn wifi off during this process to just minimize changes on the NC while the script is running
[Nook Color Android Development] xboxexpert:
This script worked perfect for me. No problems what so ever. I was on 1.0.1

I am now wondering how I would go about updating Froyo in the future and also why is my SD Card not being mounted to my PC when I plug it in? ADB works but I can not see my SD card on the computer once plugged in.
[Nook Color Android Development] jasoraso:
Anyone have any tips on how to get the 1.1 kernel installed for Froyo on the emmc dual boot?
[Nook Color Android Development] xboxexpert:
Does your SD card mount when plugged into the PC? I cant get it to mount so I can drop files over to it through the computer.
[Nook Color Android Development] jasoraso:
Yeah, my SD card is mounting fine - I slide the notifications down, and select the option there for USB storage ... then it pops up on my win7 box ...

I am used to flashing the kernel using CWR - but I think if I use that, it will flash to the 2.1 Eclair partition -
[Nook Color Android Development] bedoig:
Hi everyone!

Just got my NC on Wednesday. Very exciting!

Question - is it possible to run this from terminal emulator on the device, or do the commands have to be entered through ADB shell?
[Nook Color Android Development] jasoraso:
I suspect it would be possible to run from the terminal; but I would wait for confirmation from th OP.
[Nook Color Android Development] jasoraso:
I opened up the script to install and saw how the OP was installing Froyo:

I renamed the 1.1 kernel to uFImg and then mounted the first partition and replaced the uFImg that was there!

running great!!
[Nook Color Android Development] bedoig:
Just curious because I was at work and don't have ADB. I'll probably try one of the bootable SD images first anyway. Thanks!
[Nook Color Android Development] corwinmortac:
I ran this from a terminal and its working fine. Good Job OP this is greatness....

Swyped from a Gingerbread CM7 EVO using the Xda app
[Nook Color Android Development] Novarider:
Can this be used if I already dd Nookie Froyo to my emmc?
[Nook Color Android Development] sudermatt:
Do I have to partition my card at all? or can my standard NC SD Card work?

Can we run this from the NC terminal?

This looks really easy.
[Nook Color Android Development] sudermatt:
Tried to "go for it" out of terminal emulator with an SD card that wasn't specifically prepared with partitions...just the one I've always used.

No go...lot's of errors...
[Nook Color Android Development] loganthered:
This is very sexy indeed. You sir, have won yourself one internets.
[Nook Color Android Development] NikolaiT:
The gapps and market aren't included in this package, could you upload one that includes them? I cannot get them to install manually.
[Nook Color Android Development] ChrisJ951:
Guide for overclocking froyo from internal here:

http://xdaforums.com/showthread.php?p=10986513#post10986513

Also thanks again for this dual boot script :D
[Nook Color Android Development] mtl171:
Nice work but got a strange output after installing

>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Create working directory
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Back up /media to sdcard
>>>>>>>>>>>>>>>>>>>>
tar: removing leading '/' from member names
[Nook Color Android Development] Divine_Madcat:
So.. is there an easy way to unpartion the /media section? After running the script, my eclair build just keeps booting up to the screen, but as soon as i unlock, it says it has an error and must reboot. So, basically, this hosed my nook's install (1.1.0).. yay.

Since it isn't working, can you give some guide on how to get my /media back to full go?
[Nook Color Android Development] ChrisJ951:
I'm unsure of how to repartition /media but restoring to the original firmware works (i tested this once after messing some stuff up by accident) and if you want to dual boot you probably have to downgrade to 1.0.1 until this method is updated
[Nook Color Android Development] Divine_Madcat:
Well, either way, i should be ok, since i did a nandroid of my 1.01 before running the 1.1 update..
[Nook Color Android Development] Divine_Madcat:
WEll, did a nandroid restore, updated to 1.1, and still getting the same error:

""Your NookColor ecountered a problem that requires a system restart" Doesn't let me do anything but reboot...... yay.
[Nook Color Android Development] Divine_Madcat:
WEll, did a nandroid restore, updated to 1.1, and still getting the same error:

""Your NookColor ecountered a problem that requires a system restart" Doesn't let me do anything but reboot...... yay.

WEll, a nandroid back to just 1.01 seems like it works, so maybe i am not totally hosed...
[Nook Color Android Development] mtl171:
Lol. same thing happened to me right afterwards. you have to start fresh by booting into clockwork and restoring your NC from a factory image.

http://xdaforums.com/showthread.php?t=914690&highlight=cwm

its a pain but its the only thing that works. the 8 boot fail should also work but didn't work for me.

You MUST also format /data and /system via clockwork. hope that helps.
[Nook Color Android Development] Divine_Madcat:
Thanks for the advice. Curious though - why does the 1.1.0_r2 fail? Will i need to format everything, restore my nandroid, and then update?
[Nook Color Android Development] ChrisJ951:
I dont know how nandroid does restores (im guessing it does it files, not img's) but here is the guide I used

http://xdaforums.com/showthread.php?t=919353
[Nook Color Android Development] Divine_Madcat:
Actually, a full nandroid is 4 .img files, one each for boot, cache, data and system.

I think to be safe, i will make sure my updater is good, and try it again. If my 1.01 image is goo, it has to be something else.

So, i think part of the problem is this: in my current 1.01 build, my "Available Storage" lists 0.00B of 0.00B.... i am guess my /media i really bhorked....
[Nook Color Android Development] Divine_Madcat:
So, i have fixed my issue, and here is what it was offically.

Somehow, the script did not correctly recreate the /media partition. For whatever reason, 1.01 can run correctly with no media partition, but 1.10 does NOT, and will constantly reboot you. 1.01 reported 0.00B or 0.00B for media, showing it was not working well.

So, to fix this, i followed pieces from the orignal SH script, to repair my media partition:

adb shell

cd /sdcard/dualboot

mkdir /data/dualboottmp

busybox tar zxf dual-boot-files.tar.gz -C /data/dualboottmp

umount /media

/data/dualboottmp/parted -s /dev/block/mmcblk0 rm 8

/data/dualboottmp/parted -s /dev/block/mmcblk0 rm 8 //took two goes to get rid of it

/data/dualboottmp/parted -s /dev/block/mmcblk0 rm 9

/data/dualboottmp/parted -s /dev/block/mmcblk0 rm 9

/data/dualboottmp/parted -s /dev/block/mmcblk0 rm 10

/data/dualboottmp/parted -s /dev/block/mmcblk0 rm 10

/data/dualboottmp/parted -s /dev/block/mmcblk0 mkpart logical fat32 2312 7691

newfs_msdos -F 32 -L media /dev/block/mmcblk0p8

mount -t vfat /dev/block/mmcblk0p8 /media

reboot

Once the system was up, i restored the contents of the media backup tar to the now correctly mounting /media folder (and it would show up in windows). After that, updating to the 1.10_r2 build work without error, and life is good again.

It was a fun try, but led to nothing...
[Nook Color Android Development] Fishfoot:
Hello,

Thanks for the cool script but after running it I can't seem to get froyo to boot. If I press the home button on reboot I get the android loading screen but it never boots.

Any advice? I thought about possibly DD ing the working froyo emmc images onto the partitions you created with the scripts.

Sent from my Rooted Nook
[Nook Color Android Development] isolated_epidemic:
How do I undo this? I need to get back to stock. I have tried dd'ing the stock boot and system images to their respective locations, and still when i get back into Eclair its showing that I only have 3.72gb

I have also tried using the Monster Root Pack 0.5 and did all the wipes and tried installing 1.01 fresh and still 3.72gb available. If i'm not mistaken my /media partition is still split from trying this. I assume its a simple step that I'm overlooking.

I have literally spent all day trying all of the different Return to Stock threads and all have yielded the same results. Can someone point me in the right direction?
[Nook Color Android Development] rookie1:
To go back to stock configuration, create a text file in your /sdcard/dualboot folder. Let's call it reformat-media.sh. You should still have dual-boot-files.tar.gz in the same folder. Then in your adb shell, do the following,

cd /sdcard/dualboot

busybox sh reformat-media.sh

Note this script does not do backup for you. It will ask you whether you have done your back up, and give you a choice to Ctrl-C to abort the script. If you chose to continue, it will delete /media as well as froyo's system and data partition, then recreate /media to use all available space.

Once this is done, you can restore back your /media backup.

Content of reformat-media.sh

echo "This will delete /media, as well as Froyo /system and /data partition."
echo "Have you done your backup????"
echo "If not, press Ctrl-C now to abort this script and do you backup."
read -p "If you are sure, press ENTER to continue reformating /media" tmpvar
mkdir /data/dualboottmp
busybox tar zxf dual-boot-files.tar.gz -C /data/dualboottmp
chmod 766 /data/dualboottmp/parted
umount /media
/data/dualboottmp/parted -s /dev/block/mmcblk0 rm 10
/data/dualboottmp/parted -s /dev/block/mmcblk0 rm 9
/data/dualboottmp/parted -s /dev/block/mmcblk0 rm 8
/data/dualboottmp/parted -s /dev/block/mmcblk0 mkpart logical fat32 2311 7691
newfs_msdos -F 32 -L media /dev/block/mmcblk0p8
mount -t vfat /dev/block/mmcblk0p8 /media
busybox rm -rf /data/dualboottmp
echo "/media partition re-created."
echo "You can restore your data in /media now"
[Nook Color Android Development] candre23:
I'm getting the same result. The script is crashing/quitting at the same point. Any resolution for this?
[Nook Color Android Development] rookie1:
Seems /media backup failed. Can you run

busybox tar zcf /sdcard/media_backup.tar.gz /media

at your adb shell prompt, and see whether it's successful? If it's successful, you should have a file named media_backup.tar.gz on your sd card.
[Nook Color Android Development] candre23:
I ran the command and it did make the backup file (57.4MB), but the output was identical to when I ran the script "tar: removing leading '/' from member names". After that, it just sat there and never gave me a prompt.

EDIT - The backup tar.gz is garbage. Despite it's file size, it only contains a couple files and winrar gives an "unexpected end of archive" error when opened.
[Nook Color Android Development] rookie1:
Might be a stupid question, do you have enough space on your sd card for the backup?
[Nook Color Android Development] newsted33:
The script didn't work for me for some reason (probably a notepad issue) but typing it all out by hand did. Thanks a lot.
[Nook Color Android Development] candre23:
Not a stupid question, I thought of it myself. I'm only using a 2gb card, but I have over 800mb free. Should be plenty, right?
[Nook Color Android Development] x-ravin:
Did this last night with no issue. Pretty awesome scripting. I used a 512mb card so you dont need much. Thanks OP.

Sent from Nook Color.