Please help me out. I have followed the rooting guide 'Method one' instructions exactly as given. Only I get stuck at the SuperOneClick part. I get failed at Getting mount path...
After getting error I see two new apps installed
CWM and SuperSU
I don't see busybox anywhere as mentioned in the guide
Thanks in advance
SuperOneClick v1.9.5.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
4.0.3
OK
4.0.3
Pushing psneuter...
4727 KB/s (585731 bytes in 0.121s)
OK
chmod psneuter...
OK
Running psneuter...
ROOTED
Pushing busybox...
2327 KB/s (1062992 bytes in 0.446s)
OK
chmod busybox...
OK
Getting mount path...
rootfs on / type rootfs (ro,relatime)
FAILED
That said on checking with Root Checker app by joeykrim it shows I have root access.
I haven't done the part after SuperOneclick where I have to install stock kernel.
Someone please tell me soon what to do next cause I'm just stuck here scared to go ahead and use my phone. I've still put it on flight mode for past almost 2 hours
bump
use cfroot or the root/unroot without insecure kernel for ICS. superone click wont work.
Related
update my motorola atrix 4.1.57 version sent by day 29/03/2011 att and now does not serve me the superone click, I am root on my phone icon but does not root permission have tried to install / uninstall again with the superoneclick but neither can remove the icon or the permission of root Once again.
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
853 KB/s (585731 bytes in 0.670s)
OK
chmod psneuter...
OK
Running psneuter...
Sorry for my English but I'm using a translator
superoneclick doesn't work on 4.1.57, and if you had root before the update you will not have it afterwards unless you followed this steps beforehand:
http://forum.xda-developers.com/showthread.php?t=1013931
You should also not use SuperOneClick if you use the SBF to get back to 4.1.26
You should use aRoot. It's very simple and will work over SuperOneClick.
Sorry if I sound like a **** but that is not a dev question....and you could of read a few of the threads to see why it wouldn't work
Not dev, moved to a proper forum
Hi guys! I've been researching on how to root and flash my device for a long time now, but it seems that every forum/sites I go through only confuses me all the more, I am a GT-p1010 user from the philippines with a 2.2.1 firware, kerenel 2.6.32.9 and nuildnumber FROYO.DXKC2, I've tried to download z4root but everytime I install it my antivirus goes off and uninstalls it for me, I also tried the superoneclick and this is what it said
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.27s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.53s
Waiting for device...
OK 0.33s
2.2.1
Getting manufacturer...
samsung
OK 0.03s
Getting model...
GT-P1010
OK 0.03s
Getting version...
DXKC2
OK 0.02s
Checking if rooted...
False
OK 0.05s
Installing BusyBox (temporary)... - Step #1
621 KB/s (1062992 bytes in 1.671s)
OK 1.95s
Installing BusyBox (temporary)... - Step #2
OK 0.02s
Rooting device... - Step #1
cannot stat 'C:\Users\Acer\Downloads\SuperOneClickv2.1.1-ShortFuse\Exploits\psneuter': No such file or directory
OK 0.31s
Rooting device... - Step #2
Unable to chmod /data/local/tmp/psneuter: No such file or directory
OK 0.08s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
./psneuter: not found
FAILED
I alsoo tried to root it with zergrush but it also failed, I am really getting desperate I need help!
rex013090 said:
Hi guys! I've been researching on how to root and flash my device for a long time now, but it seems that every forum/sites I go through only confuses me all the more, I am a GT-p1010 user from the philippines with a 2.2.1 firware, kerenel 2.6.32.9 and nuildnumber FROYO.DXKC2, I've tried to download z4root but everytime I install it my antivirus goes off and uninstalls it for me, I also tried the superoneclick and this is what it said
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 0.27s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.53s
Waiting for device...
OK 0.33s
2.2.1
Getting manufacturer...
samsung
OK 0.03s
Getting model...
GT-P1010
OK 0.03s
Getting version...
DXKC2
OK 0.02s
Checking if rooted...
False
OK 0.05s
Installing BusyBox (temporary)... - Step #1
621 KB/s (1062992 bytes in 1.671s)
OK 1.95s
Installing BusyBox (temporary)... - Step #2
OK 0.02s
Rooting device... - Step #1
cannot stat 'C:\Users\Acer\Downloads\SuperOneClickv2.1.1-ShortFuse\Exploits\psneuter': No such file or directory
OK 0.31s
Rooting device... - Step #2
Unable to chmod /data/local/tmp/psneuter: No such file or directory
OK 0.08s
Rooting device... - Step #3
OK 0.02s
Rooting device... - Step #4
./psneuter: not found
FAILED
I alsoo tried to root it with zergrush but it also failed, I am really getting desperate I need help!
Click to expand...
Click to collapse
You must root your tab. The following is the easiest guide:
http://androidadvices.com/how-to-update-samsung-galaxy-tab-wifi-p1010-to-xwkc1-froyo-2-2-1-firmware/
Follow instructions carefully on how to Odin.
thanx bro, but I'm afraid to flash my tab, since this is my first tab and my first time to flash or root anything, I might brick my tab...
Im experiancing this problem for a long time now... I have a galaxy s phone with darky's ROM v10.0 RC final. evidently it is rooted but some apps don't recognized it as a rooted phone. first, when i ran the superuser it fails and said com.noshufou.android.su is failed to work...and then theres a notificaTION that su binary is outdated but i tried to update it a million times but always failing, tried this su update fixer but still negative results. downloaded busybox installers the first one also failed to install busybox saying the directory where i want to put it has a problem, tried to put it to other option directory but still negative. the other busybox installer says that my phone is not rooted. how come this happens when titanium backup recognized my rooted phone. im running out of bright ideas here (if what Ive done can be classified as a bright ones hahaha) please someone help me...
Jayfunk said:
Im experiancing this problem for a long time now... I have a galaxy s phone with darky's ROM v10.0 RC final. evidently it is rooted but some apps don't recognized it as a rooted phone. first, when i ran the superuser it fails and said com.noshufou.android.su is failed to work...and then theres a notificaTION that su binary is outdated but i tried to update it a million times but always failing, tried this su update fixer but still negative results. downloaded busybox installers the first one also failed to install busybox saying the directory where i want to put it has a problem, tried to put it to other option directory but still negative. the other busybox installer says that my phone is not rooted. how come this happens when titanium backup recognized my rooted phone. im running out of bright ideas here (if what Ive done can be classified as a bright ones hahaha) please someone help me...
Click to expand...
Click to collapse
Try to update your busybox...
Hi everyone,
I'm really sorry if this has been brought up before. I've been searching and I can't find anything and I'm becoming frustrated and confused and my brain is about to explode. :laugh:
SO.. any help is incredibly appreciated.
I have successfully unlocked my phone.
I have successfully installed SuperUser v3.1.3.
SU Binary v3.1.1.
My phone is the HTC Incredible 2.
When I attempt to update the binary and get root access, the following displays:
"Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.1.1
Checking installed version = 3.1.1
Unpacking sutools... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Gaining root access..."
And that's where it all stops. I don't get an "okay", but instead a pop-up that reads "Activity Superuser Request (in application Superuser) is not responding". I am then given two options. Either I "Wait" or "Force Close". I wait and wait and wait and nothing succeeds. So, I have no other option but to "Force Close".
Why? What do I need to do? Please help me. Thank you.
Any help?
Invisible post?
Can someone please help me?
maybe you can try root with bin4ry
I've done quite a bit of searching over the past couple days but can't quite seem to find what I'm looking for.
I'm trying to root my Azpen A700 tablet manually. I've managed to load ChainsDD's Superuser.apk and su binary to the device in the appropriate locations. I've run all the chmods on them and can use ChainsDD's su binary when I run adb shell. I know I did this backward, but I'm really just playing with this thing, flying somewhat blind, and I don't much care if I brick it, so sue me.
So I tried to run 'fastboot oem unlock' just to see what it would do/if it would work. I loaded the latest ADB Composite Driver. I think the problem is that I can't get this POS to boot into the bootloader. It only wants to boot into recovery. If I run 'adb reboot-bootloader' or 'adb reboot bootloader' it always boots up into Android. I've tried using every volume/power button combo I can think of, and no dice. I really have no idea if the bootloader can even be unlocked. Does anyone have any ideas as to how to make this work?
By the way, I also tried SuperOneClick. It warned me that my device was already rooted, I'm guessing because it knows the su binary, and asked me if I wanted to root it anyway. I said Yes, and got the "failed to set prot mask" error on Step 4.
LeonardHatred said:
I've done quite a bit of searching over the past couple days but can't quite seem to find what I'm looking for.
I'm trying to root my Azpen A700 tablet manually. I've managed to load ChainsDD's Superuser.apk and su binary to the device in the appropriate locations. I've run all the chmods on them and can use ChainsDD's su binary when I run adb shell. I know I did this backward, but I'm really just playing with this thing, flying somewhat blind, and I don't much care if I brick it, so sue me.
So I tried to run 'fastboot oem unlock' just to see what it would do/if it would work. I loaded the latest ADB Composite Driver. I think the problem is that I can't get this POS to boot into the bootloader. It only wants to boot into recovery. If I run 'adb reboot-bootloader' or 'adb reboot bootloader' it always boots up into Android. I've tried using every volume/power button combo I can think of, and no dice. I really have no idea if the bootloader can even be unlocked. Does anyone have any ideas as to how to make this work?
By the way, I also tried SuperOneClick. It warned me that my device was already rooted, I'm guessing because it knows the su binary, and asked me if I wanted to root it anyway. I said Yes, and got the "failed to set prot mask" error on Step 4.
Click to expand...
Click to collapse
Why do you think you need to get into the bootloader? The device already has root access through ADB. Just open an ADB shell and replace the su binary with one that doesn't restrict user gaining root.
BLuFeNiX said:
Why do you think you need to get into the bootloader? The device already has root access through ADB. Just open an ADB shell and replace the su binary with one that doesn't restrict user gaining root.
Click to expand...
Click to collapse
Well, that's what I thought I did. I have the ChainsDD su binary in /system/xbin with a symlink, /system/bin/su, that points to it. I ran 'chmod 06755 /system/xbin/su' on it so the setuid and setgid are applied, just like the stock su binary. But if I run Titanium Backup, it says it can't get root through /system/bin/su. And if I run su through a Terminal Emulator on the device, I get an error "explosion" of permissions errors. Is there another su binary I should be using instead? Or maybe there's something that Superuser.apk needs to do that I'm missing?
I guess the reason I'm trying to get into the bootloader is so I can unlock it and try rooting the easy way, to see what's different from what I've done so far. I didn't really understand why I needed to get into the bootloader if I was so easily able to replace the su binary, but I figured maybe there was something that needed to be done with file permissions that couldn't be done if, say, /system was mounted, or something like that. Does that idea hold any water?
Maybe using the su binary I have I can modify permissions on files where needed?
Thanks for the help!
LeonardHatred said:
Well, that's what I thought I did. I have the ChainsDD su binary in /system/xbin with a symlink, /system/bin/su, that points to it. I ran 'chmod 06755 /system/xbin/su' on it so the setuid and setgid are applied, just like the stock su binary. But if I run Titanium Backup, it says it can't get root through /system/bin/su. And if I run su through a Terminal Emulator on the device, I get an error "explosion" of permissions errors. Is there another su binary I should be using instead? Or maybe there's something that Superuser.apk needs to do that I'm missing?
I guess the reason I'm trying to get into the bootloader is so I can unlock it and try rooting the easy way, to see what's different from what I've done so far. I didn't really understand why I needed to get into the bootloader if I was so easily able to replace the su binary, but I figured maybe there was something that needed to be done with file permissions that couldn't be done if, say, /system was mounted, or something like that. Does that idea hold any water?
Maybe using the su binary I have I can modify permissions on files where needed?
Thanks for the help!
Click to expand...
Click to collapse
Do it again, but us the su binary found here: https://plus.google.com/103583939320326217147/posts/4FemP5ACLSn
BLuFeNiX said:
Do it again, but us the su binary found here:
Click to expand...
Click to collapse
That did it, thanks!
Maybe now I'll root my Nexus 4 this way...
LeonardHatred said:
That did it, thanks!
Maybe now I'll root my Nexus 4 this way...
Click to expand...
Click to collapse
No problem.