yashsingh1/xdaforums huggingface dataset:
[Fascinate General] htim95:
I found a rom for the evo I believe that has it for 2.2
[Nook Color Android Development] Homer_S_xda:
I have Nookie Froyo on a 16GB SDcard and it's fairly stable. I do like to use the NC from the stock or rooted OS on the EMMC on occasion. When I'm running internal and insert the NF card, it only sees the boot partition just like under windows.

So, here is my thought. With Linux, it should be somewhat straightforward to have a script to unmount boot from sdcard and remount the SDcard partition on the SDcard as sdcard. The only similar thread I found was this one.

Can a bright person give me a hand on this one?

UPDATE: The answer lies here.

Homer
[Nook Color Android Development] ChrisJ951:
I lost the page but on the forums theres one talking about mount points. What you're going to want to do(or at least this is my guess) is run something like

adb shell umount /dev/block/mmcblk1 (This is the boot partition normally)
mkdir sdcard
mount /dev/block/"Whatever the sd card mount point is" sdcard
[Nook Color Android Development] japzone:
Try This

If you mean mouting the Nookie Froyo/Honey's sdcard partition, you can do it from a Terminal App. You just need to figure out what the Nookie card's mount device is and mount the 4th partition.

Try this:

(use cd command to non System Folder)
mkdir /nookie
su
mount '/dev/block/mmcblk1p4' '/(location of nookie folder)/nookie/'

This should Mount the Partition to the "nookie" folder. You shouldn't need to unmount the First partition. You just need to mount the 4th to a different location. Then use a File Browser like Astro or Root Explorer to Browse and Transfer files.

Then use this to unmount after done file transfers and stuff:

unmount '/(location of nookie folder)/nookie/'
[Nook Color Android Development] Homer_S_xda:
Thanks for the replies. I think the goal here would be to make it transparent to applications that are writing to the sdcard partition. That way, I would browse to the files the same way regardless of the OS I happen to have booted. Also, the 117MB or so free on boot is going to fill up with junk and runs the risk of getting overwritten, wrecking the Froyo/Honeycomb installation.

Homer
[Nook Color Android Development] japzone:
More Suggestions

Good point. How about this instead.

su
unmount '/sdcard'
mount '/dev/block/mmcblk1p4' '/sdcard'

This would unmount the boot partition and then mount the sdcard partition in it's place. This is assuming that Rooted Stock mounts the SDcard at folder '/sdcard' by default, I haven't rooted my NC's Stock.

Now Mounting the Media partition(Where your books and other Media are stored) from Nookie Froyo isn't as clear cut. I found the Mount Table for Rooted Stock and Media is listed different then the others. As shown in Bold:

rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk0p6 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
[b]/dev/block//vold/179:8 /media vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0[/b]

As I said I don't have my NC Rooted so I can't investigate this. On the other hand, Accessing Stock System(p5) or Data(p6) partitions should be straight forward.

cd /sdcard
mkdir /stock-system
mount '/dev/block/mmcblk0p5' '/stock-system'
[Nook Color Android Development] Starfire-1:
A few nights ago I set up my NC to dual boot following ...

http://xdaforums.com/showthread.php?t=920347

Which in addition to stealing about 20% of the internal /media partition for the NF system, it also replaced the uboot to selectively choose which distro you wanted to boot from as well as editing the /system/etc/vold.fstab to change how the sdcard was mounted. Perhaps this last step may help(?)

