Related
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.
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.
Anyone know of a way to hide my root on the nexus 6?
Thanks, Robert
Hide it from what?
From apps that don't work with rooted phones. The one app in particular is puzzles and dragons.
Does Xposed framwork work on Lollipop yet? You could use Root Clock then.
http://repo.xposed.info/module/com.devadvance.rootcloak
Mauk80 said:
Does Xposed framwork work on Lollipop yet? You could use Root Clock then.
http://repo.xposed.info/module/com.devadvance.rootcloak
Click to expand...
Click to collapse
No xposed on Lollipop yet.
Any workaround till today ? this is really frustrating
Wonder why a game should care if you are rooted?
Wonder why *anything* would care if you have root access....?
It isn't like any possible detection method can actually verify that the device *does not* have root.
For example;
cp /system/bin/sh /system/bin/bitemerootchecker
chown root.root /system/bin/bitemerootchecker
chmod 6755 /system/bin/bitemerootchecker
Now you have an "su" command that can't be detected.
I was checking out the Root Thread for S6 and realized that my Edge's ROM version matched one on there except for the G925 vs G920. Would that root work on my Edge's similar ROM?
Never EVER try to root your phone unless it meets ALL the requirements! Mine is a SAMSUNG-SM-G925V. Unless that root is developed for a SAMSUNG-SM-G925V, you're taking a chance on bricking your phone. There are things you can do to remove bloatware and improve battery performance, which are a couple of the main reasons for installing a different ROM. I've done it myself and find battery performance has drastically improved. Do some research and you'll find what settings you can change and which apps you can either uninstall or disable. I'm happy with the snappiness and performance of this phone and find with some simple adjustments, it makes this phone even better. We will just have to be patient to see if the bootloader can be unlocked. Who knows when or if that will happen any time soon! Hope that addresses your question.
Sent from my SM-G925V using XDA Free mobile app
MaverickCoast said:
Never EVER try to root your phone unless it meets ALL the requirements! Mine is a SAMSUNG-SM-G925V. Unless that root is developed for a SAMSUNG-SM-G925V, you're taking a chance on bricking your phone. There are things you can do to remove bloatware and improve battery performance, which are a couple of the main reasons for installing a different ROM. I've done it myself and find battery performance has drastically improved. Do some research and you'll find what settings you can change and which apps you can either uninstall or disable. I'm happy with the snappiness and performance of this phone and find with some simple adjustments, it makes this phone even better. We will just have to be patient to see if the bootloader can be unlocked. Who knows when or if that will happen any time soon! Hope that addresses your question.
Sent from my SM-G925V using XDA Free mobile app
Click to expand...
Click to collapse
I didn't realize that was the case and went ahead installing the apk. Bad news, it didn't work. Good news, the app tells you it doesn't work for G925V yet.
mngdew said:
I didn't realize that was the case and went ahead installing the apk. Bad news, it didn't work. Good news, the app tells you it doesn't work for G925V yet.
Click to expand...
Click to collapse
iambugsy said:
I was checking out the Root Thread for S6 and realized that my Edge's ROM version matched one on there except for the G925 vs G920. Would that root work on my Edge's similar ROM?
Click to expand...
Click to collapse
There's been an update. Version 3.2 of the app works fine on current Verizon S6 Edge software. I currently am sitting on one with root.
Berzerker7 said:
There's been an update. Version 3.2 of the app works fine on current Verizon S6 Edge software. I currently am sitting on one with root.
Click to expand...
Click to collapse
That's awesome news, thanks! I'll try it out when I get home today.
Yup - just used the updated APK and it worked like a charm. Went ahead and swapped out King for SuperSU.. that too works great.
How did you swapped king for super su?
furialfil said:
How did you swapped king for super su?
Click to expand...
Click to collapse
Check out the Q&A area of the PINGPONGROOT thread.. its all listed in there. I copied/pasted from it, but it might not transfer the code exactly correct..
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
Q: I'd like switching to SuperSU, what shall I do?
A: Kinguser does not have a "swtich" function. Follow these steps to do so manually: (if you are not familiar with adb, see this version: http://forum.xda-developers.com/show...&postcount=269)
1. Download supersu.7z and extract it. You will get the files needed to install Supersu.
2. Using adb to push su and busybox (if not installed) to /data/local/tmp.
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
3. Start a su session and run the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/bin/busybox && chmod 0755 /system/bin/busybox
daemonsu -d &
Then keep the session running.
4. Open Kinguser, go to Settings -> Root authorization setting -> Remove Root permission. Click to remove root permission. Your su session should be still running.
5. Uninstall Kinguser app.
6. Go back to the su session and run following commands to replace su and cleanup:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/bin/ddexe
busybox chattr -ia /system/bin/ddexe_real
cat /system/bin/ddexe_real >/system/bin/ddexe
busybox chattr -ia /system/xbin/ku.sud
rm /system/xbin/ku.sud
rm /system/xbin/pidof
rm /system/xbin/supolicy
7. Install Supersu apk
8. Open Supersu apk to update files.
9. Reboot.
wait a minute so we now have root ?
XTRoRDiNAiRE said:
wait a minute so we now have root ?
Click to expand...
Click to collapse
yes
If your version matches what's in the pingpong root thread then yes. I rooted my S6E a few min ago.
Zmnypit said:
If your version matches what's in the pingpong root thread then yes. I rooted my S6E a few min ago.
Click to expand...
Click to collapse
rooted. has anyone installed TWRP? what's the best way to go about doing that? TWRP manager doesn't list verizon specific s6.
I want to flash the no-deep-sleep fix
I believe you can't install a custom recovery yet as it will trip knox. Might want to go through the posts on the root thread.
Thanks. Yeah sorry it's a bit hard to follow the latest news since there are a thousand threads on all the s6/edge forums talking about the same issue. If the recovery is untouched, do we need to worry about the deep sleep problem? I've read it was caused by recovery.
[Terminal] App Systemizer
Terminal App Systemizer systemizes Apps systemlessly! This is inspired by App Systemizer by stangri. I then decided to make a script/UI in Terminal emulator for it to make 'app systemizing' easier.
How to use:
Install from recovery
Type su and
Code:
systemize
in Terminal emulator or adb shell (use -nc, -a, -d, refer below)
Systemize Chosen App/APK!
And reboot to apply changes
OPTIONS:
** If you don't want those colors, use -nc.
Code:
systemize -nc
** To directly systemize (without ui) a given package name/s, use -a
Code:
systemize -a com.oasisfeng.greenify org.adaway
** To directly systemize (without ui) a given apk/s, use -d
Code:
systemize -d /sdcard/example.apk /sdcard/example2.apk
** Uploading logs
Go to the menu and type `logs`, this will upload the log files of this module and will generate a link. Send that
Alternatively, Send `/cache/terminal_debloater-verbose.log` here. I'll examine it for problems and will try to fix it.
Dowloads are here!
Github
Telegram Channel
Notification Channel
DONATE? If you want to (ﾉ･ω･)ﾉﾞ
HERE'S A LITTLE VIDEO ON HOW TO USE IT:
F.A.Q
Q. Why do I need to systemize apps?
A. Some apps provide extra functionality as a system app (like Greenify, Launchers, etc). And if you just want an app to be a system app for no reason .
Q. Is A/B Devices (Pixel, Essential, MI A1 etc.) supported?
A. YES
Q. What's the advantage of using this over the other systemizers?
A. This one is very light weight (since it's just a script). And it's also very versatile and supports almost all devices.
Q. Something's not right??
A. Report in this thread...
When a systemizied app is updated, how do you re-systemize it? Do you just rerun the terminal UI and choose the updated app and reboot? After reboot, does the updated app replace the old one?
JERW28 said:
When a systemizied app is updated, how do you re-systemize it? Do you just rerun the terminal UI and choose the updated app and reboot? After reboot, does the updated app replace the old one?
Click to expand...
Click to collapse
No, it's like when you update a system app from play store, it stays as a system app.
No need to do anything if it's updated :good:
veez21 said:
No, it's like when you update a system app from play store, it stays as a system app.
No need to do anything if it's updated :good:
Click to expand...
Click to collapse
What if we wanted to use this as a tool to save space on internal memory? Once the systemized app is updated, it would take space on internal storage right? Anyway to put it back into system?
iG0tB0lts said:
What if we wanted to use this as a tool to save space on internal memory? Once the systemized app is updated, it would take space on internal storage right? Anyway to put it back into system?
Click to expand...
Click to collapse
Apks are not stored in internal mem. It's stored in /data. This only affects apks so i think saving space is out of this module's fuctionality.
After choosing option 1 for installed apps, this is all I get:
Code:
Search packages: packages search <query>
===========================
Installed Apps
===========================
Loading Apps...
0 - Exit
[CHOICE]:
yochananmarqos said:
After choosing option 1 for installed apps, this is all I get:
Click to expand...
Click to collapse
Could you do this command in terminal emulator:
Code:
pm list packages -3
veez21 said:
Could you do this command in terminal emulator:
Click to expand...
Click to collapse
Code:
$ pm list packages -3
android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died
at android.os.BinderProxy.transactNative(Native Method)
at android.os.BinderProxy.transact(Binder.java:615)
at android.os.BinderProxy.shellCommand(Binder.java:662)
at com.android.commands.pm.Pm.runShellCommand(Pm.java:295)
at com.android.commands.pm.Pm.runList(Pm.java:666)
at com.android.commands.pm.Pm.run(Pm.java:130)
at com.android.commands.pm.Pm.main(Pm.java:99)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:262)
Sent from my Nexus 5X using XDA Labs
Damn, what happened? What rom?
Anyways, I'll try to find a workaround for this without using pm
veez21 said:
Damn, what happened? What rom?
Anyways, I'll try to find a workaround for this without using pm
Click to expand...
Click to collapse
No idea why that's happening. Stock 7.1.2, just did a factory reset a few days ago.
Sent from my Nexus 5X using XDA Labs
yochananmarqos said:
No idea why that's happening. Stock 7.1.2, just did a factory reset a few days ago.
Click to expand...
Click to collapse
I couldn't find a workaround for this, sadly. You have installed 3rd apps after factory reset?
veez21 said:
I couldn't find a workaround for this, sadly. You have installed 3rd apps after factory reset?
Click to expand...
Click to collapse
Yes, I have quite a few apps installed. It does the same thing without the -3 option, too.I wonder what could be causing it?
Sent from my Nexus 5X using XDA Labs
yochananmarqos said:
Yes, I have quite a few apps installed. It does the same thing without the -3 option, too.I wonder what could be causing it?
Click to expand...
Click to collapse
Okay, could you send me the output on 'pm' command only? I want to look on what's with it.
veez21 said:
Okay, could you send me the output on 'pm' command only? I want to look on what's with it.
Click to expand...
Click to collapse
Just pm by itself just gives the --help output.
Sent from my Nexus 5X using XDA Labs
yochananmarqos said:
Just pm by itself just gives the --help output.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Some users got this problem with my snapshot updater module & I had to remove "pm" from it... I think is a common problem with Nougat, because in Lollipop & Marshmallow all is fine... Do you may enable all usb debug options under developer settings in Android?
Deic said:
Some users got this problem with my snapshot updater module & I had to remove "pm" from it... I think is a common problem with Nougat, because in Lollipop & Marshmallow all is fine... Do you may enable all usb debug options under developer settings in Android?
Click to expand...
Click to collapse
I have USB Debugging enabled, yes. I'm not sure what you mean by "all usb debug options".
Sent from my Nexus 5X using XDA Labs
yochananmarqos said:
I have USB Debugging enabled, yes. I'm not sure what you mean by "all usb debug options".
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
All options related to install/verify from Debugging section (maybe different in your ROM).
I'm not trying to get on you, or burst your bubble, so please don't get mad. I want to know what the difference between this, and titaniumbackup pro? It has a function to turn user apps into system apps. I'd rather use this, cause titanium can get wonky sometimes.