I have reclaimed ownership of my phones 'bixby' button with an app called bxActions and it works pretty nice, however the app claims it can work even better if I grant it permissions by running something on my PC through USB. It sounds sketchy.. Does anyone know what happens when you do it?
I'm mainly concerned about permanently locking it into a bxActions button, and perhaps even voiding warranty (does this count as rooting?).
Is it safe/worth it?
It is safe for you to do that, it doesn't count as rooting since it's only executing adb commands. I don't know about warranty though if you ever have to send your phone away for warranty I'd delete the app and the folder just in case
Ok, so nothing is permanent or invasive enough for Samsung to have a fit over it?
In that case ill just do it. Because frik bixby.
Just do it. Its ok
Sokonomi said:
I have reclaimed ownership of my phones 'bixby' button with an app called bxActions and it works pretty nice, however the app claims it can work even better if I grant it permissions by running something on my PC through USB. It sounds sketchy.. Does anyone know what happens when you do it?
I'm mainly concerned about permanently locking it into a bxActions button, and perhaps even voiding warranty (does this count as rooting?).
Is it safe/worth it?
Click to expand...
Click to collapse
I did it long time ago. Using all samsung features happily... Infact have provided many other apps spl permissions... doesn't break anything...
omega_warrior said:
I did it long time ago. Using all samsung features happily... Infact have provided many other apps spl permissions... doesn't break anything...
Click to expand...
Click to collapse
Can you tell me some other mods for the s8 without root? Pls
Related
Anyone else tried this su app? I've been using it for awhile now with no problems and no toasts! Minimalistic, but negatives are no logfile or grant list and no UI, but it works well and hasn't gotten corrupted (which is not the same thing I can say for superSU). I'm sure the shortfalls will be resolved with upgrades. All in all I like it. Especially the toastless granting. And you won't find a nicer or more responsive dev than Robert N. Weird su prompt thought.
So this grants superuser rights to any app that asks for it, without user confirmation or even user notification? Sounds like a huge security hole if you ask me.
_that said:
So this grants superuser rights to any app that asks for it, without user confirmation or even user notification? Sounds like a huge security hole if you ask me.
Click to expand...
Click to collapse
elfaure said:
Weird su prompt thought.
Click to expand...
Click to collapse
That last sentence makes me think it does actually prompt the user for granting the inital access, but it will not notify by default.
Please note, elfaure, that this can be done with SuperSU as well -- at least the disabling of notifications. I cannot vouch for the absence of 'corruption' because I have never experienced it with SuperSU .
MartyHulskemper said:
That last sentence makes me think it does actually prompt the user for granting the inital access, but it will not notify by default.
Please note, elfaure, that this can be done with SuperSU as well -- at least the disabling of notifications. I cannot vouch for the absence of 'corruption' because I have never experienced it with SuperSU .
Click to expand...
Click to collapse
No toasts and no notifications EVER. Its all handled transparently in the background. Huge security hole? - You bet it is. The blackest of holes. So is leaving USB debugging enabled but I do that too in case I need ADB in a brick bind. If its not enabled when you need it and you can't get there to enable it then your hosed. That was @florck 's saving grace. Without ADB even @_that couldn't have fixed it.
Its only designed for *developers* that know what they are doing and don't load malicious apps from "unknown sources". I don't quite fall into that catagory but I respect its design intent and use it wisely, not to mention never lending my tablet to anyone nor leaving it laying around for someone to play with. I know I can turn off the toasts with superSU, its the corruption that I can't handle. Its happened to me twice, only when its installed "as a system app". No real failure per say. Root wasn't failing for any reason, but in the terminal my su "#" prompt just disappeared twice and left me with only a box for a prompt. Just bugged the living h%&l out of me, that's all.
When an app asks for permissions, Allow and Deny options show up (regardless if for storage, or camera, etc.) but the allow button does not work. Deny works fine. So far i have unlocked the bootloader via Huawei website method (i guess you call that official) and flashed twrp. I have not rooted the phone yet (getting to that, but one problem at a time) and this is the first one.
I also saw someone else ask, but with now answer. Is there a way to get rid of the splash scren about the phone being unlocked and not trustable, press power button again to boot?
Do you have an special theme activated? Use the standard theme and try again
My 1st question to you is... when the window prompts, do you flag the option "don't ask to me again" or not? Because if yes, the only option avalaible becomes the "deny" one. This mechanism confused me too some time ago, when i wasn't understanding why it was blacked out; Android takes your flag as an "what a bore, just shut up and go **** ya' self leavin' me alone" answer, so it automatically deactivate the possibility to let it pass even one more time. If you didn't checked the flag, i have another question for you. Did you maybe recently made an update OTA, or with an update package found online? If the 2nd answer is what u've done, do a check for being sure that you have updated the phone with the correct package model. (BLN-21, BLN-22, ecc.) If neither this is your case, begin to tell us something more 'bout your phone configuration and start to think to backup your data and do a factory reset for eliminate this weird issue.
For the question of yours about the Nag screen (the splash one, for being clear) at the moment there is nothing that we can do to avoid it to pop out; just skip it pressing immediately the power button, is the best advice that i can do so far
I'll attempt to answer all these at once since I just got home from work. I wouldn't believe rooting the phone would cause this issue, but the problem happened before i unlocked the bootloader so I think that rules that out. I do not use a special theme, but I do use squarehome launcher for my phone, not the standard android launcher. Problem there is, the problem occurs with either launcher being active. And theme wise, I have a 3-d live aquarium for a background (which if turned off and just a static wallpaper, the same behavior occurs). As far as the phone update goes, it was an OTA update from 6 to 7, so still using stock, nothing sideloaded or flashed (yet). My data is all backed up via My backup pro, and doing a full backup with TWRP onto OTG is not a problem. I prefer not throwing in the towel, since setting up squarehome perfectly is a pain in the ass, but if it has to happen, it is better than manually setting permissions for every app that needs them. Not sure what a screenshot would do, think of any app asking for permission to use phone storage, both the allow button and the deny button visible (in white, nothing grey) and allow doesn't respond where deny responds fine. and then i have to go in manually and grant the permission after the fact. I suppose I could just root my phone and give that a whirl, seems some bloatware needs to be removed anyway, and i have the SU sitting on my hard drive already. Thanx for the responses, and let me know what you may have come up with before I just factory reset it which as mentioned, I am dreading doing.
Rommco05 said:
Hi, so you have unlocked bootloader but not rooted? This is maybe problem, you need to have rooted phone if you have unlocked bootloader for fully using phone. Can you post some screeshots?
Click to expand...
Click to collapse
Well, I didn't think that would be the answer, but you, sir were right. I rooted my phone and it seemed to have fixed the problem. I don't believe I made any other change whatsoever. Thank you very much. Glad I tried it anyway as you suggested even though I didn't think it would be the answer. I am not above saying thank you, and I was wrong. Kudos. Maybe this will help someone else. Good thing is, I planned on rooting it anyway, and you just kicked me in the pants to do it.
Rooted but allow button is still not activated
Hello guys,
I wanted to activate app twin so I rooted my phone BLN-L21 android 7.0
Allow button still deactivated.
Also the boot screen that asks to press power button still exist.
I noticed that if I activate whatsapp twin it won't work simultaneously .
I.e : when you open whatsapp you get all missed calles & messeges.
Also I was able to download themes through themes app ,but now it just views the local themes.
Note: superSu is installed.
Any help will be appreciated.
Thank you
Well, I think this is not related to OP (or at least partially), but when unlocking bootloader after setting up SD card as the default storage can break some things, like default themes.
Try to restore your firmware, and then unlock the bootloader.
If successful, you can now set up SD card as default storage.
jackmeat said:
When an app asks for permissions, Allow and Deny options show up (regardless if for storage, or camera, etc.) but the allow button does not work. Deny works fine. So far i have unlocked the bootloader via Huawei website method (i guess you call that official) and flashed twrp. I have not rooted the phone yet (getting to that, but one problem at a time) and this is the first one.
I also saw someone else ask, but with now answer. Is there a way to get rid of the splash scren about the phone being unlocked and not trustable, press power button again to boot?
Click to expand...
Click to collapse
Its happened to me before i just wiped the phone. I even sometimes cant click install when installing an apk unless i lock and unlock the screen.
As the title says... I need to write secure settings in order to disable Bixby, because Bixby is a security problem for me (it can power off my phone from lockscreen if it gets stolen, even though I have an anti-theft app to block the power menu during lockscreen). But I do not want to risk triggering Knox or have any other warranty issues on the way.
I do NOT want to root my phone!!! I tried to root my last one and i totally messed it up...
Does it work by using ADB? As I mentioned before, I do not want to root my phone, trigger knox, risk any warranty or losing my ability to upgrade android.
I have a Galaxy S8+
DJAerox said:
As the title says... I need to write secure settings in order to disable Bixby, because Bixby is a security problem for me (it can power off my phone from lockscreen if it gets stolen, even though I have an anti-theft app to block the power menu during lockscreen). But I do not want to risk triggering Knox or have any other warranty issues on the way.
I do NOT want to root my phone!!! I tried to root my last one and i totally messed it up...
Does it work by using ADB? As I mentioned before, I do not want to root my phone, trigger knox, risk any warranty or losing my ability to upgrade android.
I have a Galaxy S8+
Click to expand...
Click to collapse
I have a Galaxy S8+ and have never once tripped knox by performing any adb actions (I do write secure settings for multiple apps). It won't mess with warranty either cause a factor reset will clear anything you did with adb. So you are covered.
My last phone you couldn't turn off, reboot, or change network settings while the phone is locked. This is a very useful feature as if your phone "walks away" tracking cannot be disabled so as long as your battery is not dead you have full tracking abilities.
I did notice this feature seems to work with GPS. If you try to toggle, it will prompt for a password but that alone isn't enough to track it. I need to lock mobile data as well. I could probly just remove it from my notification tray but that is an inconvenience as I do use that toggle.
Any Ideas?
Username5.2 said:
My last phone you couldn't turn off, reboot, or change network settings while the phone is locked. This is a very useful feature as if your phone "walks away" tracking cannot be disabled so as long as your battery is not dead you have full tracking abilities.
I did notice this feature seems to work with GPS. If you try to toggle, it will prompt for a password but that alone isn't enough to track it. I need to lock mobile data as well. I could probly just remove it from my notification tray but that is an inconvenience as I do use that toggle.
Any Ideas?
Click to expand...
Click to collapse
Not all devices have added those as all it takes to beat them is removing the sim card and all android devices will reboot if the power button is held for an extended time.
Well I thought about the reboot and it will boot back up so I didn't see that as a problem. Didn't think about the sim card though. Well lets just hope if someone gets a hold of my phone they won't think about it either. Anything I can do to make it harder is still worth it.
Oh well. If someone has a way to make this happen please share. I don't even know if its something I can make happen with an app or by editing anything in the android system. I will keep looking in the mean time.
Username5.2 said:
Well I thought about the reboot and it will boot back up so I didn't see that as a problem. Didn't think about the sim card though. Well lets just hope if someone gets a hold of my phone they won't think about it either. Anything I can do to make it harder is still worth it.
Oh well. If someone has a way to make this happen please share. I don't even know if its something I can make happen with an app or by editing anything in the android system. I will keep looking in the mean time.
Click to expand...
Click to collapse
I can tell you that there are 3 steps when a device is stolen and the first one is remove the battery and the second is remove the sim card so no one can call it. the 3rd step is resetting it.
You will need a custom rom to get those options.
If you care about security too much, I would say never unlock your bootloader.
Its so easy to keep pressing the power button and reboot to bootloader and flash stuff to access your memory (With unlocked bootloader of course)
But with locked BL, they have to erase the storage in order to unlock it and do stuff. So, if security is a big concern to you, its good to always keep it locked.
I just ordered a Pixel 3a and I was gone for a while from the world of Google phones (since Nexus 4).
I know Magisk hides any trace of root and unlocked bootloader, but is there any disadvantages unique to Pixel devices when rooting, like disabled features or is hiding good enough that there won't be any difference? Just to be sure
Artim_96 said:
I just ordered a Pixel 3a and I was gone for a while from the world of Google phones (since Nexus 4).
I know Magisk hides any trace of root and unlocked bootloader, but is there any disadvantages when rooting, like disabled features or is hiding good enough that there won't be any difference? Just to be sure
Click to expand...
Click to collapse
Nothing as far as i know.
Unstroofy said:
Nothing as far as i know.
Click to expand...
Click to collapse
That sounds great. Wasn't sure if they might have done something through the Titan M or else
Rooting means unlocking your bootloader. This makes your phone at greater risk of being compromised - especially if someone has physical access to your phone (ie you lost it and someone finds it). Therefore you don't want to leave your bootloader unlocked if you have any sort of sensitive, illegal, or secret information on your phone. That's the #1 issue you have to live with. Of course for 99% of the population, there isn't anything really sensitive on their phones.
Google Pay can be hard to get working when rooted. There are ways to make it work, but it's always a cat and mouse game with Google and it may not always work in the future if Google changes something until the developers can catch up. If you can't live without Google Pay, rooting may not be the best choice for you.
There are other apps that can be temperamental when rooted - usually finance apps and some games (because they don't want players cheating). However, the Magisk hide functionality usually works with most of these apps now.
For me, the added functionality that being rooted brings (via modules and apps) is far better than the potential issues.
sic0048 said:
Rooting means unlocking your bootloader. This makes your phone at greater risk of being compromised - especially if someone has physical access to your phone (ie you lost it and someone finds it). Therefore you don't want to leave your bootloader unlocked if you have any sort of sensitive, illegal, or secret information on your phone. That's the #1 issue you have to live with. Of course for 99% of the population, there isn't anything really sensitive on their phones.
Google Pay can be hard to get working when rooted. There are ways to make it work, but it's always a cat and mouse game with Google and it may not always work in the future if Google changes something until the developers can catch up. If you can't live without Google Pay, rooting may not be the best choice for you.
There are other apps that can be temperamental when rooted - usually finance apps and some games (because they don't want players cheating). However, the Magisk hide functionality usually works with most of these apps now.
For me, the added functionality that being rooted brings (via modules and apps) is far better than the potential issues.
Click to expand...
Click to collapse
Tl;dr: nothing new. And never had a problem with any apps. Magisk Hide is working well enough, deleting apps data always works as last resort. And on custom ROMs just use MagiskHide Props Config. And if you are concerned about your data, just use the lockscreen passport as bootup protection. Then it's simply impossible to get to the data through that "insecurity", no matter what you do. And since fingerprint readers a more complex password isn't a problem.
Artim_96 said:
Tl;dr: nothing new. And never had a problem with any apps. Magisk Hide is working well enough, deleting apps data always works as last resort. And on custom ROMs just use MagiskHide Props Config. And if you are concerned about your data, just use the lockscreen passport as bootup protection. Then it's simply impossible to get to the data through that "insecurity", no matter what you do. And since fingerprint readers a more complex password isn't a problem.
Click to expand...
Click to collapse
I'm not sure exactly what you mean by lock screen passport. Can you share some more details?
The insecurity comes from the fact that a person that has physical access to your phone can simply turn the phone off and then start it and hold the power and volume up buttons. This will boot the device into the bootloader. Because the bootloader is unlocked, it allows that person the ability to flash anything and gives that person access to anything they want. That super secure lockscreen password or fingerprint won't help keep them out and does nothing but give users a false sense of security.
When the FBI paid a 1 million dollar bounty to someone to access an iPhone, they were paying someone to get around the bootloader. If you unlock your bootloader, you give this access right from the beginning - for free, and without any effort required.
I'm not trying to be argumentative either. You asked what the drawbacks to rooting were and I was simply trying to give a thorough answer. It's up to the individual user to decide if the the positives of unlocking the bootloader and rooting outweigh the negatives. If you look at my signature, you can see what side of the fence I fall on.
sic0048 said:
I'm not sure exactly what you mean by lock screen passport. Can you share some more details?
The insecurity comes from the fact that a person that has physical access to your phone can simply turn the phone off and then start it and hold the power and volume up buttons. This will boot the device into the bootloader. Because the bootloader is unlocked, it allows that person the ability to flash anything they want. That super secure lockscreen password or fingerprint won't help keep them out.
Again, I'm not familiar with this lockscreen passport you mention, so perhaps there is a way to secure the phone that I am not aware of.
I'm not trying to be argumentative either. You asked what the drawbacks to rooting were and I am simply trying to give an thorough answer. It's up to the individual user to decide if the the positives or rooting and unlocking the bootloader outweigh the negatives. If you look at my signature, you can see what side of the fence I fall on.
Click to expand...
Click to collapse
Was a typo,I meant lockscreen password. Android should ask you, if you set up a lock method other than Swipe to unlock, if you want to be asked for it on bootup.
So no matter what you are able to flash through an unlocked bootloader, /data and with it anything that could be relevant stays encrypted until you enter the lockscreen pin/pattern/password, no matter if you do this on the screen that will interrupt bootup after a few seconds or in TWRP. So it doesn't matter what you could come up flashing, as long as you don't find a way to extract the encryption key from the secure storage either in Titan M or any ARM processor, there is no way to get your hands on user data. The only thing you can do is simply wipe /data. Then you can start up new, but the users data will be gone.
And no, I never asked for disadvantages of root itself since there are little to none, I just asked for Pixel unique stuff since Google always adds stuff that other OEMs won't use for years to come.
Artim_96 said:
And no, I never asked for disadvantages of root itself since there are little to none, I just asked for Pixel unique stuff since Google always adds stuff that other OEMs won't use for years to come.
Click to expand...
Click to collapse
I misunderstood your initial post then, but the title of the thread says, "Disadvantages of rooting?"
sic0048 said:
I misunderstood your initial post then, but the title of the thread says, "Disadvantages of rooting?"
Click to expand...
Click to collapse
Fixed that. Hope the text is more clear now.
But could you reproduce what I explained? Because I would be very surprised if that was unique to Motorola and not AOSP