yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] mkasick:
These commands were necessary to get Superuser working with the old joeykrim root method. They're not necessary with this method (or the newly released one-click). In other words, if wifi-tethering is already working for you, nothing further is needed to be done.

I don't actually use TitaniumBackup. I'm not sure why its superuser-requirements would be different from other apps, but I guess it is. The new one-click appears to address this.

Busybox is a suite of "familar" Unix command-line utilites (things like cp (copy), mv (move), ls (list), etc.). It targets embedded platforms by being very featureful, yet relatively small. It's installed and used on a wide variety of embedded devices including wireless routers, print servers, phones, even televisions.

Oddly enough, Android does not include busybox by default. Instead it comes with it's own utility-programs-package called "toolbox" that isn't nearly as featureful, and quickly becomes a pain to use. Some programs, like TitaniumBackup depend on busybox programs/features, and thus require it's installation. It's safe.

The only problem with busybox is that there's not one single version of it. There's multiple builds of it from the same source code with different sets of features turned on and off. In the past, some folks had a version of busybox installed that didn't contain all the features necessary to support TitaniumBackup, so they added the option to install their own version. It's installed in a separate location, so it won't overwrite any version you do have installed, and it's safe to do. But if you've already installed another version of busybox that does work, then it may be unnecessary.
[Epic 4G Android Development] sndtubes:
I did the Jokeyrim method a few days ago. I installed a new kernal and now a new ROM. All seems ok, but ow when I do the "whoami" command in adb shell I get whoami not found. I don't think I'm really rooted anymore. Any attempt to reinstall the Jokeyrim root script results in failure (mostly "device not found" errors). When in adb shell, most commands I type now are either "not found" or "permission denied", so I'm not confident that I'm really rooted now.

Since I have / had Jokeyrim installed, how can I "uninstall" it so that I can use this method of rooting instead? BTW, the newest Clockworkmod is installed and working.

Do I need to flash to stock first? Sorry, but I'm a VERY STOOPID NOOB.
[Epic 4G Android Development] AndroidSPCS:
AWESOME, thank you!!!!! Your thread here has been my bible for rooting the Epic and it works flawlessly. :D
[Epic 4G Android Development] AndroidSPCS:
Yes I recommend you flash back to stock, and then follow the guide here as it works great.
[Epic 4G Android Development] appagom:
http://xdaforums.com/showthread.php?p=8406167#post8406167

beat you to it by 4 days :) ok not exactly in that I tested on the korean cousin, but I suspected it might also be true for epic.. since as you say he developed the trick for the moment. It surprised me that epic also just happened to need it and that our galaxy also just happened to not.

By the way, I have instructions there for how to undo all those links that busybox --install -s puts in your /system/bin directory, for a later date (warranty service or whatever). I couldn't find that anywhere so I wrote a shell hack for it.

edit: not to try to be a jerk.. just to point it works for more devices and may help more people. Actually a few pages later I found a link to some slightly hard to find cyanogenmod web page that showed this exact same method for one of the other devices, fascinate or somethign.. about a couple of weeks earlier.
[Epic 4G Android Development] appagom:
Why don't you try to get temporary root before flashing back. edit:.. ok I see you said you tried to reinstall the joeykrim script, but were you able to/did you try to get the temporary root exploit to work again? If so you're almost there. Why are you flashing roms that don't have root anyway?
[Epic 4G Android Development] appagom:
.

and that may not be entirely true. root kernel yes, but joeykrim. Here are two reasons. Installing superuser doesn't work with joeykrim method. There's a work around but it's equally simple to just copy the su into /system/xbin (remove teh symlink first) and get rid of joeykrims playlogos startup. 2) getting rid of the playlogos (and thus the unecesary ramdisk creation on every startup) avoids potential interfernces with things you might later install. For example, one click lag fix which also uses the playlogos file and actually refuses to install without first restoring it (and breaking the joeykrim method anyway)

