yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] Cypser:
I have 0004 and im running CM7 Build 32. Works fine. So does the camera. To root, i used Unrevoked 3. It does everything automatically for you. There's a kernel that comes with the CM7 builds. If you do root using unrevoked, clockwork is installed for you. it is needed.

A "NAND" is a nandroid backup. It basically backs up the current state of your phone. You should do a nandroid backup everytime you want to flash something or mess with your phone in anyway. For example if you flash a bad ROM, you can boot into recovery and flash your previous ROM using NAND.

AOSP means "Android Open Source Project."

I'll see if i can PM you a link to some basics because i can't post it here...
[EVO 4G Q&A, Help & Troubleshooting] briankurtz79:
I had a problem with my 0003 evo when I went to cm7. The black screen camera. Even bigger problem was once I did a nand restore the camera was still broke. Took it back to stock, still broke. I ended up having to get a new phone. Now I have 0004 with hw 3.70 and hboot 2.10. I'm very nervous about rooting this one but I'd really like to be running cyanogen. Any advice? Do you know what made yours work? Was there an update to cm7 that fixes the camera for the new hw?
[Nook Color General] sasigns:
I Have a NC that was rooted using the auto nooter process. What I was wondering is what is the difference between say that and nookie froyo. What is the best way to go. I love my autonottoered nc the only thing that stinks is the the skipping of the music and the youtube issue (I know thats fixable just havent taken the time).. Anyways thanks in advance for taking the time to answer this
[Nook Color General] RootNewbie:
You may find this thread useful: http://xdaforums.com/showthread.php?t=945261&highlight=nookie+froyo

I'm using a nootered nook. Not having any issues with music skipping or the youtube app. You may need to redownload the youtube apk and uninstall the old one and reinstall the new one. I use Rockplayer lite or the built in music player with no trouble...
[Droid Eris Q&A, Help & Troubleshooting] fefniir:
Great job on CM 7, Pandora works like a champ again! Only two issues I'm having ATM:

1. Whenever I tap the bar in the notification area to switch to storage mode the notification bar FCs. Not too bothersome as I can always go to the recovery console and use it that way.

2. Instead of saying "Verizon Wireless" where it identifies what network I'm on it says T-CDMA 64. Not shure if this is a major problem or not as I don't think anyone has tried to contact me since I flashed.

Anyone have any ideas on how to fix the first one at least?
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
#2 see http://xdaforums.com/showpost.php?p=10489109&postcount=1564
[Droid Eris Q&A, Help & Troubleshooting] DJBillWI:
If its in Ginger Tazz both are known issues based on what I have read in his thread, no fix yet for the FC but there is a zip file called ChangeToVZW in the official rom thread... I think it fixes the banner and roaming if needed.

Hope it helps.
[Touch Diamond, MDA Compact IV General] mikk150:
So, My diamond woke up me this morning, as usual. but problem...

my Diamond's screen didn't respond. and seems like under screen there is like vaccum. whole digitizer is pushed down, haven't had this kind of problem before. How can I get rid of that?

Last night things worked great.....
[Touch Diamond, MDA Compact IV General] grandma90:
You can`t get rid of this problem. It`s a HTC known issue.

A friend who ownes a Touch Pro has the same problem. If he puts his headset to recharge during the night face down , it will cause the interior of the touchscreen to vacuum wich renders his phone operable , but without touchscreen capabilites ( for a short while ).

I replied thinking you left your phone face down during the night. If not , then my solutions is invalid.
[Touch Diamond, MDA Compact IV General] mikk150:
well i left my phone charging whitout pouch onto glass table, so that screen was down.. yes the problem disappeared but about 2-3 weeks my phones screen was dead because here(in estonia) january s temperatures are as low as -30C and screen needed heat to come out of vaccum. it happens occasionally(never happened before). to conclude it I bought new screen and changed screen myself
[Nook Color Android Development] j4mm3r:
Okay so ChainsDD's Superuser doesnt work on Honeycomb. The reason is a (unnecessary?) hack used by the developer to link properly and use the mktemp function.

To fix this, I downloaded the sources and compiled them again, but this time avoiding the _mktemp hack. Build instructions:

(get latest CM sources)
# cd <path-to-project-directory>
# repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
# repo sync