BTW - I'm pleased with the dual booting off of the emmc. I'm a Linux person, so shrinking down the last partition and adding partitions 9 and 10 for FC seems like a nice, transparent solution. It doesn't seem to affect the operation of CWM's nandroid backup and restore (I've done both since dual booting) and I don't have to worry about popping out the SD card to boot the emmc based distro.
[Nook Color Android Development] samuelhalff:
working on vold.fstab is the way to go..
[Nook Color Android Development] j4mm3r:
This is exactly how its done on the honeycomb build floating around here.

Here is what the vold.fstab looks like in there:

$ adb shell cat /etc/vold.fstab
## Vold 2.0 Generic fstab
## - San Mehat (san@android.com)
##

#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################

## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1

## Example of a dual card setup
# dev_mount left_sdcard /sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1

## Example of specifying a specific partition for mounts
# dev_mount sdcard /sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1

dev_mount sdcard /sdcard 4 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
#dev_mount media /media 8 /devices/platform/mmci-omap-hs.1/mmc_host/mmc0

So this effectively mounts the partition 4 of the sdcard as /sdcard and everything works normally.
[Nook Color Android Development] japzone:
Mount NC Internal from Nookie Froyo

Ok I successfully mounted the Nook's Media Partition from within Nookie Froyo:

su
mount -o rw,remount -t rootfs /
mkdir /mnt/media
mount /dev/block/mmcblk0p8 /mnt/media
mount -o ro,remount -t rootfs /

NC Internal Media Partition is now mounted to '/mnt/media' as RW.
[Nook Color Android Development] Homer_S_xda:
So I need to modify the vold.fstab on my emmc to mount the 4th sdcard partition as /sdcard. Let me get it up and running again and I'll give that a whirl.

Homer
[Nook Color Android Development] Homer_S_xda:
Did some poking. This file does not exist in the default config. Should I create it with just this line:

dev_mount sdcard /sdcard 4 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1

UPDATE: Nope... either need permissions set right or have to tell the system to look at the file.

Homer
[Nook Color Android Development] j4mm3r:
Hold on a sec... are you doing this when booting into the Nook rom? 'Cause if you are then just keep in mind that the Nook is based on Eclair and vold.fstab was introduced in Froyo...

The Idea that I was trying to convey was that in case you happen to be booting from a Froyo image on the SD card, then having such a seupt in the vold.fstab would allow you to mount the remainder of the SD card as /sdcard.

If however, you want to share the SD card partition when you boot into Nook, I'm afraid that this wont work. I think the Eclair vold is kind of dumb and always tries to mount the first usable partition off of the card, which'll be the small boot partition in case you have burned nookiefroyo.
[Nook Color Android Development] samuelhalff:
On Eclair, change vold.conf..
[Nook Color Android Development] Homer_S_xda:
Thanks again everyone! The answer is here.

Homer
[Nook Color Android Development] dweezilz:
seems on 1.2 editing vold.fstab works instead of vold.conf Just replaced the first 'auto' with 4 and poof, part. 4 is now the SD card!! Previously before 1.2 update vold.conf was the route. That didn't seem to work this time so once I edited fstab it was perfect.
[Nook Color Android Development] chhaggerty:
Check this thread for updated and improved information, many thanks to j4mm3r

http://xdaforums.com/showthread.php?t=953110

Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. Using this version of su is not as secure because it will not activate Superuser for your permission to grant root access. In fact, it can work without Superuser.apk installed at all. Hopefully we will soon have an updated su or maybe the next version of Honeycomb will be prerooted. First download the following files:

1. su http://www.magicandroidapps.com/su.zip

2. Superuser.apk http://bit.ly/su2361ef

3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2

Extract the above files using your favourite program

Using adb, install all three files to /data/local:

adb push su /data/local

adb push Superuser.apk /data/local

adb push busybox /data/local

Use adb remount to open the /system directory

adb remount

Use adb shell to move files

adb shell

cd /data/local

cat Superuser.apk > /system/app/Superuser.apk

cat su > /system/bin/su

cat busybox /system/xbin/busybox

Symlink su and set permissions:

ln -s /system/bin/su /system/xbin/su

chmod 06755 /system/bin/su

Typing su should now work

su

su: access granted, courtesy of www.magicdroidapps.com

Install busybox

exit from adb shell and using a terminal application (i.e Root Explorer or Better Terminal Emulator) on the nook,

su

busybox --install -s /system/xbin

That should do it, works with Root Explorer, Titanium Backup, LCD Density, Quick Boot and SetCPU.

Good Luck
[Nook Color Android Development] HotShotAzn:
really? That simple? Root was the only reason i haven't jumped on the Honeycomb train. This may change my mind.
[Nook Color Android Development] anbradle:
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
[Nook Color Android Development] Homer_S_xda:
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?

Homer
[Nook Color Android Development] chhaggerty:
Check your steps, especially permissions and the symlink. Works consistently on reboot for me.
[Nook Color Android Development] chhaggerty:
I couldn't get it to work for me without installing in /system/bin and using a symlink to /system/xbin
[Nook Color Android Development] jtbnet:
It should work anywhere in the default PATH as long as it's got the full permissions (7655) set. I've only got one in xbin wih no symlink and all has been well for the superuser app...

root@android:/system/bin # echo $PATH

echo $PATH

/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin

root@android:/system/bin # ls -l su

ls -l su

su: No such file or directory

root@android:/system/bin # ls -l /system/xbin/su*

ls -l /system/xbin/su*

-rwSr-sr-t root root 76232 2011-02-04 09:08 su

-rwSr-sr-t root root 76232 2009-07-31 19:08 su-magic

-rwSr-sr-t root root 26264 2010-08-10 06:52 su-new

-rwSr-sr-t root root 68340 2011-01-31 11:22 su-org
[Nook Color Android Development] NuroSlam:
i might take credit for gaining root, but the rest is all you
[Nook Color Android Development] nswenson:
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.

Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.

Thanks again!

Nathan
[Nook Color Android Development] chhaggerty:
Running busybox from terminal will install all the busybox commands in /system/xbin which should make them available when using adb.
[Nook Color Android Development] jleecong:
Just a suggestion...

Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
[Nook Color Android Development] anbradle:
You were right I tried again and now I am rooted after reboot. Thanks
[Nook Color Android Development] xboxexpert:
Okay... :)
[Nook Color Android Development] slugbug2010:
I am running HC (v2) off a 8gb sd card.