ok the 3rd.. basically is just that needing something to be done at every startup can only make root more fragile. (not that you can't get it back by the exploit... but)
[Epic 4G Android Development] AndroidSPCS:
This thread should be stickied. Please!
[Epic 4G Android Development] Pvt WhoOkid:
I'm confused with this part? How do i cd to the temporary directory via windows 7.

adb push rageagainstthecage-arm5.bin /data/local/tmp

when i type this is cmd it says file can not be found, any ideas???!?! Yes im a noob.
[Epic 4G Android Development] Firon:
http://firon.net/xda/one.click.root.exploitv2.3.0.zip

Use this one click if you want to root. :P
[Epic 4G Android Development] Pvt WhoOkid:
that doesnt work for me it says something about permission.
[Epic 4G Android Development] Firon:
Post the error you got. And what platform are you on?
[Epic 4G Android Development] Pvt WhoOkid:
don't want to hi jack this thread but when i use that one click root i get this (Windows 7 32 bit, ultimate)

Exploit made by joeykrim and one click installer made by noobnl and firon
busybox by skeeterslint
Press any key to continue . . .
Copy and run the exploit (may take up to two minutes). Ignore messages about re-
logging in.
If more than five minutes pass, reboot the phone and try again.
Starting adb server...
* daemon not running. starting it now *
* daemon started successfully *
195 KB/s (5392 bytes in 0.027s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2199
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Wait for phone to reconnect...
'ping' is not recognized as an internal or external command,
operable program or batch file.
Mount system as r/w, cleanup old files, do some basic configuration
mount: Operation not permitted
failed to copy 'rootsetup' to '/system/xbin/rootsetup': Permission denied
Unable to chmod /system/xbin/rootsetup: No such file or directory
/system/xbin/rootsetup: not found
rm failed for /system/xbin/rootsetup, No such file or directory
Copying files onto phone...
failed to copy 'su' to '/system/xbin/su': Permission denied
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Permission denied

failed to copy 'playlogo' to '/system/bin/playlogo': Permission denied
failed to copy 'busybox' to '/system/xbin/busybox': Permission denied
failed to copy 'remount' to '/system/xbin/remount': Permission denied
Setting permissions...
Unable to chmod /system/bin/playlogo: Operation not permitted
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/remount: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
link failed Permission denied
Installing busybox...
/system/xbin/busybox: not found
Press any key to reboot the phone
Press any key to continue . . .

now to keep on topic, any ideas on how to "cd" or whatever it is??
[Epic 4G Android Development] cocoabro:
I tried using the 1-click method with absolutely no luck. This one worked first try.

Assuming you've got the ADK, get to the directory where you've saved it. For me, I saved it in C:\Android. So, when I open the cmd window, I type "cd.." [enter] twice to get to the root C: directory. Then I type "cd Android/tools" [enter] to get to the tools directory where adb is stored. I put the files that we need in that tools directory. Then, it's just copy/paste into the command line for everything that OP listed.

BTW, the [enter] that I showed above indicates to press the enter key, not type "[enter]". Also, to get the past command in the cmd window, click the icon in the upper left of the window, select edit and then paste. Lastly, you need to navigate to the directory where adb is stored whenever you want to call adb-related commands.

(I'm no expert in command line if anything that I've mentioned seems remedial :) )
[Epic 4G Android Development] Pvt WhoOkid:
Ok i know i got ANDORID sdk installed but what is ADK and where do i get it?
[Epic 4G Android Development] cocoabro:
I believe it's the same thing (ADK = Android Dev Kit)
[Epic 4G Android Development] cocoabro:
Permanent Root?

So I just restarted my phone, and I no longer have root. Any thoughts?
[Epic 4G Android Development] appagom:
@cocoabro

First after you reboot, root isn't automatic anymore as it was with teh exploit, maybe you know that.. Anyway, after

adb shell

you need to type "su"

(superuser should pop up and ask if want to allow root acesses.. only the first time)

Then you get #

If that works you have root.

But if that's not working.. simple, just get temporary root again with rageagainstthecage. It should still be there so need to re-push it, just re-run it. Then find out what went wrong.

ls /system/xbin/su

ls /etc/group

ls /etc/passwd

Those files with correct permissions are the ONLY things needed for root to work.

if su is there, but group and passwd are not.. That means superuser installation didn't work. I set these files up by hand(just as joeykrim did), not using superuser. You can see my link on the last page to find those instructions but it seems superuser is doing the trick for people here.

If they are all there, then it must be a permissions problem. So try again setting the permissions (the chmod command). Unfortunatley until you install busybox, the built in ls is nearly useless and doesn't have options (at least not the ones I know) to list permissions. Since superuser overwrites the pushed su though.. it still indicates maybe something went wrong with superuser installation.

edit: one other thing.. once or twice I've found superuser to be flaky about popping up its allow root box. Example, run titanium backup and mine just says.. the phone is not rooted. I hit "problems" and ask it to install busybox(it's own private version).. then superuser kicks in and asks for permissions as it should. Click yes.. and TB has root from then on. A couple of other times I've noticed the same kind of quirkiness with superuser.

