Related
If you noticed, Superuser updated to 2.3 - make sure you do an nandroid backup before you attempt to apply it. I was able to apply it, and when I attempted to launch the application, it FCed on me. I was able to grant ROM Manager SU rights, but I just wanted everyone to be aware. You can see the original Superuser 2.3 thread here.
I did a nandroid restore and got rid of it since it was FC like mad.
SU 2.3.1 is up, and so far seems to be working without any issues.
maltzer said:
SU 2.3.1 is up, and so far seems to be working without any issues.
Click to expand...
Click to collapse
FYI, I am also using 2.3.1 without problems. The only crash I noticed was when you checked the log before actually trying anything that used superuser it caused a FC. After using a couple of root apps, I can check the log without a crash.
Can I flash the 2.3.1 over the 2.3 version? I can't find any confirmation that this is the right procedure to update su.
Can't even get this to install properly on the Captivate. Installation aborted every time in recovery mode.
When I try to install from the market, I get package not signed properly error. What is the correct procedure to update your SuperUser.apk file?
might be helpful
rajendra82 said:
When I try to install from the market, I get package not signed properly error. What is the correct procedure to update your SuperUser.apk file?
Click to expand...
Click to collapse
if you go to the g1 thread and go to themes and ****....they got the apk for free......just gotta sideload it...ya digg
oh yeah it works perfect on my captivate....
I have su 2.3.1 and it works perfectly i upgraded it from market had 1.8 before i think on one of the one click root packages. No issues at all though and im back on stock rom right now.
In order to root your Nexus S (from Gingerbread to ICS!) I have made a script that all you need to do is launch with your PC! (credits to saurik for the exploit)
Hope this will help you
All you need to do, is run the script! Then, plug-in your phone (needs to be on with USD ADB DEBUG ON) and done!
You can download it here: http://www.mediafire.com/?qhefhtgs20fdtsd
This will root your phone, and then you can afterwards flash ClockworkMod from the market and then reboot into recovery =)
Peace be with you.
xian1243 said:
In order to root your Nexus S (from Gingerbread to ICS!) I have made a script that all you need to do is launch with your PC! (credits to saurik for the exploit)
Hope this will help you
All you need to do, is run the script! Then, plug-in your phone (needs to be on with USD ADB DEBUG ON) and done!
You can download it here: http://www.mediafire.com/?qhefhtgs20fdtsd
This will root your phone, and then you can afterwards flash ClockworkMod from the market and then reboot into recovery =)
Peace be with you.
Click to expand...
Click to collapse
I'll test it later. Does this use fast boot to unlock?
And saurik? He's the king of cydia. He got the exploit?
Sent from my Nexus S using Tapatalk
It worked great, thanks guys
haha..rooted..thanx!!!!!!...
is there a way to make this work with a xoom?
When I try this it shows that it worked, but it doesn't seem to load properly since ROM manager says superuser not found. When I try to update the bineries it also fails on "checking current install path".. failed to find currently installed su binary.
Any ideas?
Edit: I'm running gb 2.3.6
Zorrich said:
When I try this it shows that it worked, but it doesn't seem to load properly since ROM manager says superuser not found. When I try to update the bineries it also fails on "checking current install path".. failed to find currently installed su binary.
Any ideas?
Edit: I'm running gb 2.3.6
Click to expand...
Click to collapse
same here...
does it work with all android phones.like xperia phone.
Thanks!
Just ordered my wife a Nexus S, will try this Friday and report back!
Nice!
Ran it and it worked. Well, ran it and then had to do a few things to prove that it had worked.
After running the script, you have to install Superuser in Google Play Store (Market). Then, I installed MyBackup Pro (paid version) which does a few more fancy things if it has root access. When I ran MyBackup Pro, it said that I have superuser access.
Sweet!
I ran this on a Nexus S i9023 running ICS 4.0.3.
It looks like root access remained after reboot. Pretty good!
COOL! Thanks for sharing! The Nexus is en route!
ivd269 said:
Nice!
Ran it and it worked. Well, ran it and then had to do a few things to prove that it had worked.
After running the script, you have to install Superuser in Google Play Store (Market). Then, I installed MyBackup Pro (paid version) which does a few more fancy things if it has root access. When I ran MyBackup Pro, it said that I have superuser access.
Sweet!
I ran this on a Nexus S i9023 running ICS 4.0.3.
It looks like root access remained after reboot. Pretty good!
Click to expand...
Click to collapse
This is an early April Fool right? The Nexus S is completely open and doesn't need exploits to gain root. Unlock the bootloader then you can use fastboot to install a custom recovery image. Simples.
Hi there, have you made one for the MyTouch4G or do you know if one does exist for it ?
Thanks
Envoyé depuis mon Nexus S avec Tapatalk
Didn't work for me.
Ran the zip, plugged phone in. Downloaded superuser, and then Rom Manager. Rom Manager couldn't see root.
Modified version of this:
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
worked for me.
I had to transfer Rom Manager to the phone via email because I couldn't get it to download anything from the market on wifi. Flashed recovery through CW. MIUI is now on the pone.
SWEET!
got it to work to install ota 4.0.4 manually via cwm...only thing is i lost root and it seems this exploit doesnt work on ota 4.0.4 so i cant run it again...
this is cool
thanks for this man...i used it when i got 4.0.3 and worked well on my i9023...ini 4.0.4 it diddnt work...but i restore back to 4.0.3 and installed voodoo ota root keeper from the market...and i restored the the root ran with the script in this poost in one click in 4.0.4 . awsome
Does it wipe your phone in the process?
chushev said:
Does it wipe your phone in the process?
Click to expand...
Click to collapse
nope....
How can we use this in 4.0.4?
flibblesan said:
This is an early April Fool right? The Nexus S is completely open and doesn't need exploits to gain root. Unlock the bootloader then you can use fastboot to install a custom recovery image. Simples.
Click to expand...
Click to collapse
That requires wiping your phone, and unlocking your bootloader. Appears this works with a locked bootloader.
This is driving me nuts... I was on 5.1.1 and I am trying to get it rooted.
I'm following a guide which goes like this..
1. downgrade to kitkat 4.4 using flashtool
2. root 4.4
3. Install custom recovery
4. Flash 5.1.1 pre-rooted zip
I have had problem after problem and I think something may have screwed up along the way.
I finally managed to get kitkat installed using flashtool and a generic C6903 .108 ftf.
Problem 1... I used 'Easy Root tool' from xda to root kitkat... but it seemed to hang at the cleaning up' stage - is this a problem?
Problem 2... every time I restart my phone - kitkat asks what language etc. Whats that all about?
PROBLEM 3. The guide Im following says to install busybox after rooting kitkat.
I've tried 2 different busybox installers and both of them fail when trying to install bb.
QUESTION: Are these 3 problems linked and will it prevent me from continuing with the guide I am trying to follow??? i.e. do I need busybox to install XZ Dual Recovery and therefore a pre-rooted zip?
Root Checker basic says kitkat is rooted, as does the first busybox installer.
I'm taking a short break from this nightmare, so in the meentime if any of you chaps could advise me on whether or not its ok to continue or if I have fecked up the whole process, that would be great.
Thanks in advance
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Gamer4Life said:
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
Click to expand...
Click to collapse
Problem1... thank you, I'll try again
Problem2... Thanks. I thought It could be the lack of a SIM card and then I thought no! that can't be it lol... as usual - I was wrong ha
others... yeah mate, tried 2 different installers from play store - no joy with either.
Thanks for your help
xasbo said:
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Click to expand...
Click to collapse
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
thesweeney80 said:
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
Click to expand...
Click to collapse
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Gamer4Life said:
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
Click to expand...
Click to collapse
thanks for the tip mate but no joy see my reply to xasbo, cheers
xasbo said:
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Click to expand...
Click to collapse
Thanks mate. I was hoping Gamer4life might be right as there was no Supersu installed.
I installed supersu from play store no problem... but when I try to update binaries it says' update failed. Please reboot and try again.'. tried reboot but same story.
I guess I'll try 'easy root tool' again and then will give kingroot a bash if needbe.
One last pre-emptive question...
If I root kitkat using kingroot... should I replace kinguser with supersu before proceeding with XZDR and a pre-rooted zip or will kinguser be sufficient to continue.
Many thanks to you and everyone else who has tried to help me with this clusterf*ck,.. I appreciate it
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Gamer4Life said:
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
must have been a glitch in the matrix mate becuase its now working (Possibly thanks to your suggestion of installing Supersu?).
I reconnected to PC in order to give 'easy root tool' another crack at it.
As soon as I start install.bat It says checking if device is rooted AND I get a superuser request on my phone for adb.shell - Happy days!
I granted root access to adb shell and the root tool says Job Done. Root success etc.
So I disconnect and try to update su binaries and it worked first go!!!
*Touch wood* I think I'm now past the tricky part and it should be plain sailing from here on in. lol
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Gamer4Life said:
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
Correct, TowelRoot doesn't work for this version.
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
thesweeney80 said:
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Click to expand...
Click to collapse
:good: godspeed
@thesweeney80 you are welcome have fun
xasbo said:
:good: godspeed
Click to expand...
Click to collapse
Gamer4Life said:
@thesweeney80 you are welcome have fun
Click to expand...
Click to collapse
you fellas are the muts nuts.
All done, everything went smoothly once I got kitkat rooted properly.
MANY thanks for all your help.
Honestly I wouldnt even bother owning a smartphone if it wasnt for the peeps on XDA... F*cking awesome. THANKS :good: :highfive:
:good: awesome! don't forget to pay it forward sometime.
Hey XDA & Note 8'ers ,
I've finally got around to rooting my Note 8 - all is smooth and get a root confirmation through various apps.
But when I try and get SuperSU running, it keeps giving me the error 'SU Binary Occupied'.
I've flashed it with Stock, and also SuperSU through various methods,
but I keep getting the error of the SU Binary being occupied.
I've followed the instructions given by the SU App to deal with the above issue, but keep getting the same issue.
Any suggestions or advice on what I might have done wrong to keep causing this?
I'd like to get SuperSU working, but it's not the only app that is causing me issues in recognising that the device is rooted.
It's an Australian Note 8 (SM-N950F)
Cheers!
I have not rooted my note 8, but, I had a simmilar issue with my note 4, The SU that came with root did not work as intended, so I searched and found that there were several more SU apps, I dont remember names, the thing is, I tried several SU, untill one worked
I've heard of the issue but never personally encountered it ever on any of my Android phones. Not sure if it has anything to do with Super Su versions but I have used 2.82, 2.82-SR4, & 2.82-SR5 without any issues. I'm currently using 2.82-SR4 on my F.
is magisk installed? if not, try to install magisk manager and check if you might be rooted through that app. if yes you dont need super su.
winol said:
I have not rooted my note 8, but, I had a simmilar issue with my note 4, The SU that came with root did not work as intended, so I searched and found that there were several more SU apps, I dont remember names, the thing is, I tried several SU, untill one worked
Click to expand...
Click to collapse
bober10113 said:
is magisk installed? if not, try to install magisk manager and check if you might be rooted through that app. if yes you dont need super su.
Click to expand...
Click to collapse
Cheers, I had Magisk Manager already installed, but SuperSU hadn't been activated for the specific app, so it wasn't been given root access!
Easy solve.
rajalot said:
Cheers, I had Magisk Manager already installed, but SuperSU hadn't been activated for the specific app, so it wasn't been given root access!
Easy solve.
Click to expand...
Click to collapse
very simple solution reflash kernel reboot go to app drawer unistall magisk long press icon back to twrp flash supersu wipe cache dalvik reboot
So I had trouble installing Viper through Magisk on Pie on my Exynos Note 9. It always told me to reinstall the drivers, but that didn't seem to work.
But I found a solution:
On XDA-Labs is a new version of viper available (Version 2.6):
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Simply install this version (I chose the beta), give it root permissions and you are set!
I also installed audio modification lib from Magisk to be on the safe side.
Only issue I noticed is that YouTube videos seem to hang for a few seconds before they start playing (I am using YouTube vanced from Magisk). Apart from that everything seems to be working well!
Hope that helps everyone who is having trouble on Pie!
It isn't asking me for root permission?
Strange.
But you are rooted with Magisk and have Magisk Manager installed?
Is the app showing up in Magisk Manager under the SuperUser section?
Maybe trying to install the app again solves your issue.
Rowe90 said:
Strange.
But you are rooted with Magisk and have Magisk Manager installed?
Is the app showing up in Magisk Manager under the SuperUser section?
Maybe trying to install the app again solves your issue.
Click to expand...
Click to collapse
Correct, and nope it isn't showing up in the superuser section. Re-installing did nothing, it isn't working without root, atleast that's why I think it isn't working.
aussiesausage said:
Correct, and nope it isn't showing up in the superuser section. Re-installing did nothing, it isn't working without root, atleast that's why I think it isn't working.
Click to expand...
Click to collapse
Yeah it needs root to put itself into some system files.
I just saw they released an update yesterday which is know marked as stable. (version 2.7). Maybe you have better luck with that.
It was working on 2.7 but it suddenly stopped
Now it's not enabled and not processing
Don't know how to fix
(Btw on Samsung Galaxy A8)
This was the only thing that worked. I've been trying different things and searching for hours. The stable version does not work on my exynos note 9. The beta does though!