http://qua1ia.blogspot.com/2013/05/get-root-on-sony-tablet-p-ics-r5a.html
It works really
cream5296 said:
http://qua1ia.blogspot.com/2013/05/get-root-on-sony-tablet-p-ics-r5a.html
It works really
Click to expand...
Click to collapse
Can any console-ninja verify?
Anyone who has ever done could mount a video tutorial for the layman like me. thank you
it took me a little time to compile it (since i cannot read everything on the website, perhaps there is a precompiled binary) but after that i think i got temporary root
Code:
[0|08:40|[email protected]|~/android_run_root_shell/libs/armeabi>
$ adb push run_root_shell /data/local/tmp
[0|08:40|[email protected]|~/android_run_root_shell/libs/armeabi>
$ adb shell
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
[email protected]:/data/local/tmp $ ./run_root_shell
failed to open /dev/diag due to No such file or directory.
Attempt perf_swevent exploit...
writing address is 8e09
[email protected]:/data/local/tmp # id
uid=0(root) gid=0(root)
so i got temporary root...with that i could remount the system partition, copy busybox and su to /system/xbin and Superuser.apk to /system/app, so i guess i am rooted again, thanks for the nice work!
if anyone wants i can create a zip with all needed files and a linux bash file for installing.
smokey_joe said:
it took me a little time to compile it (since i cannot read everything on the website, perhaps there is a precompiled binary) but after that i think i got temporary root
Code:
[0|08:40|[email protected]|~/android_run_root_shell/libs/armeabi>
$ adb push run_root_shell /data/local/tmp
[0|08:40|[email protected]|~/android_run_root_shell/libs/armeabi>
$ adb shell
[email protected]:/ $ cd /data/local/tmp
[email protected]:/data/local/tmp $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
[email protected]:/data/local/tmp $ ./run_root_shell
failed to open /dev/diag due to No such file or directory.
Attempt perf_swevent exploit...
writing address is 8e09
[email protected]:/data/local/tmp # id
uid=0(root) gid=0(root)
so i got temporary root...with that i could remount the system partition, copy busybox and su to /system/xbin and Superuser.apk to /system/app, so i guess i am rooted again, thanks for the nice work!
if anyone wants i can create a zip with all needed files and a linux bash file for installing.
Click to expand...
Click to collapse
So it works???
Sent from my Sony Tablet S using xda app-developers app
jumper62 said:
So it works???
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
so i got temporary root...with that i could remount the system partition, copy busybox and su to /system/xbin and Superuser.apk to /system/app, so i guess i am rooted again, thanks for the nice work!
that's a bit vague, okay, but after doing a complete Titanium Backup on my Sony Tablet P, i gues i can say for sure, yes i have root
smokey_joe said:
it took me a little time to compile it (since i cannot read everything on the website, perhaps there is a precompiled binary) but after that i think i got temporary root
[...]
so i got temporary root...with that i could remount the system partition, copy busybox and su to /system/xbin and Superuser.apk to /system/app, so i guess i am rooted again, thanks for the nice work!
if anyone wants i can create a zip with all needed files and a linux bash file for installing.
Click to expand...
Click to collapse
Yes, I want - and I think many other users also.
It would be nice if you would provide the needed files. Maybe you can describe in short words what you exactly did.
Posted the procedure and link to files in english
http://forum.xda-developers.com/showthread.php?p=42485765
Sent from my Sony Tablet S using xda app-developers app
plerzelwupp said:
Yes, I want - and I think many other users also.
It would be nice if you would provide the needed files. Maybe you can describe in short words what you exactly did.
Click to expand...
Click to collapse
i posted a zip package below jumper62s post*, which contains all needed files and a little readme file, which explains what to do, since he didn't post any binaries and you have to compile this stuff before you can use it, i guess it's kind of useful for a lot of people out there.....but it could be that i have to delete it, if he wants me to
*http://forum.xda-developers.com/showthread.php?p=42485765
THANKS!
smokey_joe said:
i posted a zip package below jumper62s post*, which contains all needed files and a little readme file, which explains what to do, since he didn't post any binaries and you have to compile this stuff before you can use it, i guess it's kind of useful for a lot of people out there.....but it could be that i have to delete it, if he wants me to
*http://forum.xda-developers.com/showthread.php?p=42485765
Click to expand...
Click to collapse
Thank you so much - it works! :good:
I just rooted my Sony Tablet with Android 4.0.3 R5A
I justed wanted to tell it here also - I think it's better to continue the following discussion in the other (linked) thread.
Related
1) How do I remove hard linked files on the X10 Android file system? I also need to identify them with the "ls" command, but it doesn't work the same as linux by listing the count in the ls listing of hard links to a specific file. The reason is, when I try to move a file in /system/app, it tells me it failed due to cross-device link - likely because the OS knows the link will fail if I move the file to my /sdcard directory. I want to remove the hard-link.
2) Is there a listing of all the options available to the commands in the /system/bin directory? It seems the ls command, for example, is a stripped down version of the ls that comes with linux.
Thanks.
what method are you using to move the files in system/app? you should be able to move them using root explorer, or copy out using dd if= of= statements then rm, the xperia system does not seem to like cp and mv commands
I'm using:
Code:
mv /system/app/Facebook.apk /sdcard/backup/system/app
...it fails. A dd works, because it just does a block copy and doesn't move the file. I'll try moving it with Root Explorer.
I'd prefer an actual command instead of using an app on the phone, as I've connected the phone to my PC with the USB cable and using adb.exe.
FYI, I tried Root Explorer, for some reason it can move the file just fine! My phone is rooted and I'm running the adb shell with super-user access.
use this:
busybox ls -l
busybox cp
busybox mv
Or even better, use "busybox --install /system/bin" and let it install all the symlinks for you
aln688 said:
I'm using:
Code:
mv /system/app/Facebook.apk /sdcard/backup/system/app
...it fails. A dd works, because it just does a block copy and doesn't move the file. I'll try moving it with Root Explorer.
I'd prefer an actual command instead of using an app on the phone, as I've connected the phone to my PC with the USB cable and using adb.exe.
FYI, I tried Root Explorer, for some reason it can move the file just fine! My phone is rooted and I'm running the adb shell with super-user access.
Click to expand...
Click to collapse
biktor_gj said:
use this:
busybox ls -l
busybox cp
busybox mv
Or even better, use "busybox --install /system/bin" and let it install all the symlinks for you
Click to expand...
Click to collapse
Thanks for the tip, you've just explained what busybox is. I always wondered why Titanium Backup wanted Busybox for it to run properly. I'll try these commands out.
UPDATE: Nice, I get VI as well! I was wanting that. I got fedup editing a file on the PC and pushing it back to the phone. Thanks.
Here comes the latest rooting method that works with 2.0.2.A.0.24 firmware.
Credits to Scotty2 for his psneuter exploit!
1. Download and unpack rootme.tar.bz2
2. Execute ./rootme (linux) or rootme.bat (windows)
3. Done.
---
You may also want to try SuperOneClickv1.5.5-ShortFuse.zip (modified by batman_112 to use the latest exploit).
Cheers,
z
Stop for me at Point 4)
I got back
./ratc: Permission denied
Click to expand...
Click to collapse
after
./ratc
i get ... permission denided
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
zdzihu said:
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
Click to expand...
Click to collapse
Your link is broken
Try now, I got rid of installation scripts
EDIT: Now it works flawlessly. I still have no clue why copying files with .bat file messes everything up, but manual copying does the job.
why the superone reach the root sometimes so slow?
your method uses the same exploit, and works at first try
check the files plz: Invalid or Deleted File
can't download the ratc-pack --> Invalid or Deleted File
please reup - THX
EDIT: Link is OK now --> THX
Link is OK. Downloading at the moment.
Tried it manually (as described)...
But same problem... :-(
UserX10 said:
Tried it manually (as described)...
But same problem... :-(
Click to expand...
Click to collapse
I just reflashed my phone and it worked for me at 1st attempt.
Could you please got rid of the old files and retry from the beggining?
Cheers!
meta96 said:
after
./ratc
i get ... permission denided
Click to expand...
Click to collapse
Same thing for me
:-( Same Problem
I flashed my X10 with nordic FW and tried it again Step by Step... but "permission denied"... even if i remove and make the tmp directory as described...
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
chmod 777 /data/local/tmp/*
I added some screenshots to show how the process works for me.
is this a full root? i mean, is root+shell root?
zdzihu said:
Hi guys, I've noticed some people still can't get their phones rooted with SuperOneClick method. So do I, never managed to get it working Here is a simple method of rooting, using the same exploit (rageagainstthecage - credits to author). This is quick and 100% guaranteed to work but I'd rather recommend it to advanced users.
1. Install Android Terminal Emulator from the market http://bit.ly/9B46Nl
2. Download and unpack http://www.mediafire.com/?s0428zxc7n50i28
3. Plug in the phone (usb debugging mode), copy the following files with adb and change permissions:
Code:
adb push ratc /data/local/tmp/ratc
adb push busybox /data/local/tmp/busybox
adb push su /data/local/tmp/su
adb push rootme /data/local/tmp/rootme
adb push superuser.apk /data/local/tmp/superuser.apk
adb shell
chmod /data/local/tmp/*
4. Start Terminal Emulator on your phone and issue those commands:
Code:
cd /data/local/tmp
./ratc
5. Exit out of Terminal Emulator using BACK button.
6. Start any other application and exit out of it using BACK button.
7. Start Terminal Emulator again - note that you're running it as root (#)
8. Issue those commands:
Code:
cd /data/local/tmp
./rootme
Your phone will reboot - and it's done. I suggest installing Busybox from the Market. Hope it helps.
Cheers!
EDIT: Fixed.
Click to expand...
Click to collapse
Finally I was able to root my phone
just one correction, you got to use chmod 777 /data/local/tmp/*
it was not allowing to root otherwise
i kept breaking my head using the "simple" SuperOneCLick but could not show my rage against the machine
thank you for explaining this process for Root.
zdzihu said:
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
cd /data/local/tmp
chmod 777 *
I added some screenshots to show how the process works for me.
Click to expand...
Click to collapse
chmod 777 *
did it. thanx. btw like your oldstyle-skills
Just saw this thread and wanted to root my phone also...I downloaded the files provided in the first post and extracted onto my PC. When I tried running the adb application, I only get a command window only for a split second and then it disappears. Am I doing something wrong?
Everything works fine until the final step where I write ./rootme in the emulator.
Before the phone reboots, it says something right after, something about superuser.apk.
Once the phone is back on the emulator goes back to $. As well as not being able to download Busybox.
Appreciate your efforts
EDIT: No worries, I managed to get root using SuperOneClick (finally!). It was rather sketchy, would've preferred your way tbh.
I finally got my NookColor to sideload apps via ADB. The first thing I did was install Root Explorer and I rebooted the NC.
However, using Root Explorer, I do not have access to the cache or data directories. The response that I get is "Mounted as r/o" and "Your phone doesn't appear to be rooted. ..."
Did I miss something in the process and I'm not really rooted?
Also, I've noticed that the command adb remount gives back an error message as well.
Any thoughts?
Thanks!
See http://forum.xda-developers.com/showthread.php?t=857636
Assuming that you've already install the SuperUser apk
You need to push the su file into /data/local
use the following ADB commands:
Code:
adb push su /data/local/
Then
Code:
adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
Use the su file from the attachment in the thread below
http://forum.xda-developers.com/showthread.php?t=665974
Thank you, Sapienta.
I noticed the Superuser comes down as a zip and the instructions say to boot into recovery mode and flash ... does that translate to renaming the zip to apk and installing via adb (as I've done with other apps)? Or do I need to figure out how to do the recovery boot/flash?
Ya sorry about that. I should've been more clear. Ignore everything from that page just download the attachment. You need to push the "su" file into /data/local and then chmod it to 6755 per the instructions from the first link I post and you're good to go.
EDIT NVM, I got it
Well, actually, you were quite clear the first time, I had just forgotten about the first link. But now, when I try to install the file (after renaming the zip to apk) via ADB I get an error message that says file does not contain AndroidManifest.xml. But I know the file is there ... I can see it when I view it with 7Zip. So, I guess I'm being dense today, but what am I missing?
indeana said:
Well, actually, you were quite clear the first time, I had just forgotten about the first link. But now, when I try to install the file (after renaming the zip to apk) via ADB I get an error message that says file does not contain AndroidManifest.xml. But I know the file is there ... I can see it when I view it with 7Zip. So, I guess I'm being dense today, but what am I missing?
Click to expand...
Click to collapse
Inside of the zip file there should be two files, a file called "su" without an extension and the Superuser.apk.
You'll want to push the su (the file is actually a raw binary) to your NC using the steps provided. You'll also want to install the Superuser.apk after pushing the su binary.
Thank you, antoniouslj. Yesterday I installed SU first and then pushed su but Root Explorer kept erroring out. So just to be sure I'm clear, the steps would be done in this order:
1. Push su -->
adb push su /data/local/
2. Change permissions -->
adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
3. Install Superuser
Then do I adb Root Explorer or should Root Explorer be installed before I do the steps above?
indeana said:
Thank you, antoniouslj. Yesterday I installed SU first and then pushed su but Root Explorer kept erroring out. So just to be sure I'm clear, the steps would be done in this order:
1. Push su -->
adb push su /data/local/
2. Change permissions -->
adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
3. Install Superuser
Then do I adb Root Explorer or should Root Explorer be installed before I do the steps above?
Click to expand...
Click to collapse
That's exactly what I did and it worked great for me. I also had Root Explorer installed prior to installing SU.
Still Struggling!
So ... I still can't get this to work. Do I need to install an alternative launcher (like ADW) first and then do this process?
indeana said:
So ... I still can't get this to work. Do I need to install an alternative launcher (like ADW) first and then do this process?
Click to expand...
Click to collapse
No... what part of the process are you getting stuck on?
I do the three steps like we talked about earlier (and exactly in that order--except I exit out of the shell before I issue the adb install superuser.apk command) and I reboot the Nook. Turn the Nook back on and open Root Explorer, but then RE tells me that there are issues with Superuser and to close RE and restart the RE app. So I do. But it repeats the same process. (I've removed everything so I don't remember the exact language. When I open SU there is no way for me to add an app (that I know of anyway) including looking at the settings. So that's where I'm stuck. And if I can't get root access, then apps like SetCPU and Quickboot won't run successfully.
indeana said:
I do the three steps like we talked about earlier (and exactly in that order--except I exit out of the shell before I issue the adb install superuser.apk command) and I reboot the Nook. Turn the Nook back on and open Root Explorer, but then RE tells me that there are issues with Superuser and to close RE and restart the RE app. So I do. But it repeats the same process. (I've removed everything so I don't remember the exact language. When I open SU there is no way for me to add an app (that I know of anyway) including looking at the settings. So that's where I'm stuck. And if I can't get root access, then apps like SetCPU and Quickboot won't run successfully.
Click to expand...
Click to collapse
Grab another version of RE. I'm finding that version matters when trying to sideload apps.
EUREKA!!!
Thanks to everyone for your help! I finally figured it out. Just as I was about to take the last suggestion of finding and downloading another version of RE, I found and downloaded another version of Superuser (version 4). The new SU version extracts from the zip differently but I was finally able to push and modify per the earlier instructions, installed the new SU version, rebooted, started RE, added it to the SU Whitelist and BAM Root Explorer is working just as I expected it to. SetCPU and Quickboot also seems to be working.
Once again, thank you! You were all GREAT!!!
indeana said:
Thanks to everyone for your help! I finally figured it out. Just as I was about to take the last suggestion of finding and downloading another version of RE, I found and downloaded another version of Superuser (version 4). The new SU version extracts from the zip differently but I was finally able to push and modify per the earlier instructions, installed the new SU version, rebooted, started RE, added it to the SU Whitelist and BAM Root Explorer is working just as I expected it to. SetCPU and Quickboot also seems to be working.
Once again, thank you! You were all GREAT!!!
Click to expand...
Click to collapse
Nevermind...I got mine going, too.
Check this thread for updated and improved information, many thanks to j4mm3r
http://forum.xda-developers.com/showthread.php?t=953110
Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. Using this version of su is not as secure because it will not activate Superuser for your permission to grant root access. In fact, it can work without Superuser.apk installed at all. Hopefully we will soon have an updated su or maybe the next version of Honeycomb will be prerooted. First download the following files:
1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2
Extract the above files using your favourite program
Using adb, install all three files to /data/local:
adb push su /data/local
adb push Superuser.apk /data/local
adb push busybox /data/local
Use adb remount to open the /system directory
adb remount
Use adb shell to move files
adb shell
cd /data/local
cat Superuser.apk > /system/app/Superuser.apk
cat su > /system/bin/su
cat busybox /system/xbin/busybox
Symlink su and set permissions:
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su
Typing su should now work
su
su: access granted, courtesy of www.magicdroidapps.com
Install busybox
exit from adb shell and using a terminal application (i.e Root Explorer or Better Terminal Emulator) on the nook,
su
busybox --install -s /system/xbin
That should do it, works with Root Explorer, Titanium Backup, LCD Density, Quick Boot and SetCPU.
Good Luck
really? That simple? Root was the only reason i haven't jumped on the Honeycomb train. This may change my mind.
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?
Homer
anbradle said:
I tried this on the 2gb sd image got root. But after I rebooted root was gone.
Click to expand...
Click to collapse
Check your steps, especially permissions and the symlink. Works consistently on reboot for me.
Homer_S_xda said:
I noticed su is in /system/bin rather than /system/xbin on the Froyo image. Any reason?
Homer
Click to expand...
Click to collapse
I couldn't get it to work for me without installing in /system/bin and using a symlink to /system/xbin
chhaggerty said:
It wouldn't work for me without installing in /system/bin and using a symlink to /system/xbin
Click to expand...
Click to collapse
It should work anywhere in the default PATH as long as it's got the full permissions (7655) set. I've only got one in xbin wih no symlink and all has been well for the superuser app...
[email protected]:/system/bin # echo $PATH
echo $PATH
/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
[email protected]:/system/bin # ls -l su
ls -l su
su: No such file or directory
[email protected]:/system/bin # ls -l /system/xbin/su*
ls -l /system/xbin/su*
-rwSr-sr-t root root 76232 2011-02-04 09:08 su
-rwSr-sr-t root root 76232 2009-07-31 19:08 su-magic
-rwSr-sr-t root root 26264 2010-08-10 06:52 su-new
-rwSr-sr-t root root 68340 2011-01-31 11:22 su-org
chhaggerty said:
Credit goes to NuroSlam for coming up with a working method. This requires a functioning adb connection. First download the following files:
1. su http://www.magicandroidapps.com/su.zip
2. Superuser.apk http://bit.ly/su2361ef
3. busybox http://busybox.net/downloads/busybox-1.18.2.tar.bz2.
Good Luck[/B]
Click to expand...
Click to collapse
i might take credit for gaining root, but the rest is all you
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.
Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.
Thanks again!
Nathan
nswenson said:
Thanks! I couldn't really follow the part with installing busybox. Was I supose to make the busybox binary? Anyway, I just let titanium backup install busybox for me by clicking the "Problems?" button.
Just tried Root Explorer and it's working great. Nice being able to quickly edit the build.prop file. Upped the dalvik heap size to 64mb and messing with LCD density.
Thanks again!
Nathan
Click to expand...
Click to collapse
Running busybox from terminal will install all the busybox commands in /system/xbin which should make them available when using adb.
Just a suggestion...
Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
You were right I tried again and now I am rooted after reboot. Thanks
jleecong said:
Just a suggestion...
Making a batch file with the command and packing everything in 1 zip makes it a lot easier for most people and reduces the chances of people forgetting a step.
Click to expand...
Click to collapse
Okay...
I am running HC (v2) off a 8gb sd card.
So do I just do these steps to gain root or do I need to partition the sd card first?
Thanks
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
j4mm3r said:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
agreed, i was just going for root myslef
j4mm3r said:
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
In
http://howto.ccroms.net/android_project/build/mod/root
I would have though that the purpose of the changes, specifically;
LOCAL_FORCE_STATIC_EXECUTABLE := true
LOCAL_STATIC_LIBRARIES := libc
Were what should resolve the _mktemp not found?
j4mm3r said:
Note to the OP, this method isnt exactly quite the same as using the "su" from the SuperUser app would be. This is just a modified "su" binary from the AOSP build which bypasses the check for uid AID_SHELL. Typically, the su shipped with Android only allows root access if invoked via "adb shell".
Now, although this modified binary is quite ok and will get you on the way working with all the Apps that require root access, but it will leave your system unsecure.
You see the guys who developed SuperUser have a hook inside the "su" binary which invokes the SuperUser activity which allows the user to allow/disallow/track other applications' root requests and usage.
So my advice is to be really careful and understand what you are doing if you decide to install this.
I'm gonna try and recompile ChainsDD's SuperUser and see if I can remove its dependency on mktemp.
EDIT: There is no need to push the SuperUser.apk, the modified su has no relation with it and it will work anyways.
Click to expand...
Click to collapse
Howard from MagicAndroidApps.com noted this on the original Honeycomb thread. I'll update the OP to make this clear. Thanks.
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?
Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
Mikey1022 said:
So once we acquire root, there is nothing to shield apps or commands from performing root without the users knowledge?
Edit: That does sound correct the way i typed it, hope you guys understand what i'm trying to convey
Click to expand...
Click to collapse
yes, at the stands, its just root access. granted i had my own reasons for this
I've rooted my HTC Amaze. The rootedness persists across reboot. Here's how I did it.
1. Copy the zergRush temp root to the phone. I put it in /data/local
2. Run zergRush on the phone via adb shell.
One you have temp root do this (from the PC)
1. adb remount
2. adb push su /system/bin/
3. adb shell chmod 04755 /system/bin/su
Then you can install superuser.apk and reboot. After rebooting you should be able to adb shell and type su. This should prompt you (on the phone) to allow su. Once you allow it then any apps that need root should begin working.
You can find the zip file that contains the su binary here
NOTE: the adb daemon will not be running as root so, when you adb shell to the device you will not have root. You just run su and then you have root.
Questions? Just ask. I'll do my best to help. But, remember, you do this all at your own risk.
-xdadevelopers-user
I had some weirdness when allowing a second root app in superuser. It would consistently FC. The first root app was fine and continued to work but I couldn't get another root app to be authorized.
It turns out it's related to the permissions on the superuser databases. To fix my problem I went to home>menu>settings>applications>manage applications>superuser>clear data. Then run superuser and dismiss the startup dialog. Now adb shell and run su. It will prompt on the device and you should allow it. You should now have the root prompt in your adb shell session. From there type
Code:
chmod 666 /data/data/com.noshufou.android.su/databases/*
Now you can run more root apps without superuser FCing.
-xdadevelopers-user
Very nice work, I will probably wait until we have recovery to actually do it. This is a great start though, hopefully this works with no problems as I saw that some were "bricking" their devices using the Zerg method for temp root.
This is still temproot , it won't allow u to go into /system to delete bloat or edit framework .
Sent from my HTC_Amaze_4G using XDA Premium App
Revolution said:
This is still temproot , it won't allow u to go into /system to delete bloat or edit framework .
Sent from my HTC_Amaze_4G using XDA Premium App
Click to expand...
Click to collapse
Yes, it will. In fact, that's basically all it does. Of course if you want to change /system/ you'll need to su to root first, then remount it RW. From there you can make any changes you want. The changes you make will persist across a reboot. To test this I deleted teeter.apk and teeter.odex from /system/app and rebooted. Teeter is now gone from my phone.
So, unless I'm misunderstanding what you mean, this is permanent root.
-xdadevelopers-user
Alright , i mean like will it let you add edit file's in /system such as editing framework ?
xdadevelopers-user said:
Yes, it will. In fact, that's basically all it does. Of course if you want to change /system/ you'll need to su to root first, then remount it RW. From there you can make any changes you want. The changes you make will persist across a reboot. To test this I deleted teeter.apk and teeter.odex from /system/app and rebooted. Teeter is now gone from my phone.
So, unless I'm misunderstanding what you mean, this is permanent root.
-xdadevelopers-user
Click to expand...
Click to collapse
Revolution said:
Alright , i mean like will it let you add edit file's in /system such as editing framework ?
Click to expand...
Click to collapse
For the record yes it dose, but your a dev next time try it b4 you post saying it don't work because u make yourself seem like you don't know what your talking about
Sent from my HTC_Amaze_4G using xda premium
I asked a question , i could speak and ask question's. kk .
Jaywan said:
For the record yes it dose, but your a dev next time try it b4 you post saying it don't work because u make yourself seem like you don't know what your talking about
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Revolution said:
Alright , i mean like will it let you add edit file's in /system such as editing framework ?
Click to expand...
Click to collapse
Yes, you can make changes (add/edit/delete) to the files in /system.
I added:
/system/bin/su
/system/app/TitaniumBackup.apk
and deleted:
/system/app/teeter.apk
/system/app/teeter.odex
I did not edit anything in /system but I could if I had a reason to.
-xdadevelopers-user
for what it's worth...
I used the UOT kitchen to modify the battery to include percent. Since we don't have recovery yet I manually pushed the framework-res.apk and SystemUI.apk and then manually deleted the dalvik-cache. Now my status bar has the modified battery. Woohoo!
I was going to build a recovery today but android.git.kernel.org is STILL DOWN. Since the instructions I have require it I guess I'll wait for someone who already has the sources or until android.git.kernel.org comes back (I'm starting to wonder if it ever will).
-xdadevelopers-user
This is ****ing GENIUS work! Good job man. Pioneering for our amaze!
Not sure what I might be doing wrong but my su disappears after a reboot.
Try pushing to both xbin and bin
Sent from my HTC Sensation Z710e using xda premium
I did... No dice.
can you guys tell me what phone says when rebooting into hboot when its searching for a .zip, .nbh etc
its something like this
Example Sensation): PG58IMG.zip
It's not working for me.
C:\Users\Administrator\Desktop>adb push zergRush /data/local/
20 KB/s (21215 bytes in 1.000s)
C:\Users\Administrator\Desktop>adb shell
$ chmod 755 /data/local/zergRush
chmod 755 /data/local/zergRush
$ /data/local/zergRush
/data/local/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[-] Cannot copy boomsh.: Permission denied
$
Click to expand...
Click to collapse
EDIT
I removed the files in the tmp directory and it worked!
BUT
It's not consistent. When I reboot the su file disappears.
I've unlocked my bootloader. This may be required. Can anyone confirm that this works/fails on a locked bootloader?
-xdadevelopers-user
Finally, you sir are a genius
Sent from my HTC_Amaze_4G using Tapatalk
xdadevelopers-user said:
I've unlocked my bootloader. This may be required. Can anyone confirm that this works/fails on a locked bootloader?
-xdadevelopers-user
Click to expand...
Click to collapse
I'm on a locked bootloader. It doesn't work.
cmenard said:
I'm on a locked bootloader. It doesn't work.
Click to expand...
Click to collapse
Confirmed, same result for me on a locked bootloader. On reboot, it all goes away (or comes back).