Superuser su binary - Epic 4G Q&A, Help & Troubleshooting

I've noticed that the su binary installed by superuser doesn't survive a reboot. Anyone else have this problem? Any fixes?
Sent from my SPH-D700 using XDA App

Same here. Have to re update after each reboot
Sent from my SPH-D700 using Tapatalk

same here, had to update the binary too

How do you update the su?

Launch superuser, go to settings and scroll to the bottom.
Sent from my SPH-D700 using XDA App

I've found 3 su:
/system/bin/jk-su (original from the oneclick/permanent)
/system/xbin/su (symlink to /sdx/su)
/sdx/su (superuser updates this one)
Superuser does not update /system/bin/jk-su so I decided to.
So far its working.
Sent from my SPH-D700 using XDA App

dangdang said:
I've found 3 su:
/system/bin/jk-su (original from the oneclick/permanent)
/system/xbin/su (symlink to /sdx/su)
/sdx/su (superuser updates this one)
Superuser does not update /system/bin/jk-su so I decided to.
So far its working.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
How did you update it yourself?

Here's what worked for me. Keep in mind I am rooted using oneclick 2.2.4 which comes with busybox and remount scripts.
1. Update the su binary using superuser.
2. Launch a terminal (I use better terminal emulator pro)
3. Run 'su' from the terminal
4. Mount system rw with 'remount rw'
5. Remove jk-su with 'rm /system/bin/jk-su'
6. Copy the su binary superuser installed with 'cp /sdx/su /system/bin/jk-su'
7. Reboot and it should survive.
Notes:
Do not include single quotes when running the commands.
I'm paranoid about permissions so as root in terminal I ran:
chown root.shell /system/bin/jk-su
chmod 755 /system/bin/jk-su
To match the permissions of the removed jk-su. I'm not sure if this was necessary.
I haven't tested using adb yet so I don't know the steps.
Sent from my SPH-D700 using XDA App

Code:
#cp /sdx/su /system/bin/jk-su
cp: not found
the last part does not work (i have the same root method)
i have to re-root the phone when i get home today. but i will try to move the updated binary with root explorer instead of the command line.

Replace 'cp' with 'busybox cp'.
Sent from my Android using CDMA

dangdang said:
Replace 'cp' with 'busybox cp'.
Sent from my Android using CDMA
Click to expand...
Click to collapse
will try I had the same issues

dangdang said:
Here's what worked for me. Keep in mind I am rooted using oneclick 2.2.4 which comes with busybox and remount scripts.
1. Update the su binary using superuser.
2. Launch a terminal (I use better terminal emulator pro)
3. Run 'su' from the terminal
4. Mount system rw with 'remount rw'
5. Remove jk-su with 'rm /system/bin/jk-su'
6. Copy the su binary superuser installed with 'cp /sdx/su /system/bin/jk-su'
7. Reboot and it should survive.
Notes:
Do not include single quotes when running the commands.
I'm paranoid about permissions so as root in terminal I ran:
chown root.shell /system/bin/jk-su
chmod 755 /system/bin/jk-su
To match the permissions of the removed jk-su. I'm not sure if this was necessary.
I haven't tested using adb yet so I don't know the steps.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have this exact same problem on my Samsung Moment (have to update SU every reboot).
The directory structure seem a bit different. For example, there's no /system/bin/jk-su (in fact, if I find / -name 'jk-su' I get no results at all).
I am poking around the directory structure trying to figure out where to find the source and destination su files that I'm going to have to overwrite and I can't seem to figure which is which. Does anyone have any idea how to do the functional equivalent of dangdang's post on a Moment?
Thanks!

Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?

k0nane said:
Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?
Click to expand...
Click to collapse
Because people like to bring out the bat again and continue to beat the remaining not decomposed guts out of the horse...
lmao

I was about to say. WTF is everyone talking about SU not surviving a reboot /noodlescratcher
davidrules7778 said:
Because people like to bring out the bat again and continue to beat the remaining not decomposed guts out of the horse...
lmao
Click to expand...
Click to collapse

k0nane said:
Um... Why did you feel the need to necro this INCREDIBLY ANCIENT thread?
Click to expand...
Click to collapse
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.

lol. i hear ya!
DamienWind said:
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.
Click to expand...
Click to collapse

DamienWind said:
It was the most relevant post after doing a search. Forum etiquette blows my mind. I can only imagine how much "use the search feature!" I'd have gotten if I'd have made a new post about this. Oh well, I tried.
Click to expand...
Click to collapse
most likely SU is built into your kernel and short of rebuilding or repacking your kernel you cant update it..