So do I just do these steps to gain root or do I need to partition the sd card first?

Thanks
[Nook Color Android Development] j4mm3r:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".

Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.

You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.

So my advice is to be really careful and understand what you are doing if you decide to install this.

I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.

EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
[Nook Color Android Development] NuroSlam:
agreed, i was just going for root myslef
[Nook Color Android Development] jtbnet:
In

http://howto.ccroms.net/android_project/build/mod/root

I would have though that the purpose of the changes, specifically;

LOCAL_FORCE_STATIC_EXECUTABLE := true

LOCAL_STATIC_LIBRARIES := libc

Were what should resolve the _mktemp not found?
[Nook Color Android Development] chhaggerty:
Howard from MagicAndroidApps.com noted this on the original Honeycomb thread. I'll update the OP to make this clear. Thanks.
[Nook Color Android Development] Mikey:
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?

Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
[Nook Color Android Development] NuroSlam:
yes, at the stands, its just root access. granted i had my own reasons for this
[Galaxy S I9000 Q&A, Help & Troubleshooting] tanjiajun_34:
My phone seem to have a stupid circle marking that does not goes off after a month. I feel like sending my phone to service but i heard that due to the lack of S.AMOLED screen, I might get back a S.LCD screen instead. Is it true? Anyone living in Singapore just recently went to service their phones with screen problems?
[General Questions and Answers] SaintZ93:
Hey all, I could use a little help I'm new to this stuff. I installed the Android SDK all correctly with the correct Java JDK and for some reason when I create a virtual android and run it I get "Error Loading Preferences", is there any way I can fix this to get it to work? I am running Win 7 Ultimate 64-Bit (if you needed to know), thank you for your time and help in advanced.
[General Questions and Answers] TopazAaron:
Yeah, I'd like to know the answer to this also
[General Questions and Answers] DroidFreek:
R u trying to root your phone for the first time or something and what phone is it
[General Questions and Answers] SaintZ93:
ohh no, im not rooting it yet (still have to receive my phone in the mail), but in the virtual server when i create a virtual android I receive that error
[General Questions and Answers] DroidFreek:
Ohh alright then it may just be your computer just wait for the phone to come in
[General Questions and Answers] SaintZ93:
okay, thank you!
[Dell Streak 7] esimpson1:
Hey! I'm a noob on XDA (I've read tons of content, but never posted..) I can't post to the developer forum...