(do a generic build)
# source ./build/envsetup.sh
# lunch full-eng
# make
(take a break, this takes a long time)

(fix the su binary)
# cd system/extras/su
# vi su.c
(make the fix, just replace _mktemp with mktemp and remove its declaration)
# mm
(the new su binary should be available in out/target/product/generic/system/xbin)

The fixed binary is attached with this post. Just install Superuser from the market or install it after downloading from ChainsDD's thread (link above). Push the fixed su binary and away you go!!

# adb push su /system/xbin
# adb shell chmod 4755 /system/xbin/su

Let me know how it goes...

Source Code: https://github.com/j4mm3r/android_system_extras
[Nook Color Android Development] crashdau:
Works great! My Root is up and working! Thank you!
[Nook Color Android Development] chhaggerty:
Updated OP in the other thread to direct people here. Method tested and working perfect. Many thanks to j4mm3r.
[Nook Color Android Development] 18.4009:
How do I make it read/write so I can push the new SU over?

Thanks!
[Nook Color Android Development] j4mm3r:
Thank you, gentle sir!

Usually this works on the HC image

# adb remount

Or the long form:

# adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
[Nook Color Android Development] 18.4009:
Thank you, worked like a charm.

Well, I got the SU pushed over and ran the command to set permissions and rebooted but still no root after reboot.

I just got the nook so I am probably do something wrong.
[Nook Color Android Development] landlocked:
Stuck on root access issue

Many thanks to those who worked on HoneyComb (HC) v4 on eMMC and the rooting solution.

I have root after first flashing to eMMC and checking with terminal. I downloaded and pushed the new SU and still appear to have root -- according to terminal.

The Superuser app opens just fine, but Root Explorer crashes and Rom Manager/CWR complain about not having elevated rights. I *think* I have the latest version of both.

Note: I have only run the two commands above -- and not the list of commands in the OP.

What am I missing here?

Many thanks,

Landlocked
[Nook Color Android Development] 18.4009:
When I type SU in terminal emulator I get an error stating:

"reloc_library[1315]: 1749 cannot locate _mktemp..."
[Nook Color Android Development] j4mm3r:
one way to quickly check if you have it working is to do the following:

- Get to a shell:

# adb shell

(this should give you the "root@android:/ #" prompt)

- Become un priviledged:

root@android:/ # su 1000

root@android:/ $

(the "$" indicates that you are no longer root)

- Try to become root again:

root@android:/ $ su

This should open up the Superuser dialog asking you to allow or deny superuser request, which means that its working as expected. If you need more help then join on #nookolor on irc.freenode.net (see http://nookdevs.com/IRC for instructions for IRC). I can help you there.
[Nook Color Android Development] j4mm3r:
Did you replace the "su" binary with the one in the first post?
[Nook Color Android Development] 18.4009:
I get this error:
[Nook Color Android Development] landlocked:
Thanks for the info, J4mm3r. I can switch from root to standard user back to root on the NC just fine. None of the programs that are supposed to ask for root are prompting me -- as they do on my Droid 2.

I downloaded the new SU (above) and pushed it over using the sample commands.
[Nook Color Android Development] j4mm3r:
I dont think you have replaced the "su" binary with the one that I posted.
[Nook Color Android Development] landlocked:
Sorry, for the clutter, but I have appeared to have made some progress. I used the new SU (above) and repeated the steps in this thread:

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

Rom Manager now properly asks for for SU permission and installed CWR. Root Explorer still crashes, but that may be a file version issue.
[Nook Color Android Development] 18.4009:
Strange I pushed you su over to /system/bin and now I have root :)
[Nook Color Android Development] scuccia:
This is working perfectly. Thank you so much. All my root apps work properly now.
[Nook Color Android Development] lafester:
thanks j4mm3r for the fix :)

now we just need a fresh hcv5 rooted image to play with.
[Nook Color Android Development] nfcrockett:
I did the exact same thing, used new SU and completed the steps in the thread above and just installed busybox from titanium bu. Root Explorer is working fine for me.
[Nook Color Android Development] 360Razir:
j4mm3r you are da man! I have a tear in my eye right now, as I am so happy that this got Superuser working. I had lost root and your fix got it back and also now Superuser is asking for permission on everything I have tried thus far (SetCPU, RootExplorer, Root Check, Quick Boot).

