Once rooted - Motorola Droid 3

Can i unroot if necessarry
Is there a way yet
Sent from my DROID3 using XDA App

If you don't install the su binary to /system/xbin all you have to do is reboot and the root access from adb is gone until you do the exploit again.

Wait so if i do the one click root can i unroot that
Sent from my DROID3 using XDA App

You would have to delete the su binary from /system/xbin and uninstall superuser.apk for it to be considered unrooted.

wat if you factory reset it doesnt unroot
esp if you install superuser from the market, its in /data vs. /system right?
but that would leave /xbin intact right? so youd kinda be stuck rooted rofl idk

whoopsiedaisy said:
wat if you factory reset it doesnt unroot
esp if you install superuser from the market, its in /data vs. /system right?
but that would leave /xbin intact right? so youd kinda be stuck rooted rofl idk
Click to expand...
Click to collapse
I'm not sure if a factory reset leave xbin intact or not but even if it did you could just adb in, use the exploit and remove su manually.

Just keep in mind...SuperUser.apk is not root. You can install that on a non-rooted phone, it just doesn't do anything.
Root is su, having (s)uper(u)ser access to the system. SuperUser.apk is just your (you the user) control over what is granted su rights. Without the SuperUser.apk, anything and everything that wanted superusers permissions would have it, definitely something you don't want.
I'm not sure a factory reset would remove su from /system/xbin but it would remove SuperUser.apk from /data/app. This would mean you'd have no control over what apps would want to take superuser permissions and access your filesystem.
While you have superuser permissions...just delete the /system/xbin/su and reboot.
Root also doesn't prevent OTA updates.....though you will probably lose root after an OTA update and have to redo the exploit.

Related

Why the root message isn't showed like Hero&Others ?

All others rooted phones have a message showed when an application asks root, why don't we have this on Tattoo ?
On Tattoo root permissions are always enabled
Ok, it's nice but we can't see which application ask root :/
Like Terminal Emulator, when you launch it, the shell is always in normal user "$", not in root :/
JoOoSs said:
Ok, it's nice but we can't see which application ask root :/
Like Terminal Emulator, when you launch it, the shell is always in normal user "$", not in root :/
Click to expand...
Click to collapse
This is true, but I dont know how, after isntalling 5faif ROM, terminal emulator shows me the #, id command shows me that I'm root.
I'm on stock ROM, this is the problem i think!
Anybody has SetCPU ?
The problem with this is that every application can obtain root without our knowledge.
It is a serious security flaw.
Not really. Android is pretty secure. Even if you get a brick from a Andirus (Virus + Android), it's a piece of cake to undo the damage.
Netbuster said:
This is true, but I dont know how, after isntalling 5faif ROM, terminal emulator shows me the #, id command shows me that I'm root.
Click to expand...
Click to collapse
Because that rom you've flashed contains custom boot.img by mainfram3 that gives to you root at startup and loads tattoo-hack.ko (partition r/w always mounted)
Coburn64 said:
Not really. Android is pretty secure. Even if you get a brick from a Andirus (Virus + Android), it's a piece of cake to undo the damage.
Click to expand...
Click to collapse
Actually i wasn't having viruses in mind. More like keyloggers and such. SU prompt wasn't invented for no reason...
I think the OP was asking about SuperUser.apk.
It's a modified su plus a service that asks for user intervention when a program calls /system/bin/su. It's nifty and it should be used by everyone.
Android apps are prevented from looking into other apps data. If su is readily available, a app can escalated it's privileges and steal your personal info, by reading data from other apps.
mainfram3 said:
I think the OP was asking about SuperUser.apk.
It's a modified su plus a service that asks for user intervention when a program calls /system/bin/su. It's nifty and it should be used by everyone.
Android apps are prevented from looking into other apps data. If su is readily available, a app can escalated it's privileges and steal your personal info, by reading data from other apps.
Click to expand...
Click to collapse
Exactly my point.
MoDaCo Custom ROM 1 includes Superuser apk for root access.
P
Anyone know how to fix Superuser Permissions manually?
I have Tattoo with rooted boot.img (mainfram3)
I pushed su into /system/bin/
Made chmod 4577 /system/bin/su
Pushed superuser.apk from Modaco Rom to /system/app/
Restart sure...
SuperUser Permissions can be executed (list is clear)
But any app doesn't send request to Superuser Permissions.
What i could forget?
Finally, I solved it partially.
Sure, i have rooted boot.img
I extracted from Modaco Custom ROM for Tattoo:
su
Superuser.apk
copied su to: /system/bin/su
copied Superuser.apk to: /system/app
run in terminal: chmod 4577 /system/bin/su
restarted and everything works fine now... Superuser Permissions shows all root-requests, Titanium Backup works, other root-things works too
But i notice, that su-binary from Modaco ROM is about 34-36 kb, but
su-binary from guide of getting root is about 80-85 kb.
1-2 months ago we faced with difference in size of su. We choosed bigger su in case, what it can run "flash_image", smaller su can't run.
But maybe it fixed already? I did not test it yet.
Thanks @5[Strogino]
I was trying to use Titanium today to back up my apps but it didn't work.
lukic said:
Thanks @5[Strogino]
I was trying to use Titanium today to back up my apps but it didn't work.
Click to expand...
Click to collapse
What exactly wrote TB?
Did you download busybox via TB?
I don't remember exactly.
It did ask me to download busybox and I did that, but still it didn't work.

[Q] Why I get permission denied on rooted phone?

Hello...
My question is simple. Why I get permission denied on rooted phone?
When I type: adb shell, I get $. Then I type su and I get this message: Permission Denied.
I followed this how-to (http://forum.xda-developers.com/showthread.php?t=792016) to root my phone and everything was fine. I get root privilegies and installed Superuser.apk, su, busybox...
But now, when I try to get root privilegies, I get the message above. Why?
Thanks and sorry for my english.
Because your phone isn't rooted. Either you didn't do it right or it's unrooted somehow, perhaps you got an OTA.
I think my phone is rooted, because there are many apps that use root permissions installed and working normally.
Sent from my Nexus One using XDA App
Then su isn't set up properly, or isn't asking for superuser permissions, or has been denied superuser permissions? Look in your Superuser app, maybe clear settings in it and let su ask again.
So, I cleared the settings in Superuser.apk and tried open Adfree apps that needs su permissions... and it opened and got permissions normally. I really don't understand what is the problem...
Sent from my Nexus One using XDA App
You do have usb debugging enabled right?

Chainfire's Superuser app error on rooted phone

this is my problem. i have a rooted phone and i get this error
https://bu.mp/tEb2VB
thats supersu, what method did you used for rooting? don't you have installed and earlier superuser app? have you installed busybox?
jpsb said:
thats supersu, what method did you used for rooting? don't you have installed and earlier superuser app? have you installed busybox?
Click to expand...
Click to collapse
i used cmw method. i think it was a busybox installer for root
Binary updater fails to update binary – This usually happens because for Superuser can’t write to the system partition where the binary is installed. This can happen for a couple reasons. First, and most common, is that your device has S-ON which prevents the system partition from being written to at runtime. Even if a remount succeeds, and the system thinks that the partition is mounted as rw, you can’t write to it. There are different solutions for different devices, but the easiest usually involves simply updating Superuser through ROM Manager.The app consists of two parts, Superuser.apk and the su binary.The su binary is what other apps call when they need superuser rights. The binary checks the database maintained by Superuser.apk to determine if you have already granted rights to the requesting app.Superuser comes pre-installed on any rooted ROM. In fact, without it, you don’t have a rooted device at all. You cannot uninstall it, it lives on the system partition with other apps that came pre-installed on your device!http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Sounds like I have the same issue, here's my post on chainfires kernel thread:
http://forum.xda-developers.com/showthread.php?t=1331784&page=186
I don't like using CWM out of fear of the brick bug which probably only happens when wipe is used but have stayed away from the first few warnings we had.

SU Binary In /system/xbin, But SuperSU Is Not Working

Besides the SU Binary In /system/xbin, what else do I need for SuperSU to function?
It keeps saying the SU binary is not installed
SpikeyPsyche said:
Besides the SU Binary In /system/xbin, what else do I need for SuperSU to function?
It keeps saying the SU binary is not installed
Click to expand...
Click to collapse
did you download the su app from the playstore
jerrycoffman45 said:
did you download the su app from the playstore
Click to expand...
Click to collapse
I was rooted on MI9 using the DLV method. I updated to NC2, and the SU binary installed by SuperSU persisted in the /system/xbin/ directory, but the SuperSU app says it is not installed. I wanted to know what, if anything, I can do with the SU binary in place to get the SuperSU app up and running again.
SpikeyPsyche said:
I was rooted on MI9 using the DLV method. I updated to NC2, and the SU binary installed by SuperSU persisted in the /system/xbin/ directory, but the SuperSU app says it is not installed. I wanted to know what, if anything, I can do with the SU binary in place to get the SuperSU app up and running again.
Click to expand...
Click to collapse
i am not sure there is anything you can do till we get a root exploit for nc2
yeah, i too have still have su in system/xbin on NC2, but root isn't working. it's weird, but as stated above, we probably need a new exploit or something
Are the permissions correct on the su binary? Might as well check that before we start despairing.
DrAzzy said:
Are the permissions correct on the su binary? Might as well check that before we start despairing.
Click to expand...
Click to collapse
Yeah, I'm not allowed to set the permissions in Root Explorer without root, but it does show a preview and the permissions do match all the other files in xbin
YrrchSebor said:
Yeah, I'm not allowed to set the permissions in Root Explorer without root, but it does show a preview and the permissions do match all the other files in xbin
Click to expand...
Click to collapse
Same here, permissions match all the other binaries in xbin.
SpikeyPsyche said:
Same here, permissions match all the other binaries in xbin.
Click to expand...
Click to collapse
I wonder what this means. I figure we dont need a new kind of su binary, but there must be something in the new software that blocks it from working?
I hope it isn't in the kernel. I had a Sony device last, and we needed an ever so slightly modified kernel in order to get full root on 4.3. But I doubt if we will ever be able to flash kernels.
YrrchSebor said:
I wonder what this means. I figure we dont need a new kind of su binary, but there must be something in the new software that blocks it from working?
I hope it isn't in the kernel. I had a Sony device last, and we needed an ever so slightly modified kernel in order to get full root on 4.3. But I doubt if we will ever be able to flash kernels.
Click to expand...
Click to collapse
I'm guessing there is some setting or permission that needs to be changed.

make system dir writeable

Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!
groggycl said:
Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!
Click to expand...
Click to collapse
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.
mhrajib said:
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.
Click to expand...
Click to collapse
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?
groggycl said:
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?
Click to expand...
Click to collapse
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess
mhrajib said:
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess
Click to expand...
Click to collapse
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?
groggycl said:
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?
Click to expand...
Click to collapse
What kind of error do you get?? Can you do other operations through link2sd??
mhrajib said:
What kind of error do you get?? Can you do other operations through link2sd??
Click to expand...
Click to collapse
the error is the following..
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Thats the error. Tried with titanium backup pro version and it gets stuck "PROCESING" the thing... It uninstall the app I want to move to system app, but then never finishes processing..
I also used a app called mount "/system ro/rw". I grant it superuser permissions and when I hit the "mount /system rw" a message appears that says; "Your device might not be rooted or is it not compatible!"
groggycl said:
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Click to expand...
Click to collapse
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.
leledumbo said:
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.
Click to expand...
Click to collapse
I've installed busybox and when I try lsof /system it says "toybox: Unknown command lsof", is there any solution?

Categories

Resources