There's instructions there for rooting the Streak7 but for some reason, it doesn't work on mine. It looks like it gets to the point where it does an adb push for the hack, and fails.

When I try to do anything with adb (adb usb, for example) -- it also fails. Not sure what the scoop is on this. I'm anxious to see if anyone else in the US has successfully rooted their Streak7.
[General Questions and Answers] micneeley14:
I have been trying to use ROM Manager for weeks on my DInc so I can try out different ROMs. I successfully rooted my phone, but have been using the stock 2.2 HTC ROM. ROM Manager doesn't recognize my Clockwordmod and I can't use any of ROM Manager's features because it says I need to download Clockworkmod through the app. Whenever I try, the progress bar gets to like 30% and throws an error.

The only I can think might be causing this is I have a refurbished Droid Incredible so it has an SLCD display and I had to use a different recovery image (attached below) than goes on most CDMA Incredibles.

HELP!!!
[General Questions and Answers] UpwardSpiral:
I'm not sure what's going on in your situation, but I would recommend you contact Koush. he made clockworkmod, ROM manager, AND develops cyanogenmod for the incredible, so he would be the man with all the answers. you can get all his contact info from the android market page for ROM manager.
[Desire Themes and Apps] j00e:
Hi every one. Can any one make this theme for my device (HTC Desire with Oxygen 2 RC7)

When i flash it i got bootloop. When i replace all icons in framework-res.apk i got default wifi and connection signal icons (green) but all another very good.

Or how change this icons? (wifi signal, EDGE\GPRS signal, and other)
[Desire Themes and Apps] tekhop:
you mean this?

http://xdaforums.com/showthread.php?t=852023
[General Questions and Answers] elthrawno:
Hi,

Have spent the last hour or so followign various guides and downloading programs to run on my PC, and nothing has worked.

I have been using Links 2SD on my rooted HTC Hero (stock 2.1) but was unaware I had an older version. As I have deleted apps linked to the SD, data has remained on the ext2 partition, because I did not remove the link first.

My ext2 partition is full (I've calculated about 70MB of unaccounted for usage), so would really like to be able to remove some files from it.

Have tried to get to it through terminal emulator, but the $SU resulted in 'permission denied', even though I am rooted and have super user permissions installed.

I am on a Windows7 PC.

Please help, this is getting really frustrating!
[General Questions and Answers] elthrawno:
Could a mod please close this, Root Explorer did the job... and is brilliant!
[General Questions and Answers] men$hoot:
is there any same apps which is free?
[General Questions and Answers] Persianity:
thank you very much!
[Desire Q&A, Help & Troubleshooting] amoslade:
I have my Desire rooted S-OFF running CWM 2.5.0.9 and phoenix 1.3 ROM. I have been trying to upgrade to CWM 3.0.0.5. I tried following directions website and chose renaming my file as update then installing it from recovery. Now the phone will not boot into recovery although it is otherwise fully functional. Any thoughts on how to begin to remedy this? ROM Manager still says I am running 2.5.0.9.

The phone will boot into the FASTBOOT/HBOOT white screen but when I select RECOVERY it hangs at the splash screen. I posted this at the Teamuscellular site but it appears after maintenance I can no longer post over there so posting here in hopes of a faster response.
[Desire Q&A, Help & Troubleshooting] Meaple:
Download this and install the image. Will flash it all for you no problem. Make sure you get the .img.
[Desire Q&A, Help & Troubleshooting] amoslade:
I followed the instructions listed ... even tried custom recovery with unRevoked but I get the same result. Going to try reflashing 2.5 to see if I can get back into recovery at all.....
[Desire Q&A, Help & Troubleshooting] kuroneko007:
Boot into the fastboot screen and flash the new recovery from there via usb.
[Desire Q&A, Help & Troubleshooting] gurpreet3579:
You r soff so you use android flasher to install custom recovery img.
[Galaxy S I9000 Themes and Apps] totano84:
I've been trying to change my Samsung Galaxy S Boot Animation but it seems to be quite the challenge!

I currently use Darky's custom rom (latest 9.1 version based on Android 2.2.1) with Voodoo kernel (the one suggested by Darky himself..thought i don't know why).