I have a samsung galaxy s I9000 running Gingerbread will this work for me..?

Related

root

Ok, to save some people some time here for rooting and opening it up to non-market apps on your bravo, and probably any motorola AT&T device.
1. Z4Root is the easiest way to root since you just get it from the market. One buttons press then done.
2. to modify the settings.db in /data/data/com.android.providers.settings/databases/ use the SuperOneClick which you can get here
http://forum.xda-developers.com/showthread.php?t=803682
3. I used root explorer, which you can get from the market and just edited the /system/etc/motorola/com.android.providers.settings/secure.mkitso
and /system/etc/motorola/com.motorola.android.providers.settings/settings.mkitso files in place. Copying them, editing them, and chmodding them didn't seem to work for me for whatever reason. The way I did it, you don't have to do anything other than edit the file in text editor and factory reset your phone.
Rooted mine the other day using the Droid 2 root method at modmymobile.
I can't post links yet, so here's the instructions:
dragonius said:
Setup:
- Make sure you have ADB installed properly and the latest Motorola drivers.
- Download attached archive
- Extract to a directory, I used C:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open Command Prompt (Start - Run - cmd - Enter)
- adb devices (to verify the connection)
- cd C:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- Let the process run until the prompt returns you to C:/Droid2Root (be patient, it takes a while, but does happen. If not, reboot phone and try again.)
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
Once you have achieved root, to update the Superuser.apk to the latest version, run these commands:
- adb shell
- su
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- rm /system/app/Superuser.apk
- pm uninstall com.noshufou.android.su
Then search on the market for Superuser and download the one by ChainsDD. Confirmed working on latest Droid2 2.2 OTA & the new leaked 2.3.15 OTA.
Click to expand...
Click to collapse
On the Bravo its not "PC Mode", I think its "Portal and Tools" Other then that, everything worked flawlessly.
Thanks, a bunch. I actually used the Z4Root app from the market and it worked flawlessly. Now I'm just trying to figure out how to allow non market apps and maybe get an overclock going on this. any suggestions?
Grape Drank said:
Thanks, a bunch. I actually used the Z4Root app from the market and it worked flawlessly. Now I'm just trying to figure out how to allow non market apps and maybe get an overclock going on this. any suggestions?
Click to expand...
Click to collapse
I just bought this phone for my younger brother and I'm impressed. I have a Droid Incredible and its just as smooth. I also verified that the Z4root app from the marketplace roots the phone.
Did anyone get it unlocked yet
Yeah, it's a great phone. I'm trying to get the settings.db thing to work so we can install non-market apps, but it doesn't seem to be working. I got the db modded and put back in place, but I still don't see the option in the application manager screen.
IMO this is the #2 android phone on AT&T next to the captivate. that SAMOLED is great and the GPU on the captivate is top notch.
Anyway, if anyone can assist on the non-market app thing that would be great.
So far, I have rooted with Z4Root, removed the AT&T crapware, installed the MarketAccess to get around the stupid AT&T market filters. Last thing is to get the non-market apps going. After that it's a matter of waiting for this device to gain popularity and some custom ROMs.
I managed to get my Bravo to install non-market apps using:
1. SuperOneClickv1.5.5-ShortFuse
2. Click Here
I am not sure if just step 2 alone would be OK though.
Remember, you have to factory reset after you have finished with step 2.
Good Luck!
I edited my original post with the steps and tools I used to get the phone rooted and non-market unlocked.
Wait so can some explain how to unlock it?
Sent from my SGH-T959 using XDA App
cooldead said:
Wait so can some explain how to unlock it?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
If you mean "unlock" as in able to use the phone on a different carrier no one has posted how to do it yet. The OP meant allowing non-market apps.
Got cha, thanks.
Sent from my SGH-T959 using XDA App
cooldead said:
Got cha, thanks.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
No problem
I'm lost here,
Downloaded z4root onto my phone because it's not available on Market,
but it won't let me run the z4root.apk because it's not a market app.
total newb here, so any help would be appreciated.
thanks
Nevermind, got z4 to install using Android Central's Sideload Wonder Machine, then rooted my phone no problem, installed TiTanium backup, and rid of the bloatware.
Phone processes quicker, from settings, fetching list of running apps, data manager, manager etc, list loads much quicker now.
How did you go about getting rid of the garbage-ware? curious.
Hi I'm posting here in hopes to get a response because I cannot seem to get a response on the S1C forum. I rooted with z4root but cannot get non market apps enabled using S1C. I have .net framework 4.0 using vista and the motorola drivers from their site. I get as far as "getting mount path" and then it fails. Am I missing something or should this be working for me. And if so, what could be the problem? Many thanks.
SideloadWonderMachine worked for me, give it a shot. 2 clicks to add an app. Pretty foolproof (I am a fool).
Rooted my Bravo using adb install z4root (linux PC) then ran z4root from phone, worked great.
just rooted Bravo using Droid2Root files and manual ADB commands, from the thread that Gumpo10k shared in this thread, up above. Worked great, now I need a good 2.2 ROM to get tethering working.