The dev support surrounding HC on the NC is nothing short of spectacular. So many thanks go out to so many dang-smart people out there.

THANKS!! :D
[Nook Color Android Development] j4mm3r:
Glad to be of help...
[Nook Color Android Development] tgallant21:
Many thanks, very easy fix, superuser running and no problems using this method.
[Nook Color Android Development] byproxy:
stupid question... what's the extra 5 for in the 4755 chmod? there's only 3 options for permissions no? owner, group, public? so 475 i get... 4755 i don't. granted, i don't know ADB well.

thanks for the info!
[Nook Color Android Development] donballz:
Sweet hook up, thanks.
[Nook Color Android Development] j4mm3r:
Its a unix thing...

The extra octet is for setuid, setgid and sticky bits.

Ref: https://secure.wikimedia.org/wikipedia/en/wiki/Chmod#Special_modes
[Nook Color Android Development] pdub110:
Noob to Nook.

I'm using the HC v4 on eMMC.

I want to fix su, but can't get my Nook to be seen by my computer, doesn't come up or seen by USB. So can't adb from my computer to my Nook.

I installed terminal emulator but FC on me.

Any other avenues? I copied the su to root of my SD card. but how do i run commands if can't get terminal emulator or ADB to work from my computer.

Another question, i installed ROM manager, can i install CW and do a nandroid on my 16GB SD card? this was done via CW burnt to a SD card so just wondering.
[Nook Color Android Development] kuyote:
Have you tried adbing in while in recovery mode? This is the only way I've been able to get ADB to work. Boot from CWM, mount /system, and mount /data. Then you can use

adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system

adb shell mount -o remount,rw /dev/block/mmcblk1p3 /data

From there you should be able to push the files, and su to verify everything is working.
[Nook Color Android Development] hvuong2:
Root Explorer...

Ok... so I used the new SU file and was able to get it to work... Button Savior requests root and I am able to allow. Root Explorer requests root access and I was able to allow. (had top push to "\system\bin")

However, the Root Explorer force closes on me and states:

"The application Root Explorer (process.com.speedsoftware.rootexplorere) has stopped unexpectedly. Please try again."

Any/all help would be appreciated. Thanks!
[Nook Color Android Development] j4mm3r:
I assume that you have adb working for you, could you paste the output of "adb logcat" around the time that this error happens? Usually it contains additional information about why the application crashed.

I would also suggest trying a different version of RootExplorer to see if it is any better.
[Nook Color Android Development] KiNG OMaR:
This worked for me aswell :D
[Nook Color Android Development] pdub110:
This didn't work, got /system and /data and still can't ADB. I tried to adb kill-server and adb start-server. then did a adb devices, nothing listed.

I probably have the wrong drivers or something, i'll keep googling hopefully i can find a fix.
[Nook Color Android Development] Big-A-Rob:
Worked perfect. Your the man! Thanks.
[Nook Color Android Development] Homer_S_xda:
Anyone else have an issue with the MD5 on the Superuser file in the linked post? There is a discussion on it in that thread.

Homer
[Nook Color Android Development] jtbnet:
I used the superuser apk I already had laying around from using Universal Androot on another tablet... or download one from market if you feel more comfortable then replace the su...
[Nook Color Android Development] SgtSpike:
Found another su binary in /system/bin

I found another su binary in /system/bin

/system/bin must be first in the path so the system executes that one first before the one in /system/xbin that I just pushed over.

Just reran the commands from the OP using /system/bin and I have root :D

Although now I have (2) su binarys on my file system. Is that okay? Should I delete one and symlink to the other just to keep things clean?

BTW: running HC v4 on eMMC

Spike
[Nook Color Android Development] jttraverse:
How about replacing your 'su' with the one in the Superuser zip?

I've also had no luck getting adb working on my Nook, and so I'm curious whether it might be easiest of all to just replace the original 'su' in the Superuser zip with the one you made.

Then wouldn't it be simple to copy the zip to the CWR sdcard, boot to that, and then flash the zip from there? No need to use adb to push anything.

Might that work, or is there some reason it wouldn't?

-JTT
[Nook Color Android Development] jttraverse:
Switching 'su' in the SuperUser zip << no go!

