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
Related
Okay, so I've noticed that this rooting method is a little unconventional. It works through a compromised Fota.pkg which has setuid on /system/bin/sh as root. This is not a very safe, as any application that runs sh will gain root access to your system. Scary... :S Anyway, in order to fix this we need to take a few steps.
It is important that you do these in order, otherwise you may lose root access
Install a proper SU with whitelist
1. Download http://bit.ly/aWgALL
2. Unzip the system folder.
3.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push system/bin/su /sdcard/su
adb push system/app/Superuser.apk /sdcard/Superuser.apk
adb shell dd if=/sdcard/su of=/system/bin/su
adb shell dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
adb shell chmod 6777 /system/bin/su
adb shell chmod 644 /system/app/Superuser.apk
4. Reboot your phone.
Fix sh to not setuid to root
1.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell chmod 0755 /system/bin/sh
Properly install busybox
1. Here, it's easier to look for the busybox installer app from the market and then install from there. If you did everything correctly, then after you hit install in the busybox app a prompt will come up asking you to allow the app to have root. Hit allow.
You're done!
this might be stupid questions, i know. But where should I unzip the system folder that mentioned to? And where to type those command?
chai_archer said:
this might be stupid questions, i know. But where should I unzip the system folder that mentioned to? And where to type those command?
Click to expand...
Click to collapse
If you followed the root guide you can put it in the step 4 folder.
Then hit windows key + r and in the box type CMD
A console window comes up.
in the console window type cd <path.to.your.step.4.folder>
then go from there.
zephyrix said:
Properly install busybox
1. Here, it's easier to look for the busybox app from the market and then install from there. If you did everything correctly, then after you hit install in the busybox app a prompt will come up asking you to allow the app to have root. Hit allow.
You're done!
Click to expand...
Click to collapse
i did everything as mentioned but it dint ask me for permission wen installin busybox is it because i had it installed sometime before runnin this guide?
yea i knw im a noob after all
bcool15 said:
i did everything as mentioned but it dint ask me for permission wen installin busybox is it because i had it installed sometime before runnin this guide?
yea i knw im a noob after all
Click to expand...
Click to collapse
yep.
if you check the superuser app it should already be there.
zephyrix said:
yep.
if you check the superuser app it should already be there.
Click to expand...
Click to collapse
all i see in superuser app is titanium backup pro
that's strange. does busybox report that it's installed?
zephyrix said:
that's strange. does busybox report that it's installed?
Click to expand...
Click to collapse
nope it doesnt
well i tried all this and now i lost my root. Did EXACTLY what's written. Anyway to reverse this and get my root back?
unknown13x said:
well i tried all this and now i lost my root. Did EXACTLY what's written. Anyway to reverse this and get my root back?
Click to expand...
Click to collapse
i think i lost mine too but to reactivate there is command or prolly i just messed up summmwhere n redid my whole root with v3 update
bcool15 said:
i think i lost mine too but to reactivate there is command or prolly i just messed up summmwhere n redid my whole root with v3 update
Click to expand...
Click to collapse
use "su" to get root access... allow when the Superuser Whitelist notification pops up.
it worked for me....followed the steps, after i downloaded the busybox app i opened it and a box popped up "Superuser Request", it had discription of the busybox app and then asked whether to allow or deny the request....i then checked the superuser app and was able to see the busybox app in thr....
can anyone confirm if these steps were added in the new root method? please
bcool15 said:
can anyone confirm if these steps were added in the new root method? please
Click to expand...
Click to collapse
I'd like to know that too, I mean, in 2v2 do we still need to do the whitelist thing?
root in adb
I tried this on the last root (ROOT_F2v2) and I lost root in adb..
I still had regular root
I had to revert it back with "chmod 6777 /system/bin/sh" to get adb do admin task again.. (I use adb regularly)
Does anyone know how to secure sh and still have root in adb?
Regards.
th4r said:
I tried this on the last root (ROOT_F2v2) and I lost root in adb..
I still had regular root
I had to revert it back with "chmod 6777 /system/bin/sh" to get adb do admin task again.. (I use adb regularly)
Does anyone know how to secure sh and still have root in adb?
Regards.
Click to expand...
Click to collapse
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Chillest said:
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Click to expand...
Click to collapse
Yes that give me root in adb shell but adb is still running unprivileged.
I believe it's because we can't patch the bootloader yet, so we still have getprop ro.secure 1. :'(
I did a little script to toggle setuid on /system/bin/sh when I'm doing root stuff from adb
Sent from my rooted X10i
I have installed this to protect the system.
The only concern I have is i cannot run for example my cleaning script.
If i type into cmd ;
"adb shell su" it comes up with a # and freezes. If i type in
"adb shell<enter>
su" it works fine. and i can paste all the commands in line by line.
If i do either in a bat or cmd file it crashes. How do i run scripts as su
Here are the answers....
bcool15 said:
can anyone confirm if these steps were added in the new root method? please
Click to expand...
Click to collapse
No they were not. The reason is that many of the rooting steps rely on a setuid "sh"
gfgodoy said:
I'd like to know that too, I mean, in 2v2 do we still need to do the whitelist thing?
Click to expand...
Click to collapse
Yes
Chillest said:
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Click to expand...
Click to collapse
So what? The uid for the shell application launched after invoking "adb shell" is not going to match any of the installed applications anyways. The thing is that Superuser.apk installs a mechanism by which the user (human) can detect when an application is requesting root access. Based upon the nature of the application you may or may not want to grant root access. That is the whole point.
th4r said:
Yes that give me root in adb shell but adb is still running unprivileged.
I believe it's because we can't patch the bootloader yet, so we still have getprop ro.secure 1. :'(
I did a little script to toggle setuid on /system/bin/sh when I'm doing root stuff from adb
Sent from my rooted X10i
Click to expand...
Click to collapse
Oh yeah? I just use "su" whenever I want root access... and I didnt have to write any scripts to enable/disable it.
k1ckn1ck said:
I have installed this to protect the system.
The only concern I have is i cannot run for example my cleaning script.
If i type into cmd ;
"adb shell su" it comes up with a # and freezes. If i type in
"adb shell<enter>
su" it works fine. and i can paste all the commands in line by line.
If i do either in a bat or cmd file it crashes. How do i run scripts as su
Click to expand...
Click to collapse
Then you shouldn't be rooting in the first place. Take my advice, lay off the rooting. It definitely doesn't have anything that will be of advantage to you.
j4mm3r said:
Then you shouldn't be rooting in the first place. Take my advice, lay off the rooting. It definitely doesn't have anything that will be of advantage to you.
Click to expand...
Click to collapse
easy now, it's a fair question, would be nice to be able to run cleaning scripts on a protected system. no need to be a prick
in answer to the question though, once the batch starts adb shell, it won't continue till that process ends
I did some googling for some comandline tools that might allow sending keystrokes to a process, but nothing easy appeared, looks like your only option is to use a linux friendly notepad to create some shell scripts you can execute from the sdcard. i.e. on device
su
chmod 755 /sdcard/myscript.sh
./sdcard/myscript.sh
easiest way to do scripts on a secured root IMO
Edit: Im stuck. I cannot root my phone because something is wrong with Superuser.apk, and I can't uninstall superuser because I can't get root. And if I try to install Superuser it just fails because it's already in there. So I have no idea what to do now, I need to return this phone to the Verizon store and I can't get the Superuser app off the phone. Any ideas?
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=6978379
should work. I did this to upgrade from market the version that came with the lag fix from the market.
I couldn't get that to work..
What happens when you adb shell into the device, and do 'su'. If you get a # prompt, you have root.
You don't need Superuser.apk to have root access. You can always run the rage.bin process to get a root shell. From there you should be able to at least rename Superuser.apk to something like Superuser.apk.old.
Yeah, I can type su and get the # prompt. Is this what runs the rage.bin:
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
?
Sorry, Im new to the ADB process. How would I go about renaming? I wanted to use something like root explorer to find the file and remove or rename it, but I can't get any root apps to work. Obviously because Superuser doesnt function I don't get permission prompt. Root explorer either crashes or says to restart to get the permission prompt.
GHII said:
Yeah, I can type su and get the # prompt. Is this what runs the rage.bin:
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
?
Sorry, Im new to the ADB process. How would I go about renaming? I wanted to use something like root explorer to find the file and remove or rename it, but I can't get any root apps to work. Obviously because Superuser doesnt function I don't get permission prompt. Root explorer either crashes or says to restart to get the permission prompt.
Click to expand...
Click to collapse
If you can do "su" and get the # prompt, forget about rage.bin. You have root access, it's just Superuser that's screwed up.
go to your # prompt and do the following
cd /system/app
mv Superuser.apk Superuser.apk.old
See if that gets you any further as far as being able to re-install
I appreciate your help more than you know, really, thanks. I tried that and I get 'failed on 'Superuser.apk' - No such file or directory. Can it be installed anywhere else, like in a temporary directory?
When I try adb install Superuser.apk it starts to then says:
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
So I tried what you just mentioned but using the above directory:
#
cd /data/local/tmp
mv Superuser.apk Superuser.apk.old
and it didn't give me any errors, just the #..but when I went and tried to install Superuser again I got the same error as above.
Ok, new update! I remember someone asking me to do ls in adb shell to get a list of what's in there..so, I did that with /system/app and I got a list...at the very bottom of the list was superuser.apk..this whole time i've been messing with Superuser.apk, a capital S. So, I used your mv method on the lower case version, seemed to work..but when I did adb install Superuser.apk I get Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
Didn't work but I feel Im getting closer
Wow, i just happen to look and the superuser app was no longer showing up in my apps..problem solved. Thanks again for everyone's help in this thread and others.
Hi, I rooted my Vribrant, both ways (manually and with one click root). I installed terminal emulator. I tried the su command to check if I am root. The # appears normally. However I tried deleting a file with Root explorer, inside the system folder, and when I get back it's still there. I also tried deleting it manually from Terminal EMulator with these commands:
su
cd system/apps
rm Swype.apk
and I get this:
rm failed for Swype.apk, Read-only file system
I also tried:
su rm Swype.apk
and this is returned:
Permission denied.....
I also tried the exact same thing from adb shell (which I had to allow in superuser permissions program), but it gave me the exact same results. What's wrong? Am I doing something wrong? Thanks
In root explorer, try hitting the r/w button at the top and see if that works.
Sent from my SGH-T959 using XDA App
I know about the button. The strange thing is that inside system folder it grands me r/w permissions, and no matter how many times a press the r/o button it doesn't change. Still gives the results I said. However, besides root Explorer what's wrong with terminal emulator and adb?
I'm not 100% sure how to mount as root in adb. I wish I knew myself heh.
Did any of those root methods install the superuser app?
Sent from my SGH-T959 using XDA App
Terminal Emulator should return a "#" after typing "su"
Sent from my SGH-T959 using Tapatalk
From a terminal write
adb root. (will give root)
adb remount. (will remount system as r/w)
adb shell cp /system/app/swype.apk /system/app/swype.apk.bak
Adb shell rm /system/app/swype.apk
This link is what i used to use to gain rw permissions
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Alternatively from terminal on the phone type
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Assuming your sys partition is mntblock3
Sent from Conical. 07
rbirg said:
I'm not 100% sure how to mount as root in adb. I wish I knew myself heh.
Did any of those root methods install the superuser app?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes both methods installed the "Superuser Permission" app.
I7oobie said:
Terminal Emulator should return a "#" after typing "su"
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
It does normally.
linuxmotion said:
From a terminal write
adb root. (will give root)
adb remount. (will remount system as r/w)
adb shell cp /system/app/swype.apk /system/app/swype.apk.bak
Adb shell rm /system/app/swype.apk
This link is what i used to use to gain rw permissions
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Alternatively from terminal on the phone type
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Assuming your sys partition is mntblock3
Sent from Conical. 07
Click to expand...
Click to collapse
I tried the first method but it didn't work. When I entered adb root, it said "adbd cannot run as root in production builds". I searched a bit and found that I must have a rooted kernel for this to work. (I guess it's different from the root method I tried in "how to root vibrant").
Anyway the second way worked, where i replaced mntblock3 with stl9 for my phone. I tried the rm command and it worked! However as soon as I exited terminal, I couldn't delete other files. I had to retype the command. I can't do this everytime I need access in System folder. Why is this happenning? Does this have something to do with the fact that root explorer cannot change r/w to r/o mode while in system folder?
what if you open Superuser
Click on Root Explorer.
Click on Forget.
Open Root Explorer and grant Root Access and check to remember it.
work now?
Moved to Q&A, please post in the correct section.
s15274n said:
what if you open Superuser
Click on Root Explorer.
Click on Forget.
Open Root Explorer and grant Root Access and check to remember it.
work now?
Click to expand...
Click to collapse
No it didn't work. I also installed the latest version of SuperUser 2.3.6.1. But without a difference unfortunately.
What works for me, is installing sgs tools, and whenever I want to do write operations on system folder, run the appropriate script from sgs and then use root explorer......
Although I think there's something wrong? Why doesn't the mount r/w button work in root explorer, and why do I have to remount the file system through SGS tools, every time for it to work?
makes no sense to me either. Have you uninstalled RE and the installed it back granting root once reinstalled?
Yes several times.....
I am giving up. I just have to go through the whole process every time. I found some other people having this issue. I am on stock JI6 firmware. Maybe when I read a little bit more I will flash a custom rom.
Download and install Super Manager. Pretty handy program to use for Root users.
I'm not sure what the issue is,but mine does it too. I'm running the "unofficial" froyo JK2 build,flashed via ODIN,and I'm having the same issues. root works,root file explorer is stuck in rw,won't let me switch to ro,and it can't do anything to files in / or /system. manually remounting it from terminal or sgs tools works.
msnuser111 said:
I'm not sure what the issue is,but mine does it too. I'm running the "unofficial" froyo JK2 build,flashed via ODIN,and I'm having the same issues. root works,root file explorer is stuck in rw,won't let me switch to ro,and it can't do anything to files in / or /system. manually remounting it from terminal or sgs tools works.
Click to expand...
Click to collapse
At least I am not the only one with this problem.... haha
I forgot to mention that I use Root Explorer version 2.12.2
When I try a custom Rom I will post the results....
^ why not get the update, .4 is the most recent build. Do you have an illegal copy?
It's not only root explorer. It happens with other file explorers too like android mate and super manager... Inside system folder whatever, I do doesn't happen unless I unmount and remount like before
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.
I was wondering if someone could help. I have followed all the instructions of this post http://forum.xda-developers.com/showthread.php?t=1886460 It says it is successful, but still do not have root access. Could someone tell me if they see something wrong?
Here is the log from Root Checker.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.98 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 91988 2012-11-20 09:39 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your C5155 device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market - http://goo.gl/NcnHn
Fixed
Removed Super SU all is now ok.
I have been trying to root my Kyocera Rise I just got a week ago, and I am having this problem as well. However it seems that removing SuperSU isn't doing the trick. What was your method of going about this? I'm so lost without root access . I followed the tutorial to a T, multiple times, as other users have suggested, and I get nothing! Thanks for your time!
I had the same problem I went into stuff folder of binry and replaced supersu with su, re-ran it and root took 1st time
Sent from my Amazon Kindle Fire using Tapatalk 2
Forgot this but make sure you open super su and in installing from within app and then uninstall in market before running with su apk.
Sent from my C5155 using Tapatalk 2
Could not get v17 to work. I saw in the thread v3 was supposed to so I tried it and after a few attempts I got it.
Sent from my LG-VM670 using Tapatalk 2
any luck on 4.0.4?
the latest krise firmware version is 4.0.4.
In the thread the guy who reported rooting success didn't say his version num, so it could be outdated information.
I am on 4.0.4, was not aware of any other version for this phone
Sent from my Amazon Kindle Fire using Tapatalk 2
jimchee said:
Forgot this but make sure you open super su and in installing from within app and then uninstall in market before running with su apk.
Sent from my C5155 using Tapatalk 2
Click to expand...
Click to collapse
Could you please be more specific with your procedure?
sonic_knx said:
Could you please be more specific with your procedure?
Click to expand...
Click to collapse
Since you have a rooted copy now, could i borrow a backup or a copy of the system folder because I installed hp beats audio installer (do not do) and my audio drivers are messed up. It is really taking a long time to get a copy so I was hoping that you guys would have a good copy. I also have another guy with the same issue so please help us.
the actual problem and a slight fix...
The actual problem/glitch with supersu is when it tries to promt access for su it freezes the app. When I tried unistalling supersu and installing superuser. It did not work for me even with the proper uninstall procedure (going into super su settings and click uninstall and prepare for new su app. Then go to the play store search supersu, google still thinks installed so click uninstall from there then immediatly search and install superuser.) I even tried going into the root setup folder I downloaded and switched the su apk files to start the root fresh... and still nothing. I figured out its the problem with the app trying to promt you for su access (ether app) bcs when I went into the settings I changed it to automaticaly grant su (TO EVERY APP READ BOTTOM DISCLAIMER) instead of promting you to ask for su.
DISCLAIMER: I AM NOT RESPONSIBLE FOR A ROUGE APP TAKING ADVANTAGE OF YOUR PHONE WITH YOUR SU SET TO GRANT ACCESS TO ALL APPS INSTEAD OF PROMTING YOU FOR YOUR ACTION ON ACCESS.
root VM rise
I used this method to root my Rise it says hydro but works on rise too.
http://www.cricketusers.com/content/646-root-cricket-wireless-kyocera-hydro-tutorial.html