[DUMP] SGH-T989 System Dump

SGH-T989 System Dump (Odexed)
Here you guys go, a system dump, thanks to luckyduck69.
luckyduck69 said:
dump: http://dl.dropbox.com/u/21231693/T989odex.zip..
Click to expand...
Click to collapse
I have also mirrored this on my website, here.
I will have it deodexed here later tonight.
Reserved.
as;dflkjas;ldfkja;sldfkj
So, the dump would be useful if one needed to put the phone back to just the way it was out of the box, correct? One could use it with Odin to fix, say... a soft brick?
Ty for this!! this means what exactly? easier to root and set up for odin?????curious
movieaddict said:
Ty for this!! this means what exactly? easier to root and set up for odin?????curious
Click to expand...
Click to collapse
once it deodexed... the real def fun begins as far as modding or cooking up personalized roms.
but we really need to get a modded kernel somehow and get root. that must be our main priority cuz nothing else matters without it. maybe someone has a trick up their sleeve... i hope.
Awesome........ now the ball gets rolling
Ty sir Please remove all the ridiculous t-mobile bloat.
Ty luckyduck!
sence im at school and cant up u all my original build ill root this for u all and upload it back to my sf page
RaverX3X said:
sence im at school and cant up u all my original build ill root this for u all and upload it back to my sf page
Click to expand...
Click to collapse
Nice greatnews and good to see familiar faces from the gs4g thanks raver
Sent from my SGH-T989 using xda premium
Raver always comes thru so glad to see him here!
Sent from my SGH-T989 using XDA App
Ty to all of u guys!! cant wait
Hey fellas i was on sammy's open source site yesterday and nothing was there for the SGH-T989 and today there is an SGH-T989 open source.zip file up on the site just in case this helps in any way with getting things going with rooting this bad mutha!
https://opensource.samsung.com/
Sent from my SGH-T989 using xda premium
Was this dump made using "adb pull"? If so, it's next to worthless for the purposes of building a prerooted system image - no permissions, no symlinks.
Someone needs to dump system using tar. I have attached a binary of busybox (which includes tar) compiled using the instructions given at http://arighi.blogspot.com/2011/08/install-busybox-from-source-on-samsung.html
Extract it from the zip and install it as follows, I am assuming that whoever does the dump is comfortable with ADB:
Code:
adb push busybox /data/local/tmp/
Then start an adb shell or an Android Terminal Emulator session, and within it:
Code:
cd /system
/data/local/tmp/busybox tar czvf /sdcard/system_dump_t989.tar.gz *
Then grab /sdcard/system_dump_t989.tar.gz and upload it here.
To avoid having 308403434 different people do this, I suggest you guys name a volunteer
IMPORTANT: If the attempt to tar up /system above gives any errors about access denial or permissions, post the name of every file that was a problem.
Would love to but at work atm.
Sent from my SGH-T989 using xda premium
Entropy512 said:
Was this dump made using "adb pull"? If so, it's next to worthless for the purposes of building a prerooted system image - no permissions, no symlinks.
Someone needs to dump system using tar. I have attached a binary of busybox (which includes tar) compiled using the instructions given at http://arighi.blogspot.com/2011/08/install-busybox-from-source-on-samsung.html
Extract it from the zip and install it as follows, I am assuming that whoever does the dump is comfortable with ADB:
Code:
adb push busybox /data/local/tmp/
Then start an adb shell or an Android Terminal Emulator session, and within it:
Code:
cd /system
/data/local/tmp/busybox tar czvf /sdcard/system_dump_t989.tar.gz *
Then grab /sdcard/system_dump_t989.tar.gz and upload it here.
To avoid having 308403434 different people do this, I suggest you guys name a volunteer
Click to expand...
Click to collapse
"/data/local/tmp/busybox tar czvf /sdcard/system_dump_t989.tar.gz *" gives permission denied error
/system itself? That's VERY odd.
zaventh is working this now, talking with him on IRC
Edit: Looks like adb push didn't make busybox executable, as I mentioned in IRC:
Code:
adb shell chmod 755 /data/local/tmp/busybox
Finally the ball gets rolling
Sent from my SGH-T989 using xda premium
Entropy512 said:
Was this dump made using "adb pull"? If so, it's next to worthless for the purposes of building a prerooted system image - no permissions, no symlinks.
Someone needs to dump system using tar. I have attached a binary of busybox (which includes tar) compiled using the instructions given at http://arighi.blogspot.com/2011/08/install-busybox-from-source-on-samsung.html
Extract it from the zip and install it as follows, I am assuming that whoever does the dump is comfortable with ADB:
Code:
adb push busybox /data/local/tmp/
Then start an adb shell or an Android Terminal Emulator session, and within it:
Code:
cd /system
/data/local/tmp/busybox tar czvf /sdcard/system_dump_t989.tar.gz *
Then grab /sdcard/system_dump_t989.tar.gz and upload it here.
To avoid having 308403434 different people do this, I suggest you guys name a volunteer
IMPORTANT: If the attempt to tar up /system above gives any errors about access denial or permissions, post the name of every file that was a problem.
Click to expand...
Click to collapse
Dump using this method available here: http://www.multiupload.com/MKCNJTUTRW
zaventh said:
Dump using this method available here: http://www.multiupload.com/MKCNJTUTRW
Click to expand...
Click to collapse
Another dump ---- http://www.multiupload.com/424YLKAN90

