yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] rookie1:
There is no tar.gz archive of honeycomb. I can do it manually, but it's difficult to create a script to automate the data extraction from an sd image. I'll send a PM to deeper-blue and ask whether he is willing to release a tar.gz archive similar to what cicada did to nookie froyo.

Also you will need to modify init.rc to mount the correct partition as /system and /data. This is the reason I've included modified uFRam in my dual boot installation.
[Nook Color Android Development] Novarider:
I just tried this but I replaced the froyo image with the new 0.6.6 tar.gz file. Now it will boot normally if I dont press the n button but if I hold the n button it gets stuck at the loading screen. What did I do wrong?

EDIT: I edited the dual-boot.sh file to 0.6.6 and I got past the loading screen but now its stuck on the screen that the green android_ and the _ is flashing.

EDIT 2: I undid the dual boot then reran the script and I get this message

Superblock backups stored on blocks:
32768, 98304, 163840, 229376
dual-boot.sh: line 49: tune2fs: not found
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Copy Nookie Froyo files
>>>>>>>>>>>>>>>>>>>>
mount: mounting /dev/block/mmcblk0p10 on /data/dualboottmp/data failed: Invalid
argument
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Clean up
>>>>>>>>>>>>>>>>>>>>
umount: can't umount /data/dualboottmp/data: Invalid argument
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Done
>>>>>>>>>>>>>>>>>>>>

Is it normal to get Invalid argument?
[Nook Color Android Development] flak0:
OP Help im getting this:
[Nook Color Android Development] ver2go:
All the errors seem to be this:

arm-none-linux-gnueabi-gcc: Command not found

Maybe the x-compiler env didn't symlink gcc to arm-none-linux-gnueabi-gcc
[Nook Color Android Development] Novarider:
Can anyone help with this? I really want to use this but I just can't get it to work. When I originally installed froyo to the emmc I used dd not a flashable version if that matters
[Nook Color Android Development] ver2go:
Are you doing this from rooted stock? I believe you have to be in the rooted eclair then the dual-boot.sh script modified for 0.6.6. I tried it yesterday and it worked fine. I backed out since market was not in the 0.6.6 file.
[Nook Color Android Development] Novarider:
Not according to what the OP said above. I'm running nookie froyo 0.5.9 on the emmc. You install this then deleted it?

"I backed out since market was on in the 0.6.6 file"

That doesn't make sense to me what are you saying?
[Nook Color Android Development] ver2go:
On emmc I had rooted 1.1 BN eclair.

I used the dual boot here and install 0.5.9

Then I installed the customized 0.5.9 (the one with copy2emmc.sh)

When 0.6.6 came out,

I booted back into rooted 1.1 BN eclair

reran the modified dual-boot.sh with the 0.6.6 tar ball.

Booted up fine in 0.6.6, but it didn't have market in the image, so I rebooted back to BN 1.1 eclair to dual-boot.sh back to the 0.5.9

Then customized again with the 0.5.9 copy2emmc.sh
[Nook Color Android Development] Novarider:
I understand now.

I really wish i could get this working. I want to install this so I can have dual boot then replace Eclair with Honeycomb
[Nook Color Android Development] rookie1:
The dual boot script depends on a few programs on stock eclair - newfs_msdos, mke2fs, tune2fs. Have you overwritten the stock eclair on emmc? If you are running nookie froyo on emmc as your base image, can you do a 'ls /system/bin/' in adb shell and check whether these programs are there in nookie froyo?
[Nook Color Android Development] rookie1:
Seems your CodeSourcery toolchain is not setup correctly. Do you have /home/flak0/Disk2/CodeSourcery/Sourcery_G++_Lite/arm-none-linux-gnueabi-gcc?
[Nook Color Android Development] nookierookie:
Seems that flashing froyo to emmc with the newest 0.6.6 loses mke2fs and tune2fs.