I've been googling A LOT and all i could find was bootanimation.zip files and various methods to install them (mainly manual copy with root explorer or cwm) but none of them work and i always get the standard boot animation.

Tried to copy bootanimation.zip both in system\media and in data\local but i still get the same result.

Even these don't work!

http://xdaforums.com/showthread.php?t=869347

The only thing i can do that has some sort of effect is to rename bootsamsung.qmg and bootsamsungloop.qmg.

By doing this a get a black screen instead of the boot animation, so i can assume my phone/kernel/whateverthereasonis only looks for boot animation within these files.

Am i missing something?Has someone had the same issue?

Thanks!
[Galaxy S I9000 Themes and Apps] brewster1990:
i faced the same problem i used the darky rom configurator and flashed back to 8.1 for the cool animation but since 9.2 runs heaps better with the fixed root and stuff i had to stick with it despite the now old and lame nexus boot screen:(

most of the other posts deal with HTC and other phones

i look forrward to the day i can change my boot animation to the droid pissing on an apple
[Galaxy S I9000 Themes and Apps] gurulan:
Droid pissing on an apple THATs fer me. Where can i get it???
[Galaxy S I9000 Themes and Apps] totano84:
This is so sad!I can't move on from the stock galaxy s anim..which is not that bad if you ask me, but i want one of my own!

Even using Darky's and changing the boot animation in the Rom Configurator i still get the same stock SGS anim!

Well..al least i can get rid of that annoying startup sound with something else!
[Galaxy S I9000 Themes and Apps] brewster1990:
lol check out the droid peeing boot screen

http://xdaforums.com/showthread.php?t=693064

also i hope there is an answer for this cuz i've been looking for a while
[Galaxy S I9000 Themes and Apps] racerboy3801:
Try another kernel

Sent from that Green Robot Device with a 4"screen, chewing on some froyo(with an extra .1)
[Galaxy S I9000 Themes and Apps] snapper.fishes:
Didn't darky say that changing the boot animation will break the startup script?
[Galaxy S I9000 Themes and Apps] JJEgan:
I've been trying to change my Samsung Galaxy S Boot Animation but it seems to be quite the challenge!

I currently use Darky's custom rom (latest 9.1 version based on Android 2.2.1) with Voodoo kernel (the one suggested by Darky himself..thought i don't know why).

Dump that rom use Rom Kitchen .

Choose your boot animation .

http://romkitchen.org/sgs/?s=generator

http://xdaforums.com/showthread.php?t=817703

jje
[Galaxy S I9000 Themes and Apps] totano84:
Thanks for the advice!

But why do you say "dump that rom" like Doc's rom is much much better than Darky's?

I'm a new Android user so when i decided to go for a custom rom i did some googling and i found Darky's to be one of the most appreciated.
[Galaxy S I9000 Themes and Apps] Spo0kY:
HOW TO install custom boot animation

Use Root Explorer to place the bootanimation.zip in the /system/media folder. Change permissions to match the other files in the folder.
[Galaxy S I9000 Themes and Apps] sxi200:
I have used both and am sticking with docs + speedmod. Have had less issues with docs rom especially when flashing themes, boot animations etc.