Related
Now that we have our own forum, time to stake a claim.
Nooter is an image that's loaded to a microSD card that can boot the Nook Color into a basic Linux environment. It automatically enables adb and turns off ro.secure on bootup, so no interaction is necessary to get root. Nooter sets up the USB port as a USB ethernet device (RNDIS) compatible with most modern OSes to allow SSH logins. From there the ROM can be dumped, partitions mounted and edited, and (hopefully someday) bricks debricked.
Get it here: Nooter 0.2.
Up-to-date directions at http://nookdevs.com/NookColor_Rooting
Changes
0.1
first release
0.2
replaced composite CDC USB device with RNDIS. This should "just work" under most XP and later Windows
add ext2tools, dosfstools, util-linux for manual flash disk reformatting
Thanks to [mbm] for the root procedure, kernel config, and not sleeping; KCHASE731 for dissecting his NC for vital clues about the hardware config; and the rest of #nookdevs
If we've already rooted with Nooter v.01, and are using windows, is there any harm in rooting again with Nooter v.02?
Oh, and THANKS!
jasoraso said:
If we've already rooted with Nooter v.01, and are using windows, is there any harm in rooting again with Nooter v.02?
Oh, and THANKS!
Click to expand...
Click to collapse
Both versions will write the file to turn on adb every time they boot, but will only patch the ramdisk if it hasn't been done already. There's no difference in the rooting procedure from 0.1 and 0.2, just the tools for people wanting to get a shell outside of Android.
Not working for me
I must have done something wrong, but my NC just boots like normal, it never boots off the microSD card.
I am using Ubuntu Maverik.
I install the SD card while the nook is powered down and then I plug the USB cable to the computer, which automatically starts the NC, but it just boots in the OS like normal. after the NC boots, it will connect the sd card and flash memory like normal, and show the nooter02 sd contents.
Any suggestions?
EDIT: OK, figured it out, I used mmcblk0p1, instread of mmcblk0
Yesss !delivered
Hi
I receive my NC today !. It's great nooter 0.2 is awesome for two points :
it gives root access and ...
It demonstrates that the overclock is possible, because the uImage/u-boot force the clock to 1Ghz and it's working well
Code:
cat cpuinfo_cur_freq
1000000
About 997 bogomips
Cheers
Occip
Woot! Thanks for the revised tool to root from the Windoze world!
I'll have to give this a try when I get home...
So, if we used Nooter0.2, we are running 1Ghz?
occip said:
It demonstrates that the overclock is possible, because the uImage/u-boot force the clock to 1Ghz and it's working well
Click to expand...
Click to collapse
I imagine that only while running off SDCard
occip said:
Hi
I receive my NC today !. It's great nooter 0.2 is awesome for two points :
it gives root access and ...
It demonstrates that the overclock is possible, because the uImage/u-boot force the clock to 1Ghz and it's working well
Code:
cat cpuinfo_cur_freq
1000000
About 997 bogomips
Cheers
Occip
Click to expand...
Click to collapse
Heh, I never even checked! I used the config for the Zoom3 sdk (OMAP3630 like the DX) for x-loader and u-boot and I guess that's where that gets set.
We should have BN's sources for both soon enough, and it will be a very easy change to the stock bootloader to get 1GHz in Android.
ryoojin83 said:
I must have done something wrong, but my NC just boots like normal, it never boots off the microSD card.
I am using Ubuntu Maverik.
I install the SD card while the nook is powered down and then I plug the USB cable to the computer, which automatically starts the NC, but it just boots in the OS like normal. after the NC boots, it will connect the sd card and flash memory like normal, and show the nooter02 sd contents.
Any suggestions?
EDIT: OK, figured it out, I used mmcblk0p1, instread of mmcblk0
Click to expand...
Click to collapse
Um, help? I'm following the directions and I'm familiar with the mmcblk0 from my multiple phones, but I don't understand how that applies here. I'm using Maverick and get the same thing you do...it just boots normally.
Thanks
weiln12 said:
Um, help? I'm following the directions and I'm familiar with the mmcblk0 from my multiple phones, but I don't understand how that applies here. I'm using Maverick and get the same thing you do...it just boots normally.
Thanks
Click to expand...
Click to collapse
are you using a dedicated microsd reader or your phone or the nook itself to flash the image?
I just confirmed that nooter broke the NC's in-store features, such as read any book for up to 1 hour per day. Any chance of looking into this?
daveknights said:
I just confirmed that nooter broke the NC's in-store features, such as read any book for up to 1 hour per day. Any chance of looking into this?
Click to expand...
Click to collapse
All Nooter does is set a flag to turn on adbd and turn off the root lockdown flag. Either the BN app checks that root or adbd aren't enabled, or the ramdisk is signed and the process of unpacking, changing the security flag, and repacking the ramdisk screws up the signature. You could try copying the ramdisk.img from partition 3 over uRamdisk in partition 1, which would unroot but leave adbd running, and see if that re-enables the store features. Of course, you'd have no root, but if you just want basic apps then that might be enough.
I am using windows vista 32 sp2 and could not get root. help question. In the windows USB ADB instructions with the copy and paste part
;B & N Nook Color ; %SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002 %CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
why do i get
this bottom part stuck to it
Read more: http://nookdevs.com/NookColor_USB_ADB#ixzz17adJ0qwv
Under Creative Commons License: Attribution Non-Commercial Share Alike
along with my copy and paste. anyone know where this last line come from.
Also about this part of the process with rooting
Once the devices show up, wait another 30 seconds while the script makes the changes to enable ADB. (ADB will be available after you reboot into Android)
is it 30 sec or 5 min's I have read hear on the XDA boards it is 5 mins to enable ADB. It is hard to tell cause nothing really happens.
Once rooted is there a firmware (#) difference i can check to see if it worked
This is the 2nd time i am posting this as before i got no answers
I've been trying this for up to 2 mins, both with Windows and Mac and I'm kinda sure the root isn't working for me. I just received the NC, so is it possible B&N updated over the weekend in response to the news?
Is there a way to check version of firmware/bootloader/etc?
EDIT: Ok got it working amazingly. I uninstalled the driver (Android ADB Interface) and checked the delete files option. When I rescanned it found it and installed the correct drivers under W7.
pokey9000, is the uRamdisk.bak file on partition 1 something nooter created or is that a how the stock NC comes? and if nooter creates it, would deleting uRamdisk and renaming uRamdisk.bak to uRamdisk unroot the NC just like copying the ramdisk.img file over from partition 3?
do you have any documentation on what else (specific files) nooter modifies?
would it be possible to unroot a NC without doing a factory reset?
ruze said:
EDIT: Ok got it working amazingly. I uninstalled the driver (Android ADB Interface) and checked the delete files option. When I rescanned it found it and installed the correct drivers under W7.
Click to expand...
Click to collapse
I had to do the same exact procedure to get a Win7 machine to talk with my NC over ADB.
jsmith.nook said:
pokey9000, is the uRamdisk.bak file on partition 1 something nooter created or is that a how the stock NC comes? and if nooter creates it, would deleting uRamdisk and renaming uRamdisk.bak to uRamdisk unroot the NC just like copying the ramdisk.img file over from partition 3?
do you have any documentation on what else (specific files) nooter modifies?
would it be possible to unroot a NC without doing a factory reset?
Click to expand...
Click to collapse
Nooter modifies the default.prop to allow root in uRamdisk after copying the original to uRamdisk.bak. Then it creates /data/property/persist.service.adb.enable to turn on adb. So copying uRamdisk.bak to uRamdisk and deleting /data/property/persist.service.adb.enable will put things back to normal. But you'll still have app specific content in /data/app, /data/dalvik.cache, /data/data, anything you do to /system, etc.
pokey9000 said:
Nooter modifies the default.prop to allow root in uRamdisk after copying the original to uRamdisk.bak. Then it creates /data/property/persist.service.adb.enable to turn on adb.
Click to expand...
Click to collapse
Would modifying default.prop to enable adb there, rather than create the property file, also work? Or does that have no effect?
Thank you for this great tool. Your work is greatly appreciated.
[This method is now obsolete. I've created flashable zips for setting up dual boot. And flashable dual boot Nookie Froyo and Honeycomb ROMs. See my other post.]
I've successfully dual boot B&N stock eclair and nookie froyo, both from internal eMMC. Here are the steps to use my script,
1. Download attached dualboot.zip. Create a folder called 'dualboot' on your NC's SD card. Unzip dualboot.zip into this folder.
2. Download Nookie Froyo 5.9 base image from http://edencomputing.com/nookcolor/nookie-froyo-base-0.5.9.tar.gz and copy into the same 'dualboot' folder on SD.
3. Check you have these 3 files in SD's 'dualboot' folder,
dual-boot-files.tar.gz
dual-boot.sh
nookie-froyo-base-0.5.9.tar.gz
4. Make sure /sdcard and /media are mounted in NC. If they are visible on your host PC, umount if you are running Linux, or 'safely remove' if you are on Windows, or 'eject' in Mac.
5. From your host PC, run 'adb shell' to go into your NC.
6. At adb shell, run the following commands.
cd /sdcard/dualboot
busybox sh dual-boot.sh
7. After a few minutes and a lot of messages scrolling by, you should see a message says ">>>>>>>>>>>>>>>>>>>>Done". At this point, you can reboot the NC. Normal boot will go to stock eclair. Hold 'n' button during boot to go to froyo.
p.s. I've also modified the recovery boot keycombo (stock is Power + n) in u-boot.bin. Hold both Vol+ and Vol- during boot to go into recovery. Keep holding them till you are in recovery, no need to worry about how long to hold.
If you want to remove dual boot
1. follow steps in this post http://forum.xda-developers.com/showpost.php?p=11001928&postcount=66 to restore media partition to stock configuration. Note you need to make your own backup of media partition before trying this.
2. follow steps in this post http://forum.xda-developers.com/showpost.php?p=11014734&postcount=88 to restore stock u-boot.
Original steps kept below if you are interested to know what the script does
Here is how I have done it,
1. In stock rom partition 8 of internal eMMC is mounted as media. We can use a partition tool to shrink this partition to make enough room to create 2 more partitions, 1 for froyo system partition (mmcblk0p9) and 1 for froyo data partition (mmcblk0p10). The partition tool I used is GNU parted which comes with Koush's clockwork mod. You can download a pre-compiled copy from his git tree. It can be run on the NC itself.
2. Copy all files from nookie froyo's system partition into mmcblk0p9, and data into mmcblk0p10.
2. Copy nookie froyo's uImage into mmcblk0p1. The file name should be changed to uFImg, so that it can co-exist with stock eclair's uImage on the same partition.
3. Modify nookie froyo's init.rc in the ramdisk, to mount mmcblk0p9 as system, and mmcblk0p10 as data. Pack the ramdisk image, and copy into mmcblk0p1 as uFRam. Again we use a different name so it can co-exist with stock eclair's uRamdisk.
4. I've modified B&N's u-boot tool to detect whether 'N' button is pressed during boot. If it's pressed, boot using uFImg and uFRam. Otherwise boot using stock uImage and uRamdisk. Attached is my modified u-boot. Copy the u-boot.bin into mmcblk0p1 to overwrite stock u-boot.bin.
With this setup, if no button is touched during boot, NC will boot into stock eclair. If you hold 'N' button during boot, it will boot into nookie froyo.
One problem I've found is with the modified partition layout, when booting into stock eclair, media partition does not get automatically mounted. But I'm able to manually mount it.
Played around with the partition layout a bit. It seems if media (partition 8) is at the end of eMMC, it will be automounted in stock eclair. So my final partition layout looks like this,
Code:
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7691MB 7230MB extended
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext3
7 1941MB 2311MB 370MB logical ext3
9 2311MB 2681MB 370MB logical ext2
10 2681MB 3692MB 1011MB logical ext3
8 3692MB 7691MB 3999MB logical fat32 lba
< standard disclaimers - I'm not responsible for whatever damage you did to your NC >
Very nice work. Will have a look.
Thanks.
Nice work. However, I have a concern. As we may have experienced, NC would sometimes randomly reboot itself. So there will be chances that first I boot my NC with nookie froyo, then it reboot and become 2.1 again...
Until a permanent solution is found, this dual boot will not be as effective as it should...
lazinase said:
Nice work. However, I have a concern. As we may have experienced, NC would sometimes randomly reboot itself. So there will be chances that first I boot my NC with nookie froyo, then it reboot and become 2.1 again...
Until a permanent solution is found, this dual boot will not be as effective as it should...
Click to expand...
Click to collapse
I think the problem is over-exaggerated. Since changing the stock governor to ondemand, i have never had a 2.1 reset. Additionally, i have NEVER had a NF (2.2) reset.
Anyway, thanks for the guide OP.. i am actually itching to do this myself...
Divine_Madcat said:
I think the problem is over-exaggerated. Since changing the stock governor to ondemand, i have never had a 2.1 reset. Additionally, i have NEVER had a NF (2.2) reset.
Anyway, thanks for the guide OP.. i am actually itching to do this myself...
Click to expand...
Click to collapse
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.
Does this affect Clockwork Recovery at all?
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
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
Another thread claimed that the reboots people were having were the Java run time service rebooting, not an actual OS reboot.
Sent from my Nexus One using XDA App
BugmanXDA said:
Another thread claimed that the reboots people were having were the Java run time service rebooting, not an actual OS reboot.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
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.
BugsBunny891 said:
I agree. the random reboot has only happened to me while on eclair, nookie froyo hasn't given me a single one.
Click to expand...
Click to collapse
BugmanXDA said:
Another thread claimed that the reboots people were having were the Java run time service rebooting, not an actual OS reboot.
Click to expand...
Click to collapse
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!
rookie1 said:
I've successfully dual boot B&N stock eclair and nookie froyo, both from internal eMMC. Here is how I have done it,
1. In stock rom partition 8 of internal eMMC is mounted as media. We can use a partition tool to shrink this partition to make enough room to create 2 more partitions, 1 for froyo system partition (mmcblk0p9) and 1 for froyo data partition (mmcblk0p10). The partition tool I used is GNU parted which comes with Koush's clockwork mod. You can download a pre-compiled copy from his git tree. It can be run on the NC itself.
2. Copy all files from nookie froyo's system partition into mmcblk0p9, and data into mmcblk0p10.
2. Copy nookie froyo's uImage into mmcblk0p1. The file name should be changed to uFImg, so that it can co-exist with stock eclair's uImage on the same partition.
3. Modify nookie froyo's init.rc in the ramdisk, to mount mmcblk0p9 as system, and mmcblk0p10 as data. Pack the ramdisk image, and copy into mmcblk0p1 as uFRam. Again we use a different name so it can co-exist with stock eclair's uRamdisk.
4. I've modified B&N's u-boot tool to detect whether 'N' button is pressed during boot. If it's pressed, boot using uFImg and uFRam. Otherwise boot using stock uImage and uRamdisk. Attached is my modified u-boot. Copy the u-boot.bin into mmcblk0p1 to overwrite stock u-boot.bin.
With this setup, if no button is touched during boot, NC will boot into stock eclair. If you hold 'N' button during boot, it will boot into nookie froyo.
One problem I've found is with the modified partition layout, when booting into stock eclair, media partition does not get automatically mounted. But I'm able to manually mount it.
< standard disclaimers - I'm not responsible for whatever damage you did to your NC >
Click to expand...
Click to collapse
Excellent work. How large did you make the mmcblk0p9 and 0p10 partitions and could you provde a link to android gparted? Thanks much.
runhopskipjump said:
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!
Click to expand...
Click to collapse
^This.
solution worked for me as well.
BugmanXDA said:
Another thread claimed that the reboots people were having were the Java run time service rebooting, not an actual OS reboot.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
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.
If anyone is interested, I've managed to get NF on eMMC with mounting uSD.
Thought you should know.
Sam
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!
I'm creating a script to do the installation. Will update the 1st post once I tested it.
That would be great!
Sent from my LogicPD Zoom2 using XDA App
rookie1 said:
I'm creating a script to do the installation. Will update the 1st post once I tested it.
Click to expand...
Click to collapse
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
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.
From mobileread I found this amazing post:
the Nook Tablet is still bootable from SD. The rep said that while they think only 3% of sales of the NC go to people who want to root it, they are still sales they wouldnt otherwise have. And they aren't interested in removing the ability to root for those who want to do that. I was pleasantly surprised how ok they are with rooting. Plus, he said they have to keep the boot from SD option. When someone brings a messed up device into a B&N store, they can wipe the device clean and restore it to its original condition by booting the system from an SD card (by using the OS on the card to restore the system on the device).
Click to expand...
Click to collapse
OMG the monkey hitting my head XD
Edit - Not yet found the way to bypass bootloader.
Oh man, I'm really starting to like B&N management.
Smart, smart, smart.
Stuff like this is why I still bought B&N books on my rooted nook.
Perhaps wishful thinking on my part, but I thought I could take a bootable CM7 uSD from my NC and put it in the NT. No dice. It just boots up into the Nook OS. The same card works on my NC.
yeah i tested it out myself today with no luck. when i get mine i'm gonna try an install just to see what happens. maybe you need to run the installer on the device you want? i know that doesn't make sense but i'll have mine tomorrow so if it works i'll post back here. but the boot from sd was invaluable when i deleted the boot file on my nc. and i've seen people get sold on the tablet based on how easy the nc was to root and tinker with. but the stock experience is nice enough that i won't NEED to root it right away.
smatticus said:
yeah i tested it out myself today with no luck. when i get mine i'm gonna try an install just to see what happens. maybe you need to run the installer on the device you want? i know that doesn't make sense but i'll have mine tomorrow so if it works i'll post back here. but the boot from sd was invaluable when i deleted the boot file on my nc. and i've seen people get sold on the tablet based on how easy the nc was to root and tinker with. but the stock experience is nice enough that i won't NEED to root it right away.
Click to expand...
Click to collapse
Unfortunately it wouldn't even run the installer. I created a fresh bootable uSD using the image from here:
http://forum.xda-developers.com/showthread.php?t=1000957
Then dumped the latest CM7 NC nightly on it, put it in the NT, and turned it on. The NT just went straight into the Nook OS.
Just to make sure nothing was wrong with it, I put it in my NC. The installer started up, CM7 installed, and after a reboot I was in a fresh install of CM7. Next I took the uSD, put it in the NT, and restarted it. Still didn't work.
lionclaw said:
Unfortunately it wouldn't even run the installer. I created a fresh bootable uSD using the image from here:
http://forum.xda-developers.com/showthread.php?t=1000957
Then dumped the latest CM7 NC nightly on it, put it in the NT, and turned it on. The NT just went straight into the Nook OS.
Just to make sure nothing was wrong with it, I put it in my NC. The installer started up, CM7 installed, and after a reboot I was in a fresh install of CM7. Next I took the uSD, put it in the NT, and restarted it. Still didn't work.
Click to expand...
Click to collapse
This method can't simple directly used with NT, we need edit something like autonooter or supernooter to work with the new hardware.
Btw try the supernooter file please.http://forum.xda-developers.com/showthread.php?t=871940
lionclaw said:
Perhaps wishful thinking on my part, but I thought I could take a bootable CM7 uSD from my NC and put it in the NT. No dice. It just boots up into the Nook OS. The same card works on my NC.
Click to expand...
Click to collapse
smatticus said:
yeah i tested it out myself today with no luck. when i get mine i'm gonna try an install just to see what happens. maybe you need to run the installer on the device you want? i know that doesn't make sense but i'll have mine tomorrow so if it works i'll post back here. but the boot from sd was invaluable when i deleted the boot file on my nc. and i've seen people get sold on the tablet based on how easy the nc was to root and tinker with. but the stock experience is nice enough that i won't NEED to root it right away.
Click to expand...
Click to collapse
This won't work because each version of CM is tailored to work for the specific device in question, based on the hardware that device has. The NC does not have the same hardware as the NT, therefore you can't use the version of CM built for the NC on the NT. CM has drivers built-in in order to communicate with the device in question, and the drivers for communication with the NC cannot be used to communicate with dissimilar hardware on the NT.
We will just have to wait until the CM devs rebuild CM to include the drivers for the NT.
Solidsnake726 said:
Stuff like this is why I still bought B&N books on my rooted nook.
Click to expand...
Click to collapse
+1. They've bought my loyalty. The NT also just shot straight to the top of my Christmas list as a result of this.
I just got ahold of my Nook Tablet today. I can't wait until the developers get going on this. I definitely will still support B & N for allowing this to be done.
Honestly, B&N is way better off letting users hack away at it. It makes it a hot sales item, resulting in free advertising and better company image (good for shareholder confidence). Also, hopefully they learned from Sony on how NOT to provide an "open" system--giving freedom then taking it away.
It appears that it may only boot signed code..
also, I'm not able to open build.prop on the device using a file manager or when I transfer it to my local machine..
Hopefully some devs will pick it up soon and let us know where we stand
I don't have the machine yet, but why doesn't the superoneclick program work for the Nook tablet as well? Has anyone tried?
jamus28 said:
I don't have the machine yet, but why doesn't the superoneclick program work for the Nook tablet as well? Has anyone tried?
Click to expand...
Click to collapse
it don't work.
Don't panic people. Just because a bootable card does not boot up the Tablet does not mean it will not boot from a card. A whole new CWR will need to be created for the tablet.
Even without root right now, most everything is available.
Obviously we are still missing the android market, but almost all other gapps are currently working, home replacements as well.
I know this doesn't work as well as CM, but it is definitely a huge improvement over what we had yesterday morning.
diamond_lover said:
From mobileread I found this amazing post:
OMG the monkey hitting my head XD
Edit - Not yet found the way to bypass bootloader.
Click to expand...
Click to collapse
The problem with your quoted text: There's a difference between "booting from SD" and "booting ANYTHING from SD".
B&N can allow the former in order to permit unbricks at the store (signed B&N images) without allowing the latter (unsigned images).
need to look at the xft/mlo boot file on sdcard
hello. I think that the NT might boot from SD but is not seeing the right MLO file on the card. If I remember from the OMAP 3 boot sequence, the MLO has to be put on the sdcard first. The reason is that the MLO is the very low level boot code that get into the internal SRAM of the chip. TI provided a tool to convert the xft image to an MLO file and added some kind of magic number so that the chip accepted it as valid for execution. You do not want to use the NC MLO on a NT. that might kill the OMAP. The first thing to do is get the OMAP4 XFT source code and covert it to an MLO using the OMAP 4 TOOL and put it on an sdcard on the first sector to see if the NT will take it.
Just my 2 cents
Fifcic said:
hello. I think that the NT might boot from SD but is not seeing the right MLO file on the card. If I remember from the OMAP 3 boot sequence, the MLO has to be put on the sdcard first. The reason is that the MLO is the very low level boot code that get into the internal SRAM of the chip. TI provided a tool to convert the xft image to an MLO file and added some kind of magic number so that the chip accepted it as valid for execution. You do not want to use the NC MLO on a NT. that might kill the OMAP. The first thing to do is get the OMAP4 XFT source code and covert it to an MLO using the OMAP 4 TOOL and put it on an sdcard on the first sector to see if the NT will take it.
Just my 2 cents
Click to expand...
Click to collapse
If this is true, BN needs to follow Amazon and release the source code for NT.
discothan said:
If this is true, BN needs to follow Amazon and release the source code for NT.
Click to expand...
Click to collapse
I thought they did, there is a link in the NT developer forum I believe.
I now have proof that the Nook Tablet is efuse locked and bootloaders signed. We can only boot signed bootloaders, kernels, and ramdisks from microSD.
Don't buy this if you expect any real development to happen on it. The only possible way is through kexec, and that's a lot of trouble to go through considering all the other tablet options.
For what it's worth, the u-boot in the recently posted update image from the Kindle Fire does not appear to have the signed header that the one on the NT has.
Things I learned in the process:
-USB boot is enabled, as is SD boot
-I can boot from a microSD if I format it the same as for Nook Color (modified CHS, fat on p1) and copy the MLO, u-boot, and boot.img renamed to flashing_boot.img
-There is a serial port inside that will let you at the u-boot console and a shell after the OS boots
-x-loader is signed. A known-good x-loader on microsd will not even execute, and the next item in the boot list checked (emmc)
-u-boot is signed. I know this because a known-good u-boot from Pandaboard that should be close enough to boot causes x-loader to take the code path where the secure ROM call with a pointer to the image returns nonzero
-kernel and ramdisk are signed individually in the boot.img. I can modify a byte in the boot.img on the microsd that's in the middle of the kernel or the ramdisk section and u-boot will fail the same exact call that x-loader uses to validate u-boot, but this time emitting a message complaining that the image is corrupt
-Comparing the first part of u-boot grabbed from the NC, NT, and the KF, shows that the signature that's at address 0 of the KF and NC versions is seen about 300 bytes into the NT version, with some unknown junk above. I assume that's the signature, and that the call to the secure ROM returns the image pointer (which is passed by reference, a good clue) plus the size of the header.
Wait.. Nook Touch or Nook Tablet?
DarkDvr said:
Wait.. Nook Touch or Nook Tablet?
Click to expand...
Click to collapse
Tablet. I blame BN's marketing.
what about this?
http://code.google.com/p/pandroid/downloads/detail?name=u-boot.bin&can=2&q=
That's certainly... interesting. Definitely not the direction I assumed they would go given those quotes from the B&N guys that have been thrown around.
I'll hold off any true disappointment until more people have had more time to poke at this thing. Nothing against you pokey, and thanks for your investigations so far.
diamond_lover said:
what about this?
http://code.google.com/p/pandroid/downloads/detail?name=u-boot.bin&can=2&q=
Click to expand...
Click to collapse
Close enough to the one for Pandaboard minimal Linux, which I tried.
pokey9000 said:
Close enough to the one for Pandaboard minimal Linux, which I tried.
Click to expand...
Click to collapse
I hope we can find a workaround, there will be a way to do that, because they installed android in some way.
BTW, have you tried a bootable SD card? I think it's the right path to follow.
EDIT: I see you can't boot by sd card.. what about if you try some file from Nook Color?
pokey9000: what kind of a response you can get when trying to boot your test SD in BB Playbook, I wonder?
diamond_lover said:
I hope we can find a workaround, there will be a way to do that, because they installed android in some way.
BTW, have you tried a bootable SD card? I think it's the right path to follow.
EDIT: I see you can't boot by sd card.. what about if you try some file from Nook Color?
Click to expand...
Click to collapse
Trust me, I've tried every trick used when we figured out how to boot on the NC.
might need some combination of keypress while the thing powers on...
I bet BN built-in some backdoor 'boot off SD' mode. This would allow them to grab the Nook Tablets and reformat the onboard space/memory however they see fit.
This was done in the past with the NC.
discothan said:
might need some combination of keypress while the thing powers on...
I bet BN built-in some backdoor 'boot off SD' mode. This would allow them to grab the Nook Tablets and reformat the onboard space/memory however they see fit.
This was done in the past with the NC.
Click to expand...
Click to collapse
I agree, but it sounds like the problem is not with it blindly skipping the SD card but with it not seeing a signed image on the SD card. In that case B&N might just be providing their stores with SD cards with a properly signed image that doesn't need any other tricks
If B&N really is requiring signed images to boot from the SD card, I guess there might a different method to change the bootloader - after all, most (all?) phones won't boot off of a SD card, and it is still possible to change bootloaders on many of them.
BUT, I don't think this device is going to have nearly the same dev support as a year ago to discover/crack the bootloader issue.
I'll wait a little bit longer, but the quick progress rooting the Kindle Fire makes me think that that might be my next device to replace my lost Nook Color.
Sorry B&N - you might have lost me!
jasoraso said:
If B&N really is requiring signed images to boot from the SD card, I guess there might a different method to change the bootloader - after all, most (all?) phones won't boot off of a SD card, and it is still possible to change bootloaders on many of them.
BUT, I don't think this device is going to have nearly the same dev support as a year ago to discover/crack the bootloader issue.
I'll wait a little bit longer, but the quick progress rooting the Kindle Fire makes me think that that might be my next device to replace my lost Nook Color.
Sorry B&N - you might have lost me!
Click to expand...
Click to collapse
agreeed. there's so many low-cost devices out there and devs are going to have to pick "sides": kindle fire, nook tablet, and who can forget the hp touchpad
Considering most people havent had this in their hands more than 24 hours, I think it's a bit premature to make any calls.
That being said, I'll be holding on to my $$ a wee bit longer it seems.
I really hope it can be rooted and then be able to put ICS on it. I guess I will hold onto my money a little longer also.
Even though I want the NT more, I would get a KF since it can be rooted.
DarkDvr said:
Fill your heart with patience, people =)
Click to expand...
Click to collapse
Let's all just take a deep breath and not get carried away, this stuff hasn't been out for a week yet.
Nuenjin said:
Let's all just take a deep breath and not get carried away, this stuff hasn't been out for a week yet.
Click to expand...
Click to collapse
It isn't even "officially" out at all yet
so far I am happy with it but root would be nice.
I thought it was officially out today?
Ellerbestyle said:
I thought it was officially out today?
Click to expand...
Click to collapse
Official date is 18/11
Hello guys,
Is there a possibility to update the "archos 10.1 (gen8)"
from android froyo 2.2 to android 4.4??
And if it is possible would it be worth it to do that ?
Will speed and so increase the tablet?
Greetings Avanox
Absolutely not.
Mavasilisk said:
Absolutely not.
Click to expand...
Click to collapse
Hello again, thank you for your reply.
And not possible to install another version that's higher than 2.2 on that tablet?
Greetings Avanox
Avanox said:
Hello again, thank you for your reply.
And not possible to install another version that's higher than 2.2 on that tablet?
Greetings Avanox
Click to expand...
Click to collapse
2.3 or 4.0 but that's the highest u can go, did u even have a look in the gen8 android development section?
Ranomez said:
2.3 or 4.0 but that's the highest u can go, did u even have a look in the gen8 android development section?
Click to expand...
Click to collapse
Waw great. Thanks for the information.
Yes I did check this section but probably not good enough.
Avanox said:
Waw great. Thanks for the information.
Yes I did check this section but probably not good enough.
Click to expand...
Click to collapse
Here is the link to ICS (4.0.x): http://forum.xda-developers.com/showthread.php?t=1941377
And here is the link to GB (2.3.x): http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread (there is also a thread on this forum)
Unfortunately the openaos site seems to be down right now (was up in the morning and last night when I answered you) but anyway I did find cm9 (ics) to be more stable and "usable" (less bugs than actually affect usability) than cm7 (gb) although no doubt quite a bit slower than cm7, but again that's me that has at least 300 apps installed on each android device and that goes back to since I had a HTC Touch Pro 2 and turned it from an windows mobile device to an android one and the specs on that were way lower than the ones on the gen8.
Also feel free to ask any questions you may have related to our gen8 tablets, I am one of the "lost souls" still using this tablet and I can say that judging by the fact that I bought this quite soon after it was released (at least in my country) I can say it has served me well since then and I still think it is a decent device (although I do now have a much better and much more powerful tablet device too, my 101it is still a fun thing to play around with).
Hello again I will give it a try now.
Any idea where I can download the kernel ?
Because the download link doesn't work on the link you gave me for android 4.
I just posted for it.
Would you still have it or could you reupload this for me?
Would be awesome.
Greetings Avanox
Ranomez said:
Here is the link to ICS (4.0.x): http://forum.xda-developers.com/showthread.php?t=1941377
And here is the link to GB (2.3.x): http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread (there is also a thread on this forum)
Unfortunately the openaos site seems to be down right now (was up in the morning and last night when I answered you) but anyway I did find cm9 (ics) to be more stable and "usable" (less bugs than actually affect usability) than cm7 (gb) although no doubt quite a bit slower than cm7, but again that's me that has at least 300 apps installed on each android device and that goes back to since I had a HTC Touch Pro 2 and turned it from an windows mobile device to an android one and the specs on that were way lower than the ones on the gen8.
Also feel free to ask any questions you may have related to our gen8 tablets, I am one of the "lost souls" still using this tablet and I can say that judging by the fact that I bought this quite soon after it was released (at least in my country) I can say it has served me well since then and I still think it is a decent device (although I do now have a much better and much more powerful tablet device too, my 101it is still a fun thing to play around with).
Click to expand...
Click to collapse
Avanox said:
Hello again I will give it a try now.
Any idea where I can download the kernel ?
Because the download link doesn't work on the link you gave me for android 4.
I just posted for it.
Would you still have it or could you reupload this for me?
Would be awesome.
Greetings Avanox
Click to expand...
Click to collapse
The link that you are talking about that isn't working is the kernel source link (which is actually very unfortunate) and not the kernel itself, the kernel can be downloaded from the attachments of the first post in the thread (a zimage and the initramfs.cpio.gs files)
Hello again ,
I will set it on a row:
1. Cm9 image download (ok)
2. Initramfs.cpio.gz download (ok)
3. Kernel download
(which files are the kernel to download zimage and the initramfs.cpio.gs??)
I can't see a link to the zimage ?? Can you give me the correct link?
4. Data.img.tar.gz download (ok)
Install kernel by SDE menu
(ok I know how to get in the SDE menu but what steps I have to do there?)
Where to configure menu.Ist (is that the one I downloaded in the attachements downstairs?
What about the terminal ? How to enter the terminal to activate Bluetooth?
What is the swap configuration??
Ok and one last question, at the moment my Archos 10.1 gen8 is running on Urukdroid must I remove the sd card for this procedure and reinstall the SDE firmware or not?
Or is this method for cm9 (android4) not like urukdroid method??
Sorry for all my questions but I don’t want to make mistakes.
Greetings Avanox
Ranomez said:
The link that you are talking about that isn't working is the kernel source link (which is actually very unfortunate) and not the kernel itself, the kernel can be downloaded from the attachments of the first post in the thread (a zimage and the initramfs.cpio.gs files)
Click to expand...
Click to collapse
Avanox said:
Hello again ,
I will set it on a row:
1. Cm9 image download (ok)
2. Initramfs.cpio.gz download (ok)
3. Kernel download
(which files are the kernel to download zimage and the initramfs.cpio.gs??)
I can't see a link to the zimage ?? Can you give me the correct link?
4. Data.img.tar.gz download (ok)
Install kernel by SDE menu
(ok I know how to get in the SDE menu but what steps I have to do there?)
Where to configure menu.Ist (is that the one I downloaded in the attachements downstairs?
What about the terminal ? How to enter the terminal to activate Bluetooth?
What is the swap configuration??
Ok and one last question, at the moment my Archos 10.1 gen8 is running on Urukdroid must I remove the sd card for this procedure and reinstall the SDE firmware or not?
Or is this method for cm9 (android4) not like urukdroid method??
Sorry for all my questions but I don’t want to make mistakes.
Greetings Avanox
Click to expand...
Click to collapse
There are a few files starting with zImage, chose one of the 3 of them and rename it to just zImage (no extension and don't extract it although when youu will download it it is an archive, just rename it to zImage and I can't really tell you which one to choose cause I do not know which of the 3 will work best for you, I personally use the 35% one.
To flash it you will use the same procedure as for urukdorid but you will loose access to urukdroid, though you don't need to remove your card and also AFAIR the OpenAOS multi-boot menu does not have the ability to boot at tablet boot (or I am wrong, not sure) so you might have to reboot in recovery and run developer version each time you want to boot it.
You could also use kboot for even more multi-boot and being able to still use urukdroid, I think I posted a mirror for the files on it's thread, or at least I wanted to, if I didn't I will. BUT if you do want this first backup the urukdroid kenrel and initramfs, I can tell you how to do it if you intend to do this, if loosing access to urukdroid is ok for you then I'd say don't bother, uruk isn't that great, you can get the same things on stock after getting root on it, though I could still recommend using it as that's the only way to have rooted stock using the kernels here on the forums or being able to boot also GB and/or debian/bodhi/whatever other linux distro you fancy.
For the OpenAOS boot menu you indeed need to download that menu.lst and put it on the storage, it is already setup for booting CM9 so you don't really need to do much more here.
Swap is already configured so you don't really need to do anything about that or worry about it, it's just info and for the bluetooth I think terminal emulator comes preinstalled so you do the commands in there but I would recommend creating a bash script and downloading SManager from play store and using that to create a homescreen shortcut to your script (I could also share you my script if you would like later after I charge my archos.
Also there is no initramfs.cpio.gs that was a typo, it's actually .gz so you have the right file and the kernel is the zImage.
In the SDE menu just do the steps you did when you flashed urukdroid but only place the initramfs.cpio.gz and zImage without a 3rd file (if I remember correctly the steps for flashing urukdroid), I can't really tell you what steps to do in there as I don't really remember, it's something like go in the repair menu and click flash developer firmware or something along those lines I think.
EDIT: Also if you intend to edit the menu.lst file for whatever reason (if you want to use kboot to add the CM7 kernel and use that to boot CM7 and/or debian for example) don't use windows notepad, instead install notepad++.
Ok this makes some things clear to me
Yeah is also a long time ago urukdroid installing.
I found the guide from it but it seems idd similar to your explanation.
https://code.google.com/archive/p/urukdroid/wikis/Installation.wiki
ok I Installed Kernel and initramfs.cpio.gz
But what about installing cm9 image?
1. I did extract "CYANOBIZ_BETA2.6_A101.img" and copyd it to the root.
2. I did uncompressed data.img.tar.gz, I choosed one of the 3 images and renamed it to data_ICS.img
3. I did copy the 2 files to the root.
But what now how to install it? That's not specificly said how you must do it.
Can you help me ?
Greetings
Avanox said:
ok I Installed Kernel and initramfs.cpio.gz
But what about installing cm9 image?
1. I did extract "CYANOBIZ_BETA2.6_A101.img" and copyd it to the root.
2. I did uncompressed data.img.tar.gz, I choosed one of the 3 images and renamed it to data_ICS.img
3. I did copy the 2 files to the root.
But what now how to install it? That's not specificly said how you must do it.
Can you help me ?
Greetings
Click to expand...
Click to collapse
You need to also drop the menu.lst file on the internal memory and have the cm9 image named as CYANOBIZ_BETA2.6.img then just got to recovery and boot the developer edition firmware and you will be greeted by a boot menu with just one item, click power and it will boot and that's it.
You don't really install anything, the tablet will boot from the img file and use the data.img file as the data partition, that's all (and if you decide to move any apps to the sd card aka internal memory don't boot in an other android os like stock because the android_secure folder will be wiped, though I am not sure CM9 allows you to, I know CM7 does).
Also I have uploaded kboot and it is on the thread in the development section if you want to use that for more flexible multi-boot (or at least to have the multi-boot menu loaded at every normal boot without needing to enter recovery to boot ics), although now it will be a bit hard to obtain the uruk kernel in case you still want to boot that, it is possible, you just need a linux computer or the ext2fsd driver in windows, I can't really give you the kernel from my installation of it since I understood yours is on the sd card and mine is on the internal memory.
And if you would like I can give you kboot already set up with the stock root kernel and all the 3 ics kernels to make it easier for you.
Ow ok will try tomorrow.
Euhm yeah urukdroid is no more on tablet I think I installed last sde firmware.
The kboot is that for switching between then Linux similar system and android 2.2 and android 4 and maybe urukdroid if I reinstall it (not necessary for the Moment?)
Yeah I will try out that kboot you may send it to me if you want. Maybe it's cool feature
Thanks in advance
Greetings
Ranomez said:
You need to also drop the menu.lst file on the internal memory and have the cm9 image named as CYANOBIZ_BETA2.6.img then just got to recovery and boot the developer edition firmware and you will be greeted by a boot menu with just one item, click power and it will boot and that's it.
You don't really install anything, the tablet will boot from the img file and use the data.img file as the data partition, that's all (and if you decide to move any apps to the sd card aka internal memory don't boot in an other android os like stock because the android_secure folder will be wiped, though I am not sure CM9 allows you to, I know CM7 does).
Also I have uploaded kboot and it is on the thread in the development section if you want to use that for more flexible multi-boot (or at least to have the multi-boot menu loaded at every normal boot without needing to enter recovery to boot ics), although now it will be a bit hard to obtain the uruk kernel in case you still want to boot that, it is possible, you just need a linux computer or the ext2fsd driver in windows, I can't really give you the kernel from my installation of it since I understood yours is on the sd card and mine is on the internal memory.
And if you would like I can give you kboot already set up with the stock root kernel and all the 3 ics kernels to make it easier for you.
Click to expand...
Click to collapse
Avanox said:
Ow ok will try tomorrow.
Euhm yeah urukdroid is no more on tablet I think I installed last sde firmware.
The kboot is that for switching between then Linux similar system and android 2.2 and android 4 and maybe urukdroid if I reinstall it (not necessary for the Moment?)
Yeah I will try out that kboot you may send it to me if you want. Maybe it's cool feature
Thanks in advance
Greetings
Click to expand...
Click to collapse
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Hello first of all I wanted to say I just got into android 4.4.
But when I start it up I get a lot of messages that are saying.
This application doesn't work anymore.
Any idea what this could be?
Hmm after looking I restarted it and now it works better the android 4.4
But how do you put something on the internal memory if I connect them with usb to laptop I can't acces the root with all my files.
Greetings
R
anomez;65030979 said:
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Click to expand...
Click to collapse
Avanox said:
Hmm after looking I restarted it and now it works better the android 4.4
But how do you put something on the internal memory if I connect them with usb to laptop I can't acces the root with all my files.
Greetings
Click to expand...
Click to collapse
It is clearly stated that you can't access the internal memory via msc on the ics thread, only the sd card, and that is also true for any firmware that boots from an img file since the img is on the internal memory and that would mean cutting the system's access to itself=crash.
Ranomez said:
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Click to expand...
Click to collapse
Hello again,
Owkey now if I start up my tablet android 2.2.1 startsup
(firmware version: 2.4.83)
I did set the iso file from cyanobiz_BETA2.6.img on my internal memory.
So cm9 boots nice on the tablet but I must go first to the SDE (by pushing volume + ) then a see a white menu -> developer edition -> and chose cyonade and it start good
Urukdroid was installed on my sdcard but that doesn't start anymore as standard at moment. don't know why?
Before I started with cm9 I installed the latest SDE firmware for archos 10.1 gen8. (and the procedure to runb cm9)
Would it work with your kboot file so I can choose between:
android 2.2 (Archos),
Android 4 (CYANOBIZ)
Angstrom (openAOS)
urukdroid 1.6 (not in the menu)
Greeetings Avanox
Avanox said:
Hello again,
Owkey now if I start up my tablet android 2.2.1 startsup
(firmware version: 2.4.83)
I did set the iso file from cyanobiz_BETA2.6.img on my internal memory.
So cm9 boots nice on the tablet but I must go first to the SDE (by pushing volume + ) then a see a white menu -> developer edition -> and chose cyonade and it start good
Urukdroid was installed on my sdcard but that doesn't start anymore as standard at moment. don't know why?
Before I started with cm9 I installed the latest SDE firmware for archos 10.1 gen8. (and the procedure to runb cm9)
Would it work with your kboot file so I can choose between:
android 2.2 (Archos),
Android 4 (CYANOBIZ)
Angstrom (openAOS)
urukdroid 1.6 (not in the menu)
Greeetings Avanox
Click to expand...
Click to collapse
Kboot will make it load at boot so it will go to the boot menu instead of stock 2.2 from where u can choose what to boot or (after a period of time) it will just boot your last selection.
Yes from Kboot you can choose to boot any of those though I really wouldn't recommend Angstrom (I don't even think you can still find a rootfs.img for it, if you still have it on your internal memory please upload) cause it is really limited and also I don't think OpenAOS made a kernel for Angstrom and it'll be quite hard to get the kernel from the SDL aos package (though I do have a kernel that can boot it directly, compiled from the stock 2.2 sources, NOT by me). In theory you can edit the menu.lst to launch Angstrom for it but remember you must edit it with Notepad++ and not any other windows text editor (notepad, word, etc) and you will need to know the format for booting a linux image file (I can tell you what that is) and just add the OpenAOS CM7 (gingerbread) kernel also and use that to boot Angstrom, never boot ANYTHING ELSE when loading the boot menu with the ICS kernel, you will have the same options but you must always remember you CAN'T launch anything else than ICS when launching the OpenAOS boot menu with the ICS kernel. But if you are actually interested in running linux I'd say just go the debianlxde way (download from OpenAOS site) as it is so way much better than Angstrom.
To boot UrukDroid you will need to either have linux installed on your PC/laptop or boot a live cd, put the MicroSD Card in a card reader and connect it and then search the uruk partitions to find the zImage and initramfs.cpio.gz (they might have some slightly different names) and put those in a new folder in the kboot os folder, of if you want I could probably unpack the UrukDroid install and update packages to find the right kernel for you but as I can't really remember what tools I need for doing that you will have to wait about 2-3 weeks (I have exams and also bought myself a Nintendo New 3DS XL that I plan to hard mod after I finish with the exams and do a nand dump and try to edit the firmware and flash it back to see what I can obtain so that's gonna take me about 1-5 days as I am not the best with soldering things on motherboards). You will also have to wait that exact same amount of time if you want me to tell you from where on the UD partitions to find the kernel files as I do not know myself and will have to search for them.