P.S... the output above from whookid one click root, incorrectly credits joeykrim with the exploit. He must think I hate him cause I've said this before,.. I don't but, he did not create the exploit. Actually he didn't create the permanent root method either. He just put it all together. See his page for credits, which are correct there.
[Epic 4G Android Development] cocoabro:
@ appagom

First of all, thanks for taking the time to write all that up. Unfortunately, I still can't get it to keep root past a reboot. I followed your instructions from your post Root and and everything else for shw-m110s and just about anything else. Also I entered the ls /etc/group and ls /etc/passwd; both were fine. I never got the popup about superuser root access until I ran TitaniumBackup (after all the other stuff). But, once I rebooted, I no longer had root. Any ideas?

I did a backup of my device before trying any of this - should I restore it an try again?

Thanks.
[Epic 4G Android Development] mkasick:
Do you have busybox installed?

If not, download the one-click installer package, extract "busybox" from it and temporarilly install it with adb. You don't not need root for this, so don't worry about that:

adb push busybox /data/local/tmp
adb shell chmod 755 /data/local/tmp/busybox

Now, run the following in an adb shell (again, you don't need root). If you didn't temporarilly install busybox (you had already installed it to /system) then use "busybox" instead of "/data/local/tmp/busybox" in the lines below:

/data/local/tmp/busybox find / -name su -exec /data/local/tmp/busybox md5sum {} \; 2> /dev/null
/data/local/tmp/busybox find / -name su -exec ls -l {} \; 2> /dev/null

and report the exact output.

Once done you can remove the temporary busybox:

adb shell rm /data/local/tmp/busybox

I suspect you might have multiple "su"s installed, and the first one in your path isn't Superuser's.
[Epic 4G Android Development] cocoabro:
@mkasick

once I hit enter after /data/local/tmp/busybox find / -name su -exec ls -l {} \; 2> /dev/null, the following appears:

/data/local/tmp/busybox find / -name su -exec ls -l {} \; 2> /dev/null

eafd6ce052f80a7f217d2e6033b2ce15 /system/xbin/su

eafd6ce052f80a7f217d2e6033b2ce15 /system/bin/su

$ -rwsr-xr-x root shell 26264 2010-08-18 01:44 su

lrwsrwsrwt root shell 2010-10-19 03:14 su -> /system/xbin/su

$

Diagnosis? Thanks!

This whole exercise is making me wish I would've pursued Linux a decade ago when some of my friends were tinkering with it :) Oh well, 20/20.

edit: - I suppose the two directories with su listed confirm your suspicion... now to know how to fix it...
[Epic 4G Android Development] appagom:
yeah.. I would add superuser last pesonally to diagnose. You don't need superuser to have root. It just replaces your su with one that protects root with the popup.

As for your problem... it actually sounds like the orignal reason why joeykrim made his less simple version in the first place. I wonder if it's related to ROM versions. Try the joeykrim method. google "joeykrim permanent root sdx"

P.S. I assume by not having root, you mean su doesn't work from adb. That should always be the first test.

so in my aproach therre is ONE su in /system/xbin and the one in /system/bin is just a link to that (or other way around). Not a problem. Superuser finds and overwrites the real one and the link stays ok. I don't know if two are needed. I can't see why really, but I followed some precedent.

Anyway.. if mkasick is right.. try su from adb.. If that works and superuser doesn't, maybe he's right.

try calling su explicitly by path

/system/bin/su

if that doesn't work it's probably the setuserid bit got lost. "busybox ls" (if you have busybox) or regaining temp root and chmoding again will confirm. If this is the case... it's a joeykrim problem... really I should say leshak problem.. lesserr known (maybe?) but he developed the work around.
[Epic 4G Android Development] appagom:
by the way.. I think superoneclick is working on epic (google or search it). For any of you are aren't having fun working it out by hand.. give it a try. It uses the simpler non joeykrim method of the OP here. When things still don't work though.. by hand is the way to go.

edit: I fogot coco said he already tried that

edit:.. but with joeykrim method you're still going to have issues with installing superuser. For solution, click my link.. look one post up.. click the link there.(too lazy to chase the link myself right now)
[Epic 4G Android Development] mkasick:
It's a problem with the Superuser program. Anytime the su binary can't launch the Superuser task it will return "Permission denied".

You have one version of "su" installed, and it's the most recent version for Superuser. "su" itself looks setup correctly, it's owned by root:shell and has the setuid bit set. You also have a (superfluous?) symlink from /system/bin/su to /system/xbin/su. This should be harmless, and you can verify by running "/system/xbin/su" directly and confirming it doesn't work that way either. You could delete /system/bin/su, but some root-requiring programs hardcode su's path and might assume only "/system/bin/su" exists, I'm not sure.

How did you install Superuser.apk? Did you do "adb install Superuser.apk" or download it from the Market?

If either, remove the program (Settings -> Applications -> Manage applications -> Superuser -> Unistall). Then reinstall Superuser.apk (don't need to be root) either via "adb install", selecting Superuser.apk from a file manager, or just downloading it from the Market.

If it was "one click root" that installed Superuser.apk then you can't reinstall it without root. But I suspect the program itself is probably fine. Try clearing its settings (Settings -> Applications -> Manage applications; Menu -> Filter -> All; Superuser -> Clear data).

Also, when you run "su" from an adb shell, make sure your phone screen is awake and unlocked. This is where the Superuser Request window pops up. I've found that if you run "su" when the screen is off you'll never get the request window and it won't work.

His "ls" output shows the setuid bit is there (the "s" in -rwsr-xr-x) so that's not the problem. Also, the lost-setuid-bit bug has, to my knowledge, never appeared in any of the Galaxy S devices.
[Epic 4G Android Development] appagom:
I agree 100%. I missed the ls output.

As mkasick said... you can't reinstall the superuser's su without a mostly working su!, but you can reinstall the package and configurations which may be enough. Personally I wouldn't play with that too long before just...

uninstalling superuser entirely (as suggested), regaining temporary root. Remove any /system/bin/su and /system/xbin/su files or links. Repush non-superuser su (the way the OP suggests so as not to confuse things with possibly different locations from my method). Set up /etc/group and /etc/passwd by hand (For this though you can see my if it's not in the OP) without installing superuser. Set permissions etc...

Reboot and see that it works. It will, and you'll feel better and can say "Yay, I got permanent root".

Then on to the task of securing it with superuser by reinstalling superuser again. If it breaks again at least you'll feel good about where you stand. To me when there's problems.. it's nice to break it down, and get one victory at a time.
[Epic 4G Android Development] appagom:
To mine too except for joeykrim's own testamony that the workaround was needed for the epic. Seems more and more likely that needed simply means "worked".
[Epic 4G Android Development] DRockstar:
mkasick,

I just wanted to say thanks for your original post in this thread...

At the time I was just finishing up my own all in one root and recovery, and based on this topic... I named my own solution the Simple One Click Root. It's a windows, mac, and linux script, feel free to check it out. It's kind of a behemoth all in one batch and bash script that provides root, clockwork mod, kernel, uninstaller, and sdx app remover all in one menu and lets you pick what you want to do. Took me what seems like forever to get it done to my satisfaction.

I remember being stoked that playlogo didn't have to recopy root every boot... anyways, figured I'd let you know
[Epic 4G Android Development] cocoabro:
@appagom and @mkasick

Thank you both for your continued help. I haven't gotten to try again since the other day as I haven't had my USB cable with me. I'll definitely try your latest directions tomorrow and let you know how it turns out.

Anyway, I installed Superuser by the "push" command so it doesn't show up in my list of applications (via post #4). How would I remove it?

Also, I'm checking for root with "su" through ADB and looking for the "#".

Thanks again.
[Epic 4G Android Development] wj0t:
does this work for the dk28?
[Epic 4G Android Development] DRockstar:
If you're asking this question, then use the one click root or the all in one... they both use this method, and they both had to be rewritten so that it would work in froyo... basically, the exploit is called from a root.sh script that is run from the phone, and a delay was added to allow time for the exploit to complete.

I don't think the original post instructions will work on froyo because of this.
[Epic 4G Android Development] appagom:
The OP method certainly does work in froyo and before the one clikcs did work exactly for this type of reason. (generically works anyway, maybe it's missing some things like setting write mount and disconnecting and waiting to see a prompt and trying again) Tiny technical glitches, like a delay (how would the user not notice to wait to enter the next command, ok yes you need to disconnect and reconnect, so that's missing in this brief version, personally I ahve 2 scripts, one for temproot and one to install root) or needing to repeat a step and such are quite obvious when you understand it and do it by hand, whereas they just break wonder one clicks for a few weeks. I like z4root used it quite abit, but it broke with 2.2.1 seemingly because the app itself doesn't run properly, nothing to do with the exploit. So we are back to doing it by hand in Korea corner and people there have managed (because writing a good guide took far less time and is less fragile than writing some multiplatfrom one click wizard for every device, and generates fewer rediculous questions actually). I'd rather see more education and less "let us handle the stuff inside the box". The "BIG FAQ ON ROOTING ECT" in I9000 doesn't even mention rageagainstthecage in like a 20 page (printed) FAQ on rooting and ROMS.

I have similar, although more thorough maybe instructions linked from the first page of the Korean galaxy S shw-m110s thread stickied in I9000 general. I won't plug a link. But you can find it if you want. Other things have come and gone and been nice and convenient, but adb has ALWAYS done the job. Ilike the one clicks and they should be the first advice for people who barely know what adb is or have no clue what "ls" means, but writeups like the one here should be linked from the first page of every one click thread. Now I'm repacking kernels though and frankly google should fix this massive security hole (rageagainstthecage) and leave us with just things requiring physical access to the phone, three buttons or Odin/ heimdall(which I like especially in linux). We'd still be ok.
[Vibrant Q&A, Help & Troubleshooting] VibrantOwnr:
Can someone post an umodified build.prop file from the JI6 release?

Thanks
[Legend General] gallery:
Hi Everybody

From today evening onwards my HTC legend Android Market has paid applications

also has automatic update feature in market
[Legend General] Kwen:
Automatic update...that's a 2.2 feature

Are you using a stock room or Azure based? Have you received any OTA update?

If stock, what's your ROM version?? :eek:
[Legend General] -MojaV-:
Here in Norway we got paid apps today, and with that the auto-update function in market. Got the Legend with stock 2.1 and was suprised to see it as I also thought this was a 2.2 only function.
[Legend General] Firecold:
Same here in Russia. The question is - how they managed to update market.apk w/o any kind of notifications/pop-ups/downloads/etc?
[Legend General] acid74:
Mine shows the paid apps,no auto update tho...using stock rom here in Norway.
[Legend General] zabaknilesh:
I am from India....sorry but no Auto update feature...

yes paid access to applications is available now and showing in indian currency..no need for the market enabler now!!

Update: Yess automatic updates are now available to all 2.1 users for Android!!!
[Legend General] rajasyaitan:
Lucky for you guys. Still stuck with no official Market support.
[Legend General] gallery:
Still using stock Rom

No notifications for update to Android market

Still in eclair 2.1 stock Rom
[Legend General] gallery:
Android market also has now with widget support
[Legend General] gallery:
I am using only the stock Rom