Your script does create the partitions with parted, confirmed by running (parted) print... Somehow I doubt copying over the system/data/boot files would work though.
[Nook Color Android Development] Novarider:
I will check tomorrow and let you know. Can that command be used in terminal or does it have to be adb?
[Nook Color Android Development] Mytos-xda:
is there a script or command i can use inside eclair that will force your boot to boot to nf?
[Nook Color Android Development] dfellars77:
Froyo 0.6.7

Do we know if this method works with the latest NF release?
[Nook Color Android Development] Novarider:
mke2fs and tune2fs are both not there. Is it possible to do this without those files? I can do it by command line if I need to if you tell me what needs to be typed.
[Nook Color Android Development] ver2go:
cat dual-boot.sh

Follow it from the tar of nookie tarball on. Provided the partitions have already been created previously.
[Nook Color Android Development] Novarider:
Huh? Were you talking to me?
[Nook Color Android Development] aho43:
Just upgraded my existing dual boot emmc NF 5.9 install to 6.7 following rookie1's script.

If you are trying to install the dualboot for the first time, just change the following line in the script from the "Copy Nookie Froyo Files" portion:

busybox tar zxf nookie-froyo-base-0.5.9.tar.gz -C /data/dualboottmp

to

busybox tar zxf nookie-froyo-base-0.6.7.tar.gz -C /data/dualboottmp

Then follow the original instructions, and make sure you have the 6.7 base rom in your dualboot folder. Available here, http://edencomputing.com/nookcolor/nookie-froyo-base-0.6.7.tar.gz

If you are trying to upgrade you need to create the working directory then skip to the "Copy Nookie Froyo Files" portion of the script, making the change I mentioned above.
[Nook Color Android Development] sacwoo:
I am getting this same error when trying to repair my media partition

/sdcard/dualboot # newfs_msdos -F 32 -L media /dev/block/mmcblk0p8

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

/sbin/sh: newfs_msdos: not found

Anyone? I can't DL any of my books without fixing this media partition. If no one has any ideas I may end up returning it and playing dumb.
[Nook Color Android Development] jewnersey:
Can i dual boot between my nookie0.6.7 on emmc and the new HCv4 that is flashable?

I really wanna mess around with honeycomb but my NF is all set up and I don't want to lose it.
[Nook Color Android Development] rookie1:
Are you running stock eclair? newfs_msdos should be in /system/bin
[Nook Color Android Development] rookie1:
If you already have eclair/froyo dual boot setup, you can overwrite eclair using flashable HC. Just remember to back up my dual boot u-boot.bin. In case the flashable HC overwrites u-boot.bin, you will lose the dual boot capability.
[Nook Color Android Development] jewnersey:
Im currently only running froyo on emmc, but reallllly dont want to wipe because i have it set up so perfectly.

so basically the only way i can do it is if flash back to eclair, install dualboot with froyo, then overwrite eclair with HC..?
[Nook Color Android Development] ver2go:
Okay, lets back up. You're still trying to put 0.6.x froyo on your emmc as partition 9 and 10 using dual-boot right?

To get pass the lack of mkfs, tunefs etc.. from you being in froyo and not the stock eclair rooted, we need to make sure the partitions are there from your previous install.

do a

ls /dev/block/mmcblk0p?

If you have all the additional partitions (9 and 10 would be a good indicator).

Then you can modify the dual-boot.sh by removing all the portions that do the repartition, make partition and create fs.