I wondered in my earlier post whether I might get away with simply switching the cooked 'su' for the existing original in the superuser zip file....just as a way to not have to use adb to push the new 'su' file into place.

Fwiw, it did not work. Superuser seemed to install just fine, but other apps can't get SU permissions so I'm going to say that it failed. (sweet idea though, eh :)

..ah well, if only I could get ADB to work.

-JTT
[Nook Color Android Development] j4mm3r:
The reason is simple. The Superuser app needs to have superuser permissions itself to replace the su binary and set it to proper permissions.

One way to automate would be to download the CWR flashable zip from ChainsDD's thread, and replace the su binary in it with the fixed one that I provided, and install it using CWR. I think you may have to turn of signature validation in CWR or something if the install fails.

Haven't tried any of this myself so just saying.

EDIT: I'm sorry that I didnt provide very user/n00b friendly instructions because my post was targeted for developers. Anways, there are plenty of methods of getting root working. Its just important to understand what exactly this fix delivers.
[Nook Color Android Development] beehiveblack:
So, after about 4 hours of getting ADB installed JUST to do this SU push, I have an error I cant figure out...

beehiveblack@beehiveblack-Desktop:~$ adb devices

List of devices attached

xxxxxxxxxxxx	device (just hiding my serial)

beehiveblack@beehiveblack-Desktop:~$ adb shell

root@android:/ # adb push su /data/local

error: device not found

1|root@android:/ #

so what gives?
[Nook Color Android Development] EpicFail236:
skip adb shell. by doing that, you are now working in the device, so push won't work properly.
[Nook Color Android Development] beehiveblack:
Got it thanks... still cant make a backup with CWM.

But atleast i have my root back.
[Nook Color Android Development] jttraverse:
Pushed 'su'..but how to keep root going?

I also found that 'su' had to be pushed to the /system/bin directory to get it to work. But on testing the 'su 1000' command and dropping out of root, 'su' does not get back to root. It pauses for several seconds before coming back "Permission Denied". Has anyone found out exactly why pushing 'su' over does leave you in as root, but apparently isn't permanent?

I'm concerned about not being able to go back to 'su' since the point of the "su 1000" command seemed to be to make sure you could go back to 'su'. If that's true then I'd appreciate any help on what I may be doing wrong.

-JTT
[Nook Color Android Development] j4mm3r:
Did you have the Superuser.apk android app installed? This su binary relies on the Superuser App to show up on the screen to ask the user to either allow or disallow the particular su request. It times out if the user fails to acknowledge.

I'm not sure if I pointed out earlier but in the original HC v4 build, /system/bin/su is just symlinked to /system/xbin/su, so it might not work pushing it to /system/xbin if the symlink doesn't exist. Either way, its basic UNIX, check your PATH environment variable, when you invoke a command at the command line, the first match in your path is the one that gets executed if you hadn't specified the absolute path of the command. Hence, if you have two different "su" binaries installed at /system/bin and /system/xbin, invoking su at the command line will execute the /system/bin/su if /system/bin is in your PATH before /system/xbin.

There is no mystery... just UNIX
[Nook Color Android Development] Chinpokomon:
Or the short form:

# adb shell mount -o remount,rw /system /system
[Nook Color Android Development] Chuck6993:
OK so I just got this to work on my duel booting nook, with honeycomb v04 on partitions 9 and 10.

First I downloaded the su binary on my computer

Then I booted up my nook to honeycomb

Installed Superuser from the market

Then pushed the files to /system/bin and /system/xbin

I hope this helps some people. I had some problems getting it to work when I was just pushing it to /system/xbin. I also wasn't sure if it was going to work because I was duel booting. But after I pushed the files I used Titanium Backup to install a bunch of apps (including angry birds) as a test.

:)
[Nook Color Android Development] CLShortFuse:
I'm the author of SuperOneClick

I'm going to try using this for Honeycomb devices.

This will hopefully allow 0day Xoom rooting without unlocking the bootloader
[Nook Color Android Development] britoso:
hmmm, tried the adb steps without error, yet I dont get prompted to allow/deny a su request. SuperUser shows no apps in its UI/List.

Do I have the right version ?

Update try #2:

Was using a bad su (su-2.3.6.1-ef-signed.zip), works now. :)
[Nook Color Android Development] electrikjesus:
What would i have to do to get ADB to work on the Dual boot HC v4? I have tried everything :-!

