hi guys,
i have a wetab, and recently i installed windows 8 on it, and it works so good
since 2 days i liked to try and see how will android be on it but i dont want to format the windows 8
therefor i made an sd card bootable with android 4.0.3 installed on it, it the the project android-x86
in all cases all went well, but i realise that it have superuser.apk , and yes the rom is rooted, BUT
you cant grant access for root, what i mean is
i can open the root explorer, go to system/app delete what ever i want it work, but when i want to change permission
for example i cant it say i must gain root, i open superuser make the response always allow, but no clue, keep denying
everything...and what i saw also in system/app that all the apps permission is set to rwxrwxrwx and it is odexed rom
tried to update superuser...the same story never worked. tried to replace the su and busybox in system/xbin, and superuser.apk in system/app,
and su in system/bin with the latest versions....it didnt boot up lol the android is no longer detected.....and there is noway to go to recovery since it has not.....
so when there is root how i can edit or manage or gain root access ???
and by the way in terminal command
adb shell
root
i got this # so root is available
Lol....no one ?
Sent from my GT-N7100 using XDA Premium HD app
Related
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
smokin1337 said:
Install SuperSU from the market, then run it a popup will come up asking to update binary say yes.
Then use a file manager to go to /system/app and delete SuperUser.apk
After that the system will use supersu for everything asking you to grant permission just like superuser.
Click to expand...
Click to collapse
good looks bro.. worked perfect!!!!
evod3 said:
good looks bro.. worked perfect!!!!
Click to expand...
Click to collapse
Simply , you should have went to the official xda thread of super su by chain fire and should have flashed the zip. The zips removes the super user and replace it with super su
evo401 said:
is there any way to use the new super su instead of superuser?? how do i get rid of the superuser app?? thanks!
Click to expand...
Click to collapse
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Zeuszoos said:
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work.
Just make sure that it has Write access to the System partition. Even when in
Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
Wrong! Now you cannot grant root access to any app since you don't have the binary.
If you do the 3rd step you will lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store and update the binary then remove the old superuser apk as smokin1337 said. Your steps are lengthy and will never work.
Or just flash the zip file.
Zeuszoos said:
Originally Posted by Zeuszoos
Here is how I replaced SuperUser with SuperSU. It is really easy to do!
Just follow the steps and you'll be up and running with SuperSU in a couple of minutes!
If you do not have "Root Explorer", any file manager with Root access will work. Just make sure that it has Write access to the System partition. Even when in Root Explorer, I think you have to turn this feature on. Not sure. Just check.
1) Use Root Explorer and delete SuperUser.Apk from the /system/app folder.
2) Go to the Android Market and download and install Super User.
3) Use Root Explorer again and delete SU from /system/bin.
4) Go to the Market and uninstall Super User.
5) Go to the Market and install SuperSU & Pro Key.
Click to expand...
Click to collapse
mnomaanw said:
Wrong! Now you cannot grant root access
to any app since you don't have the binary. If you do the 3rd step you will
lose root and you will have to root your phone again from recovery.
The correct step should be to just download supersu from play store
and update the binary then remove the old superuser apk as smokin1337 said.
Your steps are lengthy and will never work.
Click to expand...
Click to collapse
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Zeuszoos said:
First off, I don't understand the hostility.
Secondly, I'm not the one who's wrong. You are, sir. And I find it pretty arrogant for someone to be so rude and make such a statement to someone as if iwhat they're saying is a fact, when the person they're commenting to just finished stating that they had already done it. Don't ya think?
Or did you not read the part where I said, "This is how I DID IT."???
In fact, I had just finished performing these same steps on my "Samsung Galaxy Note 2" and my "Samsung Galaxy Galaxy Tablet", not an hour before I posted them here and guuess what? I have Root access on both and no recovery was necessary!
Now you can continue making the same claim if you wish. Or you can acknowledge that "I did it successfully" outranks you saying "it won't work".
The steps I posted above work just fine. You don't have to worry about losing Root access when you boot your device, because you never reboot your phone before SuperSU is on it and you have the binary installed again. I mean, what do you think SuperSU puts on your phone? Could it be a binary, hello??? <lol>
Of course, the one thing to note is whether you have it installed in /bin or /xbin. If you don't find "su" in /bin then you now know where to look.
Click to expand...
Click to collapse
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
mnomaanw said:
Oh ok I did not want to sound rude sorry.
I was under the impression that deleting su binary will not allow the supersu to install its su binary, but yeah if you have mounted the system rw then supersu should be able to install the binary. And your method should work without doing the 2nd and 4th step I guess. If you have more devices then maybe give it a try without doing 2nd and 4th step.
Click to expand...
Click to collapse
No problem.
As for mounting it read/write, yes, that does need to be done. I should have included that. Thanks for noting it.
There is a utility that will mount your system partition as writable when you boot it up. It's called "mount r/w" or something like that. It's in the Google Play Market. I think it has an icon of a yellow folder with a lock, or something like that. Most people recommend against doing that and if you don't want to do it that way, as I'm sure you know, root explorer can mount it writable until you tell it not to, or reboot..
I'm new here but have been messing around with android for awhile. I spent all afternoon searching for an answer but haven't been able to find anything. I had rooted my prime but not unlocked it while it was on ics, I used ota rootkeeper to keep root when I upgraded to jb but i think when asus sent out another update i forgot to save root. I still have su in /system/bin and superuser installed but it won't prompt me to give any programs root access. I typed in su in a terminal emulator and it said permission denied. so my question is, how do I get root back without unlocking?
Does this thread help ? http://forum.xda-developers.com/showthread.php?t=1911261&highlight=partial+root
I was able to get root back back doing something similar. Somehow the permissions got messed up for su. I went into adb and got root permission through CD/ system then ./usr/we-need-root/su-backup; su. Then I pushed new su, busybox, and superuser.apk files and fixed the permissions and changed the owner of su using chown and chmod.
peterk-1 said:
Does this thread help ? http://forum.xda-developers.com/showthread.php?t=1911261&highlight=partial+root
Click to expand...
Click to collapse
recently bought was what supposed to be new lg g2. discovered it was rooted. have no need for root access at this time. is SuperSU the easiest way to "unroot"? it's already an installed app. thanks
*bump*
I don't know what is the right way. Maybe other people will help you.
mhale14 said:
recently bought was what supposed to be new lg g2. discovered it was rooted. have no need for root access at this time. is SuperSU the easiest way to "unroot"? it's already an installed app. thanks
Click to expand...
Click to collapse
SuperSU app isn't what grants you and/or apps superuser ( aka root ) rights: it's an app that stores in a database the apps you have granted root thus you don't get prompted everytime, It's the Android executable named su.
You at any time can uninstall both. The su binary typically is located in folder /system/xbin and/or folder /system/bin
I rooted my strange tablet using Kingo and apparently it was succesful:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-20_zpsurdgzj8p.png
But I have been trying for days to erase a file in /system and I have not been able to do it, I think I have read every relevant thread about this problem but no luck, I tried using ES and changed /system to r/w in the root options but when trying to delete the file all I get is operation failed, the same happens with all the other root explorers and tools. I even tried the solution on this thread: http://forum.xda-developers.com/ascend-p7/help/edit-replace-write-files-set-immutable-t2884172
but still can't delete it.
Also the app root toolkit for android gives me this weird error too:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-06_zps4nrxqiev.png
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-02_zpsa1ycwdwl.png
Do you have an app like root explorer that specifically asks for root permissions? It doesn't matter if you have root if the explorer can't use it
Sent from my Nexus 5 using Tapatalk
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Try installing root explorer and then attempt to delete the file, then it should instantly open a window asking for root. The of course grant the permission. That should always work, but if it doesn't just restart the tablet, if it still doesn't work it must mean you are deleting a file that is in use by the system. Otherwise i have no idea whats wrong
Sent from my Nexus 5 using Tapatalk
Talos91 said:
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Click to expand...
Click to collapse
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
JMink said:
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Rooted my device using kingo root, I didn't intall other recovery.
Bad idea to try and remove system files without a custom recovery and a nandroid backup made and stored in a safe spot. What are you trying to remove?
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Talos91 said:
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Click to expand...
Click to collapse
That is the binary. If you remove it, you wouldn't be rooted. Can you link the thread you are looking at? There's an app made specifically for replacing that su binary with SuperSU and it's binary called Super-SUme, though I believe it is a paid app.
I know it is the binary but according to this guy:
http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365/page23
(post 223)
""It appears kango wrote to /system/sbin/su whereas supersu wrote /system/xbin/su and subsequently supersu would keep wanting to update 'su' then fail.
The long and the short of it is once I manually removed /system/sbin/su supersu stopped telling me 'su' was outdated. I don't know android but I do know linux.
$PATH on my tablet has /system/sbin/ prior to /system/xbin/ so it would appear supersu is issuing 'su -V' as opposed to '/system/xbin/su -V' when it checks the version. The kingo 'su' was older than the supersu 'su'.
Dunno what the solution is 'cos the older 'su' is going to get called first & I figure there's nothing but trouble to be gained from changing $PATH globally. Nevertheless it might be enough to check $PATH for unwanted 'su' and flag them, possibly offer to remove them? In my case I renamed it "/system/sbin/su.ORIGINAL" so that it's still runnable in an emergency"""
If you rename it, it won't be able to run, and won't require removal.
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Talos91 said:
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Click to expand...
Click to collapse
Seems like the SU binary that Kingroot included is pretty finicky and only works for some things. I've rooted 100s of devices and have never had issues like that. Have seen complaints about other various oddities with Kingroot too. It's nice that it's easy and works on a variety of devices, but if you have only limited control then that kind of defeats part of the purpose of rooting it...
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
With Root Explorer, does it let you set the system to R/W? There's a little button at the top of the app that will say R/O or R/W for Read Only or Read Write. If you don't have R/W to the system, then you are unable to make changes to it.
I just renamed file su and then it became able to be deleted.
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
Connect your android tablet device to your windows computer. Then enable usb debugging on your android tablet. Then open the windows program called cmd. Then do these commands.
Code:
adb root
Code:
adb remount
Code:
adb shell rm /system/sbin/su
I have lenovo vibe shot and I have updated it with Android 6.0.1, rooted it with SuperSU 2.78
and installed systemless xposed framework on it all of the things are going well but
recently I tried to change the boot animation and I realized that I dont and I cant have writing access
to /system and any of its sub folders (i want to replace a couple of MP4 files inside /system/media
no matter if I use mount commands from adb from PC or any other app in my mobile, write access will not be given
for example ES File explorer says it is read only, when I click on write and click OK, it will show no error, but going to
same setting again it shows read only selected again
similar is the case with Root Browser
I think it is due to systemless root
But is there any way I can get write acccess to /system/media ???
plz help
usman400 said:
I have lenovo vibe shot and I have updated it with Android 6.0.1, rooted it with SuperSU 2.78
and installed systemless xposed framework on it all of the things are going well but
recently I tried to change the boot animation and I realized that I dont and I cant have writing access
to /system and any of its sub folders (i want to replace a couple of MP4 files inside /system/media
no matter if I use mount commands from adb from PC or any other app in my mobile, write access will not be given
for example ES File explorer says it is read only, when I click on write and click OK, it will show no error, but going to
same setting again it shows read only selected again
similar is the case with Root Browser
I think it is due to systemless root
But is there any way I can get write acccess to /system/media ???
plz help
Click to expand...
Click to collapse
Root properly
I did it twice using TWRP I flashed Super SU 2.78 2 times, it never showed any error
and went fine
Plz tell me a little more if you mean something else by root properly
Any app that needs root access is working perfectly fine except for this permission
setting issue on /system