[Q] How to get the from R800x from ADB Root to Phone Root [Stock]

Forgot to add this to the title: [BOOTLOADER LOCKED]
Hello Fellow XDA'ers,
Using a slightly formatted zergRush (modified by Ch4lky, part of the revolutionary team) i was able to get ADB root!!
Now how do i get from adb to the phone rooted?
Thank you, in advanced!
Note: zergRush (from Ch4lky) is attached.
paxChristos said:
Forgot to add this to the title: [BOOTLOADER LOCKED]
Hello Fellow XDA'ers,
Using a slightly formatted zergRush (modified by Ch4lky, part of the revolutionary team) i was able to get ADB root!!
Now how do i get from adb to the phone rooted?
Thank you, in advanced!
Note: zergRush (from Ch4lky) is attached.
Click to expand...
Click to collapse
I'll test this out later. Some other rooting tools might work with the adb root like SuperOneClick or UniversalAndroot
CrimsonSentinel13 said:
I'll test this out later. Some other rooting tools might work with the adb root like SuperOneClick or UniversalAndroot
Click to expand...
Click to collapse
Tried SuperOneClick, gingerbreak and universalandroot
UniversalAndroot:
Developer of that one stopped updating with froyo, I got nowhere (1.6.2 beta 5) if you have a better version, go for it
Gingerbreak: I ran outta patience with this one and just killed it after 5ish minuts of running it
SuperOneClick: Claims to get root (installed busybox, and superuser) when I reboot I loose root.
Tried chmodding su, but that didn't work out
paxChristos said:
SuperOneClick: Claims to get root (installed busybox, and superuser) when I reboot I loose root.
Tried chmodding su, but that didn't work out
Click to expand...
Click to collapse
I know that SOC has 3 ways to root. Doesn't shell root stick after a reboot with a script that's installed?
Edit: Nevermind... I realized that zergRush does that.
Just tried SOC again, this time using root checker, it says i'm rooted, but rootchecker says otherwise...
So far we're at ADB rooted, so we can remount as whatever we want, but past that, what can we do?
How does all of this work? i wouldn't mind having ADB root, at least its something better then no-root
---------- Post added at 04:51 PM ---------- Previous post was at 04:33 PM ----------
Wouldn't you just push the "su" commands to the correct folder to gain root?
Tried that, no dice
My guess is that it's not changing the /system folder to rw (read write) on boot instead of the default ro (read only)
Sent from my R800x using XDA App
If you change how the OS mounts at boot through fstab or the equivalent in Android, it might work.
Well couldn't you just have it like a tethered root? like every time you restart your phone just set the /system folder to rw? I really don't know because i'm still learning ADB.
Db0y505 said:
Well couldn't you just have it like a tethered root? like every time you restart your phone just set the /system folder to rw? I really don't know because i'm still learning ADB.
Click to expand...
Click to collapse
It's a horrible, horrible loop, to change the /system to rw, you need to have root. To get root you need a way to change /system to rw...
Right now we have a temporary root that only works in adb, but goes away once the phone is rebooted...
I have perma-root now.
remounted /system [adb remount]
pushed su to /system/bin & /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
installed SuperUser through adb
installed BusyBox (if it doesn't show up) via a Market app
Ran SuperUser
installed Insecure ADB via APK & then ran it on phone, system reboots
Reboot has root & rooted insecure adb
All apps that need root have no issue. I'm looking into getting sudo added to the mix, too.
CrimsonSentinel13 said:
I have perma-root now.
remounted /system [adb remount]
pushed su to /system/bin & /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
installed SuperUser through adb
installed BusyBox (if it doesn't show up) via a Market app
Ran SuperUser
installed Insecure ADB via APK & then ran it on phone, system reboots
Reboot has root & rooted insecure adb
All apps that need root have no issue. I'm looking into getting sudo added to the mix, too.
Click to expand...
Click to collapse
you good sir, are my hero!
Do you want to post how you got this in The developers forum?
You are a hero indeed, but could you just make the instructions slightly more "noob" oriented?
You sir are awesome!
---------- Post added at 06:25 PM ---------- Previous post was at 06:04 PM ----------
Ok i just did this and i have root! Thank you so much!
Cl8rs said:
You are a hero indeed, but could you just make the instructions slightly more "noob" oriented?
Click to expand...
Click to collapse
I'll be within on it once I get home, right now I'm in class until 9
Sent from my R800x using XDA App
paxChristos said:
I'll be within on it once I get home, right now I'm in class until 9
Sent from my R800x using XDA App
Click to expand...
Click to collapse
You're the best bro!
CrimsonSentinel13 said:
I have perma-root now.
remounted /system [adb remount]
pushed su to /system/bin & /system/xbin
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
installed SuperUser through adb
installed BusyBox (if it doesn't show up) via a Market app
Ran SuperUser
installed Insecure ADB via APK & then ran it on phone, system reboots
Reboot has root & rooted insecure adb
All apps that need root have no issue. I'm looking into getting sudo added to the mix, too.
Click to expand...
Click to collapse
If you can already use adb remount, you dont need to install insecure adb because you already have it
I'll post my steps in an hour or so w/o the insecure adb step, too, in the dev section. If paxChristos gets around to it before me, I would appreciate the recognition.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=1312859
CrimsonSentinel13 said:
I'll post my steps in an hour or so w/o the insecure adb step, too, in the dev section. If paxChristos gets around to it before me, I would appreciate the recognition.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=1312859
Click to expand...
Click to collapse
No worries man, it's all you.
I need to do some "housekeeping" to get my phone to work with it,
Congrats on finding the hole, and thank you
This is AWESOME! now all we need is a work around like the DX to get some Clockwork mod recovery, or a way to crack the BL.
Never the less, i wanna say thanks to all the devs that did this, you guys rock

[HOW-TO] [GSM & CDMA] Root without Unlocking Bootloader via exploit (for 4.0.1/4.0.2)

[HOW-TO] [GSM & CDMA] Root without Unlocking Bootloader via exploit (for 4.0.1/4.0.2)
Edit: This does not works on anything newer than ICL53F (i.e., 4.0.2). It works fine on ITL41D (4.0.1), ITL41F (4.0.1) and ICL53F (4.0.2)
Once you have got root, you can now use segv11's BootUnlocker app to unlock your bootloader without wiping anything. Easy as pie!
Disclaimer: I take no credit for this exploit or the implementation of it (but I will take credit for the step-by step ). Thanks to kendong2 for pointing it out to me here.
So, it looks like zx2c4 has found a local privilege escalation exploit. See source here, and saurik has managed to package it together for Android. See here. Although this may be old news to some, I hadn't seen it before.
So what does this all mean:
If you are running a 2.6.39 kernel (or above), which all Galaxy Nexus' are, you can now root your device without having to unlock your bootloader (and without losing your data).
Moreover, you should now be able to root your device even if your hardware buttons are not working.
Additionally, this allows those who have not received an OTA update and want to apply it without having an unlocked bootloader or root to do so by copying the OTA update to /cache from /sdcard.
Notes:
1) This assumes that you have USB Debugging enable on your device (Settings > Developer Options > Enable USB Debugging) and the drivers for your device installed on your computer. For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
2) This needs to be done over ADB, as a terminal emulator on-device does not have the appropriate access. If you do not have ADB, I've attached it in the zip. Unzip all files.
3) Some users indicate that, once finished the procedure, they needed to open the Superuser app.
Step-by-step:
1) Download the attached files to your computer and unzip them in the same directory as your adb.exe file;
2) Open a command prompt in the same directory;
3) Copy the files to your device:
adb push mempodroid /data/local/tmp/mempodroid
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
4) Open a shell: adb shell
5) Change permission on mempodroid to allow it to run: chmod 777 /data/local/tmp/mempodroid
6) Run the exploit: ./data/local/tmp/mempodroid 0xd7f4 0xad4b sh
Note: Once you do step 6, your prompt should change from $ to #. If not, it did not work.
7) Mount the system partition as rw: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
8) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
9) Change permissions on su: chmod 06755 /system/bin/su
10) Copy Superuser.apk: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
11) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
12) Mount the system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
13) Rescind root: exit
14) Exit the ADB shell: exit
15) Done. You now should have root without having to unlock your bootloader.
Reserved
Reserved
This is the same as https://github.com/saurik/mempodroid
saurik ftw.
times_infinity said:
This is the same as https://github.com/saurik/mempodroid
saurik ftw.
Click to expand...
Click to collapse
Not sure what you are getting at? I mentioned saurik in the first post, and the link you posted is in the first post. And I mentioned that this may be old news, but I haven't seen it anywhere before today in the GN forums.
Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!
Sleuth255 said:
Yikes! This exploit works on any kernel from 2.6.39 and >. This could become a common root method for many devices. Linus Torvalds himself posted the fix commit! Nice work by zx2c4!
Click to expand...
Click to collapse
You need ics to have a vulnerable kernel version, so given the number of devices which currently have ics officially, I doubt it will be common. I'd also expect Google and vendors to correct this in next release.
Also many custom kernels don't have this flaw as they are at or over 3.0.18 or have patched it. This prevents gaining unnoticed root.
Sent from my Galaxy Nexus
Hmmm I thought 2.6.39 was found in GB builds. This exploit is almost a root fix for the Moto DX 4.5.621 fiasco. Unfortunately the kernel for that build is 2.6.32.9.
Sent from my Galaxy Nexus using xda premium
This was huge in the headlines a few weeks back. It's nice to see someone putting it to a good use!
Sent from my Galaxy Nexus using xda premium
Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.
Huxleysäl said:
Hi, been lurking awhile, registered to clear up somethings.
I did some research while attempting to access the /data/local/ -folder with terminal emulator and I found that it would be impossible to write or to find it while being unrooted. Rooting a phone through using an unrooted access root seems impossible.
Did I miss something or is there any other way to copy mempodroid to the data- folder? I sure would like to keep all my files.
Click to expand...
Click to collapse
I think you are mistaken. In a terminal emulator type: cd /data/local/tmp
Edit: Fixed a mistake made by auto correct...
Sent from my Galaxy Nexus using Tapatalk
efrant said:
I think you are mistaken. In a terminal emulator type: cd /data/local/temp
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links
try /data/local/tmp
Huxleysäl said:
Just did. It says "No such file or directory."
Not the best source, but if you google it, people state what I state. Sorry, can't post links
Click to expand...
Click to collapse
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk
efrant said:
Sorry, damn auto correct. It should be: cd /data/local/tmp
Not "temp".
It works fine.
Edit: Sleuth255 beat me to it!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb
Huxleysäl said:
Sure, OK, it worked. But as I'm trying to replicate his instructions, copying mempodroid to data/local/tmp doesn't compute. I tried extracting the files, puting mempodroid in a new folder in ./sdcard/ (which I named Nex), and it still couldn't find it.
Wait, just had an idea. Brb
Click to expand...
Click to collapse
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk
OK, this is exactly what I did:
I downloaded the files, extracted them into the ./sdcard folder of my android. I opened the console, wrote exactly as stated. Reaction? Cannot create /data/local/tmp/mempodroid: Permission denied
So, what I'm thinking is this: I tried the cd ./sdcard/mempodroid, found it. So, logically, that should mean that since the permission is dennied, the problem lies not in where I put the mempodroid, but with my authority over my phone. So, here we are again. Could anybody smarter then me clarify?
efrant said:
Hmm. Looks like you may be correct. In GB, we had write access to that directory, but it looks like we don't in ICS. I'll have another look tomorrow and try to figure something out.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
****, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.
Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.
convolution said:
Might want to expand on the steps.
Like what program to use to copy the file.
How do you change permission.
How do you run the exploit.
How to mount rw.
How to copy su.
Click to expand...
Click to collapse
I hade my initial problems with that too. But as if this moment it doesn't really matter. Read above posts. Anyhow, to answer your question: you need to download a console emulator
Just search for it in the market. Also the commands go in this console
For example: cat /directory/filename > /newdirectory/samefilename means to copy or move from one place. To change permission you just write that line of code ending with 777 instead of cat and then the filename etc and etc.
I didn't know any of this 'till yesterday, so it is quite understandable.
cheers
Huxleysäl said:
F***, I was hoping I was wrong. I originally thought that the exploit was this. But alas.
Try finding an alternative write route to the /data/local/- folder. That should solve all problems, I guess. Big words, ey? This is for the simpletons like me, who stupidly forgot to bootload.
Click to expand...
Click to collapse
I've updated the first post. Give that a go and let me know how it turns out. (The guide may need some minor tweaking, but I am here to help you through it.)
It seems that ADB has rw access to /data/local/tmp but a terminal emulator on-device does not. So for now, you need to be plugged into your computer.
It may be possible to do this with ADB-over-Wi-Fi, but I haven't gotten there yet.

[GUIDE] Rooting your phone...from your phone [ALL US SGS3]

Rooting your phone...from your phone (what?!)
DISCLAIMER: I do not expect anything to go wrong as I have personally tested this. However, YOU are choosing to make these modifications to your phone so I DO NOT take responsibility for any damage that may come as a result of using this. If you come back and point the finger at me, I will laugh at you.
If your phone is not an SGS3, this MAY still work for you. I take absolutely NO responsibility either way.
Prerequisites
The following files are attached to this post for convenience. Download and install the apps, download and extract the zip file somewhere convenient.
Superuser by Koush(MUST be this one. You can change it later if you so desire.)
Terminal Emulator by Jack Palevich ( MUST be this one)
Zip file, extracted somewhere convenient
Click to expand...
Click to collapse
Click to expand...
Click to collapse
THE GOODS
These generic names will be used:
/path/to/motochopperDir - This is the full path to the extracted motochopper-mobile DIRECTORY or FOLDER. Example: /sdcard/motochopper-mobile (will vary depending on where you extracted the files).
NOTE: After running the script, Motochopper may or may not print "Failed", but the exploit DOES indeed work regardless of this. Make sure you reboot for changes to take effect.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Download the attached zip file AND both apps.
Install Terminal Emulator and Superuser (use a file manager, navigate to the downloaded .apk files and click on each file to install them).
Open up Terminal Emulator and type the following commands. Press the ENTER key after each command.
Code:
cd /path/to/motochopperDir
cat setup.sh > /data/data/jackpal.androidterm/setup.sh
cd /data/data/jackpal.androidterm
chmod 755 setup.sh
./setup.sh /path/to/motochopperDir
From there, my setup.sh script will handle the rest of the process. If you are still unsure, see my sample run below.
Sample run (files were extracted to /sdcard/moto)
Code:
cd /sdcard/moto
cat setup.sh > /data/data/jackpal.androidterm/setup.sh
cd /data/data/jackpal.androidterm
chmod 755 setup.sh
./setup.sh /sdcard/moto
Credits
Motochopper exploit by djrbliss (Dan Rosenburg). Original thread here.
Jack Palevich and Koush for their apps, especially Jack Palevich. This would not be possible without the shared permissions on his app's data directory.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Links
Download the attachments!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Flash counters, etc?
Will this method increment any of the flash counters, turn on the triangle etc??
kwmike said:
Will this method increment any of the flash counters, turn on the triangle etc??
Thanks.
Click to expand...
Click to collapse
No, it will not. That's the point, there's no need to use ODIN.
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
Not working on new ATT S3 I747
This tool is not working for me. I have tried several times. I always get a 'failed' msg.
I have a 2 day old brand new S3 i747 from ATT. Stock JB 4.1.1
I extracted the motochopper-mobile.zip files to /storage/sdcard0/moto/.
The setup.sh script is in the /data/data/jackpal.androidterm after it is run. The other moto related files are not there as if the script had run ok.
After the reboot superuser needs a new binary and fails when the binary update is attempted.
All other root sensitive apps fail.
_________________________________________________________________________________________________
FIXED:
I used the download/instructions on the OP on the following link:
http://forum.xda-developers.com/showthread.php?t=2252248
While it does not do all the work from the S3 and must be loaded from a Windows environment , it did the job perfectly.
Flash counter, triangle etc. not triggered!!
Try downloading the files and run it again.
I tested it by deleting my su binary and then I ran this tool and rebooted. And BAM, su was placed in /system once again and superuser was fine.
If it still doesn't work, go to the original Motochopper thread and follow the instructions there using your computer.
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
Files are now attached to the OP.
CNexus said:
Rooting your phone...from your phone (what?!)
DISCLAIMER: I do not expect anything to go wrong as I have personally tested this. However, YOU are choosing to make these modifications to your phone so I DO NOT take responsibility for any damage that may come as a result of using this. If you come back and point the finger at me, I will laugh at you.
If your phone is not an SGS3, this MAY still work for you. I take absolutely NO responsibility either way.
Download the attached zip file AND both apps.
Install Terminal Emulator and Superuser (use a file manager, navigate to the downloaded .apk files and click on each file to install them).
Open up Terminal Emulator and type the following commands. Press the ENTER key after each command.
Code:
cd /path/to/motochopperDir
cat setup.sh > /data/data/jackpal.androidterm/setup.sh
cd /data/data/jackpal.androidterm
chmod 755 setup.sh
./setup.sh /path/to/motochopperDir
From there, my setup.sh script will handle the rest of the process. If you are still unsure, see my sample run below.
Sample run (files were extracted to /sdcard/moto)
Code:
cd /sdcard/moto
cat setup.sh > /data/data/jackpal.androidterm/setup.sh
cd /data/data/jackpal.androidterm
chmod 755 setup.sh
./setup.sh /sdcard/moto
Click to expand...
Click to collapse
This is too cool. Had no idea this was possible. Is it possible to post screenshots to help the really new members out? That's just a suggestion.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Bruce Lee said:
This is too cool. Had no idea this was possible. Is it possible to post screenshots to help the really new members out? That's just a suggestion.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It is...I'm a little busy working on other projects at the moment though, as you can see from my sig
Sent from my S3 on Sense 5
That's cool I totally understand. Just thought I would plant the seed. Lol
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
So this is suppose to allow Rooting without the use of a computer? if so, im in!
dannieloco said:
So this is suppose to allow Rooting without the use of a computer? if so, im in!
Click to expand...
Click to collapse
Yes, but so far I have only been able to confirm that it works on a couple Sprint phones...you can try it, but I can't guarantee that it will actually root your phone
It finely don't brick it though, if you're worried.
CNexus said:
Yes, but so far I have only been able to confirm that it works on a couple Sprint phones...you can try it, but I can't guarantee that it will actually root your phone
It finely don't brick it though, if you're worried.
Click to expand...
Click to collapse
Yeah Ive read about the motochopper method and its pretty safe.. wont brick the phone. I was actually going to do this to my friend's S3 on sprint. My att s3 is already rooted and rom'd
dannieloco said:
Yeah Ive read about the motochopper method and its pretty safe.. wont brick the phone. I was actually going to do this to my friend's S3 on sprint. My att s3 is already rooted and rom'd
Click to expand...
Click to collapse
Ah ok, good deal haha
CNexus said:
Ah ok, good deal haha
Click to expand...
Click to collapse
So i just tried following every single step but it wont allow for SU binaries to update. When i finished each line of code, it said FAILED and to reboot/battery pull which I did.. Not sure what to do. I was hoping it worked.. did I do something wrong? I even tried installing superuser from the app store and it wasnt updating binaries either.. TitaniumBackup didnt work...
I don't know. Just use the regular method of using ODIN to send a recovery and then flash SU :\
i install 2 apps and kept the zip motochopper on external sd no extract and then use terminal but when i put the codes and hit enter it says "no such file" what am doing wrongg?? please help i need this
Sent from my SAMSUNG-SGH-I747 using xda premium
smallyetzon said:
i install 2 apps and kept the zip motochopper on external sd no extract and then use terminal but when i put the codes and hit enter it says "no such file" what am doing wrongg?? please help i need this
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
You're supposed to extract the zip and then pass the path to the directory to setup.sh...
CNexus said:
You're supposed to extract the zip and then pass the path to the directory to setup.sh...
Click to expand...
Click to collapse
ok extracted to extsdcard example:
cd /storage/extsdcard/motochopperdir
???????
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 04:40 AM ---------- Previous post was at 04:22 AM ----------
CNexus said:
You're supposed to extract the zip and then pass the path to the directory to setup.sh...
Click to expand...
Click to collapse
i think i did it couse terminal acepted all codes so i restarted and now superuser ask me to update su binary ?? am i done?? please help
Sent from my SAMSUNG-SGH-I747 using xda premium
If you extracted to that directory, then the command you need to run is "./setup.sh /storage/extsdcard/motochopperdir"
But first you need to do "cd /data/data/jackpal.androidterm" if you're not already in that directory.
CNexus said:
If you extracted to that directory, then the command you need to run is "./setup.sh /storage/extsdcard/motochopperdir"
But first you need to do "cd /data/data/jackpal.androidterm" if you're not already in that directory.
Click to expand...
Click to collapse
im so lost my bad i dont want to make u waist your time but is it posible for you to send me the exact commands from top to bottom? i tried your sample and i dont know somethimes it tells me too many arguments haha its getting mad at me sorry for my ignorance on this anyway the extracted zip is on sdcard and is called motochopper-mobile thanks
Sent from my SAMSUNG-SGH-I747 using xda premium

Categories

Resources