Which is something like this (you still get some errors, I didn't bother going through everything, but this will work to get the new nookie on the correction partitions and boot up. I used this myself for the last upgrade).

Make sure you have the partitions created from before. Otherwise don't do this.

echo ">>>>>>>>>>>>>>>>>>>>"
echo ">>>>>>>>>>>>>>>>>>>>Create working directory"
echo ">>>>>>>>>>>>>>>>>>>>"
mkdir /data/dualboottmp

echo ">>>>>>>>>>>>>>>>>>>>"
echo ">>>>>>>>>>>>>>>>>>>>Back up /media to sdcard"
echo ">>>>>>>>>>>>>>>>>>>>"
busybox tar zcf /sdcard/media_backup.tar.gz /media
if [ "$?" -ne "0" ]; then
echo "Backup failed. Exiting."
exit 1
fi
umount /media

echo ">>>>>>>>>>>>>>>>>>>>"
echo ">>>>>>>>>>>>>>>>>>>>Restore /media"
echo ">>>>>>>>>>>>>>>>>>>>"
busybox tar zxf /sdcard/media_backup.tar.gz -C /

echo ">>>>>>>>>>>>>>>>>>>>"
echo ">>>>>>>>>>>>>>>>>>>>Copy Nookie Froyo files"
echo ">>>>>>>>>>>>>>>>>>>>"
mkdir /data/dualboottmp/system
mkdir /data/dualboottmp/data
mount -t ext2 /dev/block/mmcblk0p9 /data/dualboottmp/system
mount -t ext3 /dev/block/mmcblk0p10 /data/dualboottmp/data
busybox tar zxf nookie-froyo-base-0.6.7.tar.gz -C /data/dualboottmp
mkdir /data/dualboottmp/tmpboot
mount -t vfat /dev/block/mmcblk0p1 /data/dualboottmp/tmpboot
busybox cp /data/dualboottmp/boot/uImage /data/dualboottmp/tmpboot/uFImg
busybox cp /data/dualboottmp/uFRam /data/dualboottmp/tmpboot/uFRam
if [ -f /data/dualboottmp/tmpboot/u-boot.bin.stock ];
then
echo "u-boot.bin.stock exists. skip backup"
else
mv /data/dualboottmp/tmpboot/u-boot.bin /data/dualboottmp/tmpboot/u-boot.bin.stock
fi
busybox cp /data/dualboottmp/u-boot.bin /data/dualboottmp/tmpboot/u-boot.bin
busybox sed -i 's/\/mnt\/sdcard\ 4/\/mnt\/sdcard\ 1/g' /data/dualboottmp/system/etc/vold.fstab

echo ">>>>>>>>>>>>>>>>>>>>"
echo ">>>>>>>>>>>>>>>>>>>>Clean up"
echo ">>>>>>>>>>>>>>>>>>>>"
umount /data/dualboottmp/system
umount /data/dualboottmp/data
umount /data/dualboottmp/tmpboot
busybox rm -rf /data/dualboottmp

echo ">>>>>>>>>>>>>>>>>>>>"
echo ">>>>>>>>>>>>>>>>>>>>Done"
echo ">>>>>>>>>>>>>>>>>>>>"
[Nook Color Android Development] Novarider:
Ok thanks. I will try that when I get home from work. Would it work if I replaced the froyo image with a honeycomb image? I know I would need to change the line in the code that tells what image to flash but would everything else work the same?

My ultimate goal is to dual boot NF and HC.
[Nook Color Android Development] dfellars77:
I actually made this work by renaming the 0.6.7 img to 0.5.9 for the initial dual boot install. Worked perfectly.
[Nook Color Android Development] flak0:
You do realize that u also have to unpack the uRamdisk image from nookie froyo edit the init.RC to point to partitions 9 and 10 and then repackaged the uRamdisk image and place in the dual-boot-tools.tar as uFRam, otherwise a lot of changes and fixes won't work. Ie YouTube, Pandora, etc.
[Nook Color Android Development] Novarider:
When i run

"ls /dev/block/mmcblk0p?"

I get

/dev/block/mmcblk0p1

/dev/block/mmcblk0p2

/dev/block/mmcblk0p3

/dev/block/mmcblk0p4

/dev/block/mmcblk0p5

/dev/block/mmcblk0p6

/dev/block/mmcblk0p7

/dev/block/mmcblk0p8

/dev/block/mmcblk0p9

No partition 10. Does that mean the partion part didn't work?
[Nook Color Android Development] ver2go:
It means I gave you the wrong wildcard to match 2 digits too.

ls /dev/block/mmcblk0p*

Should show it. sorry about that.
[Nook Color Android Development] Novarider:
All 10 are there but they are listed weird. I goes 1,10,2,3,4,5,6,7,8,9 Does it matter that the are not in order?
[Nook Color Android Development] ver2go:
No, the order is just the sort order as defaulted from "ls". It means nothing other than how ls sorted the output.
[Nook Color Android Development] fwdixon:
Ok, trying this with the latest NF build (0.6.7) but keep getting errors.

busybox sh dual-boot.sh
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Create working directory
>>>>>>>>>>>>>>>>>>>>
, File existsfor /data/dualboottmp
: No such file or directoryootmp/parted
:not foundh: line7:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Back up /media to sdcard
>>>>>>>>>>>>>>>>>>>>
: No such file or directory
tar: error exit delayed from previous errors
dual-boot.sh: line 84: syntax error: unexpected end of file <expecting "then">
[Nook Color Android Development] dfellars77:
Ok, no I did not realize that. As such, I removed the froyo partitions and dual boot then did this:

However YouTube and Pandora still do not work.

Do I still need to edit the init.RC? If so, NM because that is out of my league.

Thanks!
[Nook Color Android Development] ChrisJ951:
Does anyone have a modified uFRam for 0.6.7? I can't figure out how to compile a ramdisk from its source, but I was able to uncompile it and change the new init.rc to work.
[Nook Color Android Development] fwdixon:
Tried that, doesn't work for some reason. See error message above
[Nook Color Android Development] aho43:
Are you running the script on top of Eclair or Froyo?
[Nook Color Android Development] ver2go:
Here is what I have bookmarked.

I haven't had a chance to re-pack the image yet.
[Nook Color Android Development] ChrisJ951:
The problem is the link to the perl script is no longer working (dead link). Here's the code already editted to work for the dual boot, but I cant compile it as Ive yet to find an easy way to
[Nook Color Android Development] ver2go:
The perl script was the "alternate" method.

Method 1 was to:

find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz

which seemed to work on my linux box.

If you don't have a linux box, I'll try your files a bit latter.
[Nook Color Android Development] ver2go:
* edit - not ready yet. forgot a step
[Nook Color Android Development] ChrisJ951:
If you can, try this one as well, im not sure if youre suppose to have an init.rc and a froyo.init.rc or just init.rc alone

Thanks

edit: Actually im mostly certain the first one is incorrect while is the version that needs compiling.
[Nook Color Android Development] fwdixon:
running in ADB wireless on stock eclair
[Nook Color Android Development] aho43:
6.7 ufram

Alright, I tried compiling uRamdisk from the 6.7 ramdisk-src files, following these directions: http://nookdevs.com/NookColor:_Build_the_Original_Kernel#Create_your_uRamdisk_file

I've tried using the init.rc that MattJ951 provided, which I believe was the froyo.init.rc, and by editing the regular init.rc as well. When I attempted to boot into Froyo using both of the resulting uRamdisk images, renamed to uFRam and moved to the boot partition, I get to the first "Android_" in vertical script, but it hangs there.

EDIT: Tried one more thing and got a working 6.7 uFRam packaged. Apparently I had edited init.rc incorrectly. MattJ951, I think the mount points you used were incorrect, and the init.rc you should use is the regular init.rc, not the froyo.init.rc.

The new mountpoints should be mmcblk0p9 for /system, and 0p10 for /data.

I've gone ahead and attached a uFRam for 6.7 and the init.rc I used if anyone wants to look at for reference.

If you would like to use the new uFRam just run the following in adb after placing uFRam in your dualboot folder, this is assuming you already have dualboot setup w/ Froyo installed and are just trying to upgrade your uFRam.

cd /sdcard/dualboot
mkdir /data/uframtmp
mount -t vfat /dev/block/mmcblk0p1 /data/uframtmp
busybox cp uFRam /data/uframtmp/uFRam
umount /data/uframtmp
busybox rm -rf /data/uframtmp

Youtube appears to be working. I have not confirmed if Pandora works or not.

Edit2: need to make one more change, will post a new ufram later.

My advice would be to open up rookie1's script and run it line by line manually in adb and see where it is getting messed up.
[Nook Color Android Development] rookie1:
Don't do that. Blk1 is your sd card. Most likely you don't have a partition 7 :) the reason to mount blk0 is to use the internal mmc for faster caching.
[Nook Color Android Development] aho43:
Ah, thanks. I will change that. Still learning :o
[Nook Color Android Development] ChrisJ951:
Hoping to see it posted soon. I did change the mountpoints to those but I may have missed some. rookie1 posted the original mountpoints so hopefully you can use those as reference to get the new version out. Good Luck with it as Im looking foward to dual booting with it
[Nook Color Android Development] aho43:
ok, when you edit init.rc all you need to edit is where system and where data mount, not cache. here is a proper uFRam w/ cache mounting properly to blk0p7.

i hope this works for everyone looking for it,
[Nook Color Android Development] fwdixon:
Ok, well, after making partition 8, NC goes into reboot loops. So I guess the next question is how can I restore to the default partitions without ADB (ADB doesn't work via USB, and with the NC not able to boot, can't use ADB Wireless)
[Nook Color Android Development] aho43:
Do you have clockwork recovery and if so can you boot into it? you could try killing the boot process 8 times.

http://nookdevs.com/Flash_back_to_clean_stock_ROM

If nothing else works you can make a bootable clockwork sd card.
[Nook Color Android Development] fwdixon:
well, I already botted CWR and flashed the eMMC, jsut didn't know if that would restore the partitions or not
[Nook Color Android Development] aho43:
if you already have the partitions set up i would continue in the script after the partitioning part. if you want to just scrap it and go back to regular boot, there are links in the first post on how to undo the partitioning.
[Nook Color Android Development] fwdixon:
The problem is either option requires adb afaict. Unfortunately I can only use adb wireless, and since the device is immediately rebooting after unlock, I can't open the app.
[Nook Color Android Development] aho43:
you can adb from clockwork
[Nook Color Android Development] fwdixon:
How? I didn't see a terminal in CWR. That would be great tho.
[Nook Color Android Development] winterminute:
This is exactly what I've been looking for. Couple of questions:

1) I've been playing around with the NF (6.7) that was build to be run via the SD card. Is there a difference between that build and the "base" 6.7 (nookie-froyo-base-0.6.7.tar.gz? Out of the box config or pre-installed apps, maybe?

2) When future builds of FroYo come out, what steps do we follow to upgrade?
[Nook Color Android Development] cabbieBot:
this work for deeper-blue's honeycomb v4 like it does for froyo?
[Nook Color Android Development] aztigen22:
Hi! I followed the process and tried to dual boot my NC with 1.0.1 and Froyo 5.9. When i tried to boot to Froyo, i was stuck in the boot loader screen, Eclair is ok. Then i tried to flash NC to Froyo 6.7 thinking i was replacing 5.9 but i replaced my 1.0.1 Rom. Now i followed the link as to return the partitions to original state then with CWR-SD,i wiped and formated system, data, and boot. Then i DD the system and boot images to NC and its back to 1.0.1 again. BUT, now i checked my partitions and its as follows:

system: 440.55mb

data: 941.9mb

cache: 341.82mb

media: 3.72Gb

should'nt my media BE 5GB?I tried the link in the first post to restore partitions to stock Again and this dispayed.

# busybox sh reformat-media.sh
busybox sh reformat-media.sh
This will delete /media, as well as Froyo /system and /data partition.
Have you done your backup????
If not, press Ctrl-C now to abort this script and do you backup.
': not a valid identifier
: No such file or directoryoottmp/parted
failed.
reformat-media.sh: line 9: /data/dualboottmp/parted: not found
reformat-media.sh: line 10: /data/dualboottmp/parted: not found
reformat-media.sh: line 11: /data/dualboottmp/parted: not found
reformat-media.sh: line 12: /data/dualboottmp/parted: not found
/dev/block/mmcblk0p8
/dev/block/mmcblk0p8
is not a character device0p8
Skipping mount checks
Error getting bytes / sector (Bad file number)mount: No such file or directory
/media partition re-created.
You can restore your data in /media now
#

Anything i can do to somehow restore it back to the default 5gb?im not sure wat other partitions should be but the above data is what i saw in my NC through Rootexplorer. Im sure media should be 5Gb right?
[Nook Color Android Development] aho43:
there are 2 links in the first post that tell you how to undo dual boot and restore the partitions.
[XPERIA X10 Q&A, Help & Troubleshooting] OmegaRED^:
How do i get the SE rom for dual touch?

And can it be rooted yet??
[XPERIA X10 Q&A, Help & Troubleshooting] Lord Takyon:
Have you tried reading the forum? If it had happened you would know.
[Desire Themes and Apps] listylister:
Just thought i'd post on here to let you all know about the Server Status android app. We have been working on it for the past 3 months and it's now finally ready for you all.

It has been specially designed for HTC Desire and Xperia X10 Mini so we would love your thoughts on it. Suggestions / Improvements etc.

What is Server Status

Server Status provides you with your servers uptime on the move, including average response time and average server uptime (%). It is directly fed from the server status website at http://www.server-status.co.uk. It's free of charge to add as many servers as you like. We are currently working on a premium version to allow checking of your server every 2 mins instead of every 15 mins.

You can get it by searching 'Server Status' on the app store or you can use the QR code below. To create an account please visit http://www.server-status.co.uk or register on the app itself.

Please let us know your comments.

Thanks for your time and your comments are vital to us :)
[Desire Themes and Apps] ShirazSuleman:
This should be in the Themes and Apps sub-forum, surely?
[Desire Themes and Apps] listylister:
Ahh my bad. Can it be moved please?

Thanks
[Epic 4G Q&A, Help & Troubleshooting] humdrum2009:
FOR PEOPLE HAVING WIRELESS TETHER PROBLEMS TRY THIS

First install wireless tether for root users from the market.

After install go to settings and enable WiFi encryption.

Next change your channel to a higher channel like 10-14

then put a check mark in enable access control box,

These settings work for me on every wireless device i have no problems

leave the wire less password as what it starts at then you can change it once you get a good connection .

Back up those setting with titanium backup then when you re flash a ROM its already configured when restoring
[Epic 4G Q&A, Help & Troubleshooting] smoothone:
This belongs in general and has nothing to do with development!
[Epic 4G Q&A, Help & Troubleshooting] swanysto:
So far it seems to be working. However, I am getting some pretty slow speeds. Barnacle seems to work a little better for me, but I think they have the free version capped at so much bandwidth.
[Epic 4G Q&A, Help & Troubleshooting] humdrum2009:
i noticed after i posted it

wrong section
[HD2 Android Q&A, Help & Troubleshooting and Genera] cowboykiller1313:
So i have successfully ben running android from NAND on my HTC HD2 for weeks now. when you first open an app it opens normally( holding your phone upright). As soon as i rotate it and it goes to "full screen" it wont rotate back..... This will not go away even when FC an app. This continues into every app i open up. It automatically opens in "full screen" .... The only way i can make it go away is to reboot my phone.... this gets annoying... VERY ANNOYING !!!! Does anybody have an idea how to fix this? I already tried calibrating it and one of the sensors is either to one side or the other. It will not center itself....... Lame...... SOMEBODY PLEASE HELP !!!!!

My [NAND] specs

1) DFT_LEO_MAGLDR111

2)DFT_LEO_NAND_Android

3)HSPL3_PKG

4)Radio 2.08.50.05 + task29(replaced with a working radio of my choice.) AT&T Vermont area
[EVO 4G Q&A, Help & Troubleshooting] snovvman:
I originally added my post to this thread in the Nook forum. I don't think there is enough expertise in that forum to help with this problem.

The bottom line is that ADB no longer works and I can't figure out why (see quoted text above). I would imagine that someone here would have an answer for this. Please help!

Thanks.
[EVO 4G Q&A, Help & Troubleshooting] DGreen1:
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
[EVO 4G Q&A, Help & Troubleshooting] snovvman:
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
[EVO 4G Q&A, Help & Troubleshooting] #Winning#:
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!