Sent from my NookColor running HC X2
[Nook Color Android Development] j4mm3r:
Could you elaborate on "everything"? Actually #nookdevs on irc.freenode.net is a good place to get help.

Usually problems such as yours can only be resolved interactively.
[Nook Color Android Development] britoso:
Three things:

1)make sure the adb custom port is present in %USERPROFILE%\.android\adb_usb.ini

2)Install the latest drivers from the drivers thread

3)If needed

-plug in NC

-uninstall NOOK and Generic Mass Storage device from the device manager

-unplug/replug in your NC, if prompted point it at the new driver folder
[Nook Color Android Development] electrikjesus:
Thank you both, I am still not able, says that I am still nand locked. Hmmmm...

I will pop on to the irc later after work then ;-)
[Nook Color Android Development] xlGmanlx:
hey, its Gman from xoom, just wanted to hook up a thanks for holding my hand updating my xoom!
[Nook Color Android Development] loupnook:
BN media directory access from HC

My goal for getting su working was to get USM working http://xdaforums.com/showthread.php?t=952456 to mount the media directory. I now seem to have su installed and the USM app is working. i can see my BN media directory from my pc now (yay) when using NHC usb to the pc, but i can't browse that directory from my nook HC (boo). So i can't share files between eggclair and HC. I'm a noob to nook and newbe to linux, so i'm assuming it is a permissions issue but don't have enough knowledge on how to change them yet.

Can anyone provide instructions for getting access to the media directory from Nook NC dual Boot?

I have astro and efile installed, but media directory shows up empty.

Thanks.
[Nook Color Android Development] electrikjesus:
Thank you so much for this, I have been fighting with this for some time, You ROCK!!!
[Nook Color Android Development] noobmagnet:
awesome how-to thanks a bunch worked perfectly! If I may add, remember to "adb remount" just in case anyone has problems with the adb console gives an error about not finding the directory...

anyways after this fix busybox installs just fine w00t
[Epic 4G Q&A, Help & Troubleshooting] arvinghost:
Hey guys i am just wondering is it EVER possible to run apple OS on Samsung epic?

android is an open source i know and they already got it to work on iphones but why can't we work apple os or mac os on our samsung epics since both of the operation system are linux based?

If this will never work can you please answer me with a reason and not just NO won't work.

thank you
[Epic 4G Q&A, Help & Troubleshooting] iSaint:
Iphone OS is closed source it will most likely never happen

android is open source whch is why its able to run on the iphone

Please post in the right section next time should be in the

Q&A section
[Epic 4G Q&A, Help & Troubleshooting] gtuansdiamm:
Never gonna happen because ios is not opensource

We are already having trouble getting froyo working properly so start with baby steps

Ota froyo>cm gingerbread>then maybe ios but still never gonna happen

Ur welcome to try porting it if you want
[Epic 4G Q&A, Help & Troubleshooting] swanysto:
Why would you want it? I am sure it can be done, as they have MacOS on regular computers. However, you are going to run into problems with getting radios and such to work, as you will need custom drivers. You will also have to write a driver to allow it to sync with iTunes as that seems to be the only way to get music and stuff on it. And even then you would probably run into trouble, cause iTunes looks for proper OS, otherwise it resets it.

I would say the effort would be way too high for the benefit.
[Epic 4G Q&A, Help & Troubleshooting] || Acer ||:
Right now, there is little to no chance. The closest similarity you can ever get to iOS is the MIUI ROM that is starting to take off in development for the Epic.
[Epic 4G Q&A, Help & Troubleshooting] arvinghost:
thank you guys for the answers. i wish someone can guide me to where to start if i want to start porting the ios and how to write the drivers for it.

i did alot of search and couldn't find anything helpful.

i know ios and mac are closed sources but developers already ported it to work on PC.

Linux ubuntu already can run on samsung epic so would it be easier to port mac os on the epic or ios on the epic?
[Epic 4G Q&A, Help & Troubleshooting] || Acer ||:
Why would you want mac os on the epic anyway? lol

Besides, I don't think mac os would even be optimized to work, especially since it is a closed source, like mentioned above.

The only reason why Linux ubuntu works is because it is based off of the same system, and linux is completely open sourced.