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.
Related
So when I open up terminal emulator there is a '$' sign and I input the command "su". It says that super user granted permission. After that the '$' disappears and I can't do any other commands. If I enter one it will just skip to the next line with no effect. Can anyone help? Thanks.
NanoNoodle said:
So when I open up terminal emulator there is a '$' sign and I input the command "su". It says that super user granted permission. After that the '$' disappears and I can't do any other commands. If I enter one it will just skip to the next line with no effect. Can anyone help? Thanks.
Click to expand...
Click to collapse
TiBu wipe Terminal Emulators data and reboot...
BNaughty said:
TiBu wipe Terminal Emulators data and reboot...
Click to expand...
Click to collapse
I really want to try it out but for some odd reason none of my apps that require root works now. It must be something wrong with my Super user
Uninstall superuser apk and reinstall from market? Or try clearing the data of it
Sent from my Nexus 7 using Tapatalk 2
NanoNoodle said:
I really want to try it out but for some odd reason none of my apps that require root works now. It must be something wrong with my Super user
Click to expand...
Click to collapse
Try updating the su binary. Or try installing super su switching to super su's binary AND THEN uninstall super user. Or the opposite if your already using super su. You must NOT just uninstall the su app though. You must install the other, update the binary (instructions can be found in super su's thread in android apps and games (IIRC) the app itself, or Google it.
And THEN uninstall the other one.
Worth a shot.
Snowflake approved this message.
Babydoll25 said:
Try updating the su binary. Or try installing super su switching to super su's binary AND THEN uninstall super user. Or the opposite if your already using super su. You must NOT just uninstall the su app though. You must install the other, update the binary (instructions can be found in super su's thread in android apps and games (IIRC) the app itself, or Google it.
And THEN uninstall the other one.
Worth a shot.
Snowflake approved this message.
Click to expand...
Click to collapse
I tried to update the Superusers binary but it gets stuck on trying to get root access. I installed Super su and it tried to install the binary but it doesn't seem to be able to finish updating. Any other alternatives?
NanoNoodle said:
I tried to update the Superusers binary but it gets stuck on trying to get root access. I installed Super su and it tried to install the binary but it doesn't seem to be able to finish updating. Any other alternatives?
Click to expand...
Click to collapse
http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip
Download and flash in recovery. Boom, root.
Hey there,
this is my first thread ever created by me in a development forum.
I wanted to share my sollution for a adfree Android system, without unlocking the boatloader to get R/W access to /system.
I did try it on my device, everything went fine, but i will not take any kind of reponsibility for your devices. Also your warranty may be void!
What you need:
- rooted XTZ (i tried it on the 16GB Wifi only version)
- busybox installed
- Android SDK or adb.exe
- patched hosts file, I took mine from my HTC ONE with adaway installed (unzip first)
Click to expand...
Click to collapse
How to do it:
- get a patched hosts file from another device, or use mine (attached)
- put the file on the root of your sd card (so it will be /sdcard/hosts)
- connect your tablet to your PC, make sure usb debuggig is turned on
- launch cmd window, where your adb.exe is located
- entering following commands:
Code:
0. adb shell
1. su
2. stop ric
3. busybox pkill -f /sbin/ric
4. mount -ro remount,rw /system
5. busybox cp -af /sdcard/hosts /system/etc/hosts
- if everything went ok, you should now be able to see all the entries in your /system/etc/hosts file
- sadly you have to update the file if there some new adhosts, but it will remove a lot of annoying ads from all apps and the browser
- the changes are permanent, even at a reboot
Click to expand...
Click to collapse
Just let me know, if you have some kind of questions!
thanks @juanyunis for the [TEMPORAL-FIX] Remount RW /system reboot thread, from which i got some ideas.
Greetings from Germany
I have been using the AdAway app continuously since Google decided to eliminate all ad blocking apps from its Play Store and from my experience, AdAway does not require an unlocked boot loader to work, it only requires root access, and AdAway has no problem installing a hosts file in the /system/etc directory, so I am curious about why you have to go through all that.
The problem is, that if you using vroot like i did, and you doing nothing else, you don't have read write access to /system. So adaway, adfree and whatever can't edit the hosts file. Therefore is my little mod to get it done manually
Havoc2k said:
The problem is, that if you using vroot like i did, and you doing nothing else, you don't have read write access to /system. So adaway, adfree and whatever can't edit the hosts file. Therefore is my little mod to get it done manually
Click to expand...
Click to collapse
after vroot, install SuperSU and then all app ad-blocking apps are working good.
nope sorry, i did it, installed vroot, switched to normal superSU and installed busybox. But there is no RW access, so the ad blocking apps will work, but only to the next systemreboot / userswitch
tried all of them, and tried to manually edit the host file, but without access it will not happen
greetings
Havoc2k said:
But there is no RW access
Click to expand...
Click to collapse
strange thing that with root there is no RW access.
Havoc2k said:
nope sorry, i did it, installed vroot, switched to normal superSU and installed busybox. But there is no RW access, so the ad blocking apps will work, but only to the next systemreboot / userswitch
tried all of them, and tried to manually edit the host file, but without access it will not happen
greetings
Click to expand...
Click to collapse
I have tested and have for several months ran AdAway on my XTZ, on which Vroot was used to gain root access and SuperSU is installed, and AdAway has no problem writing a hosts file to the /system/etc directory even though the permissions for the /system and /system/etc directories are set to read-only. So, because I have no problem with AdAway and you apparently have a problem with AdAway, I believe it is likely there is a flaw in your root access setup. But hey, I could be wrong.
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.
Has anyone managed to install adaway on any official rom?
The program fails when trying to apply the hosts file.
Yes i have rooted the phone and yes i have granted permisions with supersu to adaway.
revery0 said:
Has anyone managed to install adaway on any official rom?
The program fails when trying to apply the hosts file.
Yes i have rooted the phone and yes i have granted permisions with supersu to adaway.
Click to expand...
Click to collapse
I had it many times. AdAway is working very wele. Maybe you have not full rooted phone. Use MyRoM it is full rotted and AdAway is preinstalled and many others additions.
Hey...
First step is normal root. If you are ready you have to delete the immutable.list on system. Then you can use adaway.
Booth ways need busybox! Install it before you try to delete immutable.
Make it with my tool - easy update and adjust (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286) or make it manuelly with your PC and ADB.
adb shell
su
mount -o rw,remount /system
cd system
chattr -R -i *
rm –f /system/set_immutable.list
lsattr (to see if it's still there)
On my device with stock Rom it works well!
Thank you, it works like a charm!!!
revery0 said:
Thank you, it works like a charm!!!
Click to expand...
Click to collapse
No problem...
Wich way you have choosed?
Your script, cause command prompt returned an error when trying to change attributes, the reason was that adb hadnt have su permissions and for some reason supersu didnt prompt me to grant them. But with your script supersu prompt me to give adb su permissions and so i did, after that it worked.
Strange dont you think?
revery0 said:
Your util, cause command prompt returned an error when trying to change attributes, the reason was that wasanted su permiadbwasntions and suidnt proe to give it permissions, but when I tried your script then I got the prompt from supersu and itsusupersudidntsupersu..
Sounds strange dont you think?
Click to expand...
Click to collapse
I dont understand you complete. But my batch is working for you, thats fine
Auto correction on swype keyboard sucks.... I edited the previous post
revery0 said:
Auto correction on swype keyboard sucks.... I edited the previous post
Click to expand...
Click to collapse
yeah it corrects way u dont want it .. just turn off auto and leave options to pick..
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?