Related
Figured I would start here in my device thread before trying the SuperSU thread.
Anybody have issues with SuperSU since the last few updates ago?
SuperSU does not even open. Root-dependent apps do not open. Titanium sits there at the initial screen "asking for root rights" until I kill the app. AdAway does not open... just goes right to a black screen until I kill the app. AdAway seems to work though, as my web surfing does not have ads.
I've also tried manually going in and applying the latest update via (philz) recovery.
Would I be safe to roll back to an older version of SuperSU?
Mods... if you're going to gun the thread, please at least point me in the right direction as I did search, but did not find anything related to recent issues on the Note 2 for SuperSU.
TIA for help and suggestions.
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
ceabbott2 said:
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
Click to expand...
Click to collapse
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
lennykravitz2004 said:
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
Click to expand...
Click to collapse
For me, I just reflashed the ROM I was running at the time and that resolved it. Of course seeing that the update was " fixed" I attempted it and lost root again. I then did the same as before, wiped and relashed. I didn't do clean installs either time. Just wiped caches and reflashed. That sucks if you have to re-root. I mean, it's easy and all but it shouldn't have to be done.
D
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
DJ_Barcode said:
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
Click to expand...
Click to collapse
Thanks for the try. Did not work though.
Looks like I just need to re-flash the ROM.
My problem was odd. Before I discovered the aforementioned trick, I'd re-root with Chainfire or Kingo. I'd reboot, and my device would be rooted. But those two methods have an additional payload - they flash the stock recovery. So I'd ODIN the Philz Touch recovery back to the device, reboot, and root would be gone. Never figured out what was going on.
Yup. Issues with new version. Only last 2 or three updates.
They seemed to be perfectly fine with cm12 though.
Sent from my SPH-L900 using XDA Free mobile app
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
lennykravitz2004 said:
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
Click to expand...
Click to collapse
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
As always, thanks for your response. Your recommendation is what I've been doing, just wanted to follow-up on this and see if there was anything else I needed to consider or change as well.
My main concern was to make sure I was not going to run into any "big" issues (especially security) by staying on current version. Thanks for explaining where the issue really lies on this too. I'm obviously not a dev, however I do want to understand what is exactly going on and responses like yours always provide that type of info. :good: Thank you.
And, FWIW, using "fool proof" to describe a process only makes me more curious (and no, not in that way) about your suggestion. :laugh:
Now I HAVE to find out more about that option... (only after some of the best BBQ in all of the land - Sugarfire BBQ in STL )
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
How do you disable auto update of binary on SuperSU? I keep seeing it in the notification bar, very annoying.
Device Info: Sprint Galaxy Note 2 Running rooted stock Android 4.4.2. (chainfire auto root using odin)
Wifi only unit. I have no sprint contract purchased it used (I'm new to customizing android- I have flashed an old palm pda, but only via guidance)
Situation: Rooted the unit and have customized it as mine
1. No custom backup and would like to do that
2. Do not like all the bloatware apps
3. Now a system update has been downloaded asking to install (I've not okayed it)
So please help me with each of these
1. Please point me in the direction of best way to take a backup of existing rom ( I do have philz downloaded, but I'm not sure about how to ?
2. Would that deal with the persistent update request? Would it be good to update?
3. and then the bloatware removal, should I use an app that removes system apps? ( I have titanium, but I'm not good at knowing which apps to touch and not to touch) Thanks in advance and no I'm not in a hurry as yet.
Hi,
I will have your thread moved to your device section so the experts who own your device can help you.
Good luck!
Point to links please
If someone doesn't want to tackle this whole question I'd just appreciate links on how to step by step. I'd appreciate any help at all, I'm just a bit fearful of bricking the device, but if the instructions are clear I can definitely do this.
The first is issue is backup that is my priority at the moment. The second is whether to install the update or not and how to get rid of the nag. thanks
Not sure about backing up the ROM itself... but what I do is just back up the apps with Titanium and then re-load the apps (or just data) when I have to re-install my ROM like I did a couple of weeks ago. Prior to the Note II, I had an HTC Hero (stop laughing) and would do nandroids for that device. Don't know that you need that for Samsung devices, but somebody may be better to explain than I am.
ETA: here's an article on creating a nandroid, FWIW
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
If you are rooted, I don't know that the persistent update will actually apply/install. I'm on Classic Stock 4.4.2 and I also had the same nag. Here's a link on how to disable the update nag. This is what I did, as my phone would not apply the update so I just disabled the persistent reminder using the steps below.
http://forum.xda-developers.com/showthread.php?t=2442207
With respect to removing system apps, not sure I can offer much direction other than to suggest removing obvious apps (maybe like the Sprint Zone app) and then just doing a search on each app that looks like you can/want to delete or uninstall. Probably a bit time consuming, however, I am not aware of a "bloatware list" or anything which outlines safe-to-remove apps.
Much appreciated Lenny
When I did the root, I didn't really want a custom rom, just stock with root. Now that I've used titanium backup and have removed the install update nag- I'm set for a while!
lost in cyberspace said:
Much appreciated Lenny
When I did the root, I didn't really want a custom rom, just stock with root. Now that I've used titanium backup and have removed the install update nag- I'm set for a while!
Click to expand...
Click to collapse
You might also look at adding a free version of BusyBox (I use stericson's, and jrummy also has one out there).
Also might want to look at an install of AdAway, which you'll need to install manually (not available from the Play Store). You don't have to install the whole F-Droid package, you can download only the AdAway apk if you want.
https://f-droid.org/repository/browse/?fdid=org.adaway
One last piece of info, you may want to turn off automatic updating for apps, as the SuperSU app can have problems after an update and you might have to re-root your phone. Here's what I ran into.
http://forum.xda-developers.com/showpost.php?p=58955076&postcount=10
lennykravitz2004 said:
You might also look at adding a free version of BusyBox (I use stericson's, and jrummy also has one out there).
Also might want to look at an install of AdAway, which you'll need to install manually (not available from the Play Store). You don't have to install the whole F-Droid package, you can download only the AdAway apk if you want.
https://f-droid.org/repository/browse/?fdid=org.adaway
One last piece of info, you may want to turn off automatic updating for apps, as the SuperSU app can have problems after an update and you might have to re-root your phone. Here's what I ran into.
http://forum.xda-developers.com/showpost.php?p=58955076&postcount=10
Click to expand...
Click to collapse
Thank you! I've side loaded adb adblock is adaway better? I use App Ops to turn off specific things within each app such as location finding, I like MW apps manager to add more apps to the multiwindow feature., and I've turned off most apps auto update, but some apps I've left auto update. I've just turned off auto update on super user -- even though, I've not yet experienced any major issues as yet.
lost in cyberspace said:
Thank you! I've side loaded adb adblock is adaway better? I use App Ops to turn off specific things within each app such as location finding, I like MW apps manager to add more apps to the multiwindow feature., and I've turned off most apps auto update, but some apps I've left auto update. I've just turned off auto update on super user -- even though, I've not yet experienced any major issues as yet.
Click to expand...
Click to collapse
Don't know if adb adblock is better - I've never used it. Didn't see you mention a couple of these things when you said you were "all set for awhile", so I was just trying to offer a few other things to consider and look into. Sounds like you're already on the ball though!
Personally, I'm happy with stock. Big reason for me to root was getting rid of ads. I've tried some of the other ROMs but I've always come back to the stock look and feel. I've had the device since about 1 week after it came out in Fall 2012. Of course, I am also on my third one since I totaled two other ones. I absolutely love it, and am in no hurry to upgrade (if possible). Hope you enjoy it as I have... lots of good stuff from devs here!
see #5 for problem
Hi guys,
so after quite some time with custom Roms I decided to go stock again as somehow I don't need root at all. Well, that's not true. I miss AdAway.
As there is no possibility to root the stock rom, is there ANY AdBlocker that works on Lollipop? AdBlock Plus doesn't (yet).
Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.
ckpv5 said:
Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.
Click to expand...
Click to collapse
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?
fBx said:
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?
Click to expand...
Click to collapse
Flash twrp recovery and root through the recovery. It'll ask you when you reboot the system if you want to root it
Sent from my HTC One_M8 using XDA Free mobile app
Huh. Didn't know it was THAT straightforward and I've been flashing my phones for years.
Well. I flashed TWRP and SuperSU 2.46, succeeded. But Adaway and Adfree don't work correctly. They block the ads but only until you reboot, then it's reverted, kinda like with a tethered jailbreak on iPhones.
What am I doing wrong here? Also the block is not like on KitKat - there it was really blocked, really removed, here only the images of the ads are removed but you still see the space they were supposed to be.
I also used a system app removal tool that also didn't work although it shows success. It just removes the installed data like updates.
When I delete apps manually via ES Explorer, they just reappear at the next reboot.
Root Checker says root is fine but it isn't supposed to behave like that and undo my changes.
What's wrong? Do I need another kernel maybe? As I said I went back to stock completely and updatet through to L.
I believe I got whats causing the issue.
After deleting a system app and rebooting, I got a message saying that the phone was restored from an "unnormal behaviour". Does Lollipop bring some kind of system restore point that just automatically restores itself when "weird" things like host file alteration happens? If yes, how do I get rid of that?
This phone has always had system files protected since KitKat. You need a kernel mod to delete system apps.
Don't know why the ad blockers aren't working. Adaway is working fine for me on stock US Dev Edition rooted. You said you are using Adaway and AdFree? Are you actually using both at the same time? maybe they are interfering with each other?
No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Maybe I should try installing xposed and see if it's gone after a reboot.
fBx said:
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?t=2701816
But unfortunately, flar2 hasn't had the time to update for LP. A user posted the kernel module in Post #210, but a subsequent user said it doesn't work. Custom ROMs have write protection disabled, as does Dev Edition stock ROM.
fBx said:
No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Click to expand...
Click to collapse
Odd, as mentioned, I've used AdAway for quite some time now, and don't have these issues.
Yes, very odd indeed. Well, if I don't get it sorted out somehow I might as well switch to Viper or some other close to stock custom Rom again, or make it Dev like you.
Things are getting worse, in 1 of 2 cases AdAway spits an error at me when trying to apply the fixes and the phone just reboots and undos everything. It's like some protection from rooting or changing anything although I am rooted. I don't understand it. I can't possibly be the only one having problems with root on Stock Lollipop
This is really annoying me. I think I'm better of just installing a custom rom and setting the phone up again, will cost me an hour but at least I'm done with the bugs.
Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.
fBx said:
Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.
Click to expand...
Click to collapse
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.
redpoint73 said:
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.
Click to expand...
Click to collapse
I also assume that's the reason. I've never been on a stock rom since I don't know when, but figured that actually I only wanted AdAway which would normally not require a custom rom per se... but as it didn't really work in the end (and also other root-requiring stuff), I went back to custom again. Well, it's not that it's that difficult to wipe the phone occasionally and set up a clean custom rom to get it back to perfect performance. Gonna go with it.
Having a constant "Security Notice" on phone since rooting. Everything else works fine. Is there anyway I can maybe deactivate this function?
freeze in titanium backup...
Y0sHii said:
Having a constant "Security Notice" on phone since rooting. Everything else works fine. Is there anyway I can maybe deactivate this function?
Click to expand...
Click to collapse
to get rid of the security notice you will get(because the system is now rooted) simply install root explorer(or any root browser) and go to /system/app and delete securitylogagent or go into the folder and rename it adding .bkp to the end of the file name and reboot.
per
http://forum.xda-developers.com/showpost.php?p=68675715&postcount=2
I began getting this, too, after rooting my Note7. I solved it the way others suggested, with Titanium Backup by freezing the Security Log Agent. That worked for me.
SkyPhone said:
I began getting this, too, after rooting my Note7. I solved it the way others suggested, with Titanium Backup by freezing the Security Log Agent. That worked for me.
Click to expand...
Click to collapse
do you still have knox? i use samsung pay and security folder
You used the sprint method root at the N930V PHE or PH1? Not really related to thread, but just out of curiosity.
Same problem....
I'm having this same problem with my rooted note 7.
I've searched everywhere for securityagent on my note 7 and it's not there. The only way I can remove this threat found/restart device, is to remove device maintenance.
But then I lose the app done function and the advanced setting power saving mode.
I have disabled all knox and security realated apps.
But still still get the threat while device maintenance is there.
Does anyone know what the equivalent to securitylogagent is on a note 7 ????
Any help would be much appreciated, I am a noob, until 3 days ago I knew nothing, but I managed to unlock frp and root my note 7, but its been stressfull. I need help now...thanks.
Kellya86 said:
I'm having this same problem with my rooted note 7.
I've searched everywhere for securityagent on my note 7 and it's not there. The only way I can remove this threat found/restart device, is to remove device maintenance.
But then I lose the app done function and the advanced setting power saving mode.
I have disabled all knox and security realated apps.
But still still get the threat while device maintenance is there.
Does anyone know what the equivalent to securitylogagent is on a note 7 ????
Any help would be much appreciated, I am a noob, until 3 days ago I knew nothing, but I managed to unlock frp and root my note 7, but its been stressfull. I need help now...thanks.
Click to expand...
Click to collapse
You should have a package named SecurityLogAgent. Disabling this will stop the security notifications due to rooting. If you're referring to the Samsung messages regarding the recall, then you need to disable the Samsung Push service or just the notifications.
8
I'm not referring to them notifications, I have disabled Samsung push.
There is no package with the name 'securitylogagent' on my note 7.
I have researched this alot before joining and posting here. Its simply not there, no matter what I use to look for it. Just not there..
I would really like device maintenance back.. that's how iv got it disabled at the moment.
I am referring to the 'that found/restart device" warning that flags up in device maintenance.
Kellya86 said:
I'm not referring to them notifications, I have disabled Samsung push.
There is no package with the name 'securitylogagent' on my note 7.
I have researched this alot before joining and posting here. Its simply not there, no matter what I use to look for it. Just not there..
I would really like device maintenance back.. that's how iv got it disabled at the moment.
I am referring to the 'that found/restart device" warning that flags up in device maintenance.
Click to expand...
Click to collapse
Strange, there should be a folder at system/app/SecurityLogAgent
What firmware version are you on? What have you used to look for it?
I'm on 6.0.1, that I rooted on Sunday after I accidentally updated package disabler. I am a complete noob and have managed to just about get to this point without help.
I have looked for it using titanium backup, root browser and device control. It doesn't show on any...
So I have disabled a load of other things including device maintenance, com.samsung.andoid.sm.devicesecurity, and security manager service...
I was hoping one of these was the equivalent of securitylogagent.
Does this information below help?
Kellya86 said:
I'm on 6.0.1, that I rooted on Sunday after I accidentally updated package disabler. I am a complete noob and have managed to just about get to this point without help.
I have looked for it using titanium backup, root browser and device control. It doesn't show on any...
So I have disabled a load of other things including device maintenance, com.samsung.andoid.sm.devicesecurity, and security manager service...
I was hoping one of these was the equivalent of securitylogagent.
Does this information below help?
Click to expand...
Click to collapse
So by the build number I see that you are not on a Verizon firmware so the app names may be different. It appears you have UK firmware so you will have to find what the app name is for that firmware.
What I can suggest is that the next time you get the notification, long press on the icon at the left. You should be taken to the notification options for that app and you should also see an app info button on the right. you may be able to track the actual app down using this info or at least disable notifications.
Thanks for your reply.
Oh crap, I'll never find it then...
Is there a way I could post an image of my system so as some experienced members on here may look at it.??
Thanks again.
Hi all,
Joining Team Pixel tomorrow after my debacle with the Huawei Mate 20 Pro and the green screen fiasco.
Just wondering if its still worth rooting the Pixel? If i do it i wanna do it straight away to save wiping my data again when unlocking the BL. My main reasons would be for Adaway, Removing the Nav Bar, Swift theme installer and Viper.
Most of these can be done via ADB now so is it still worth rooting?
Rooting this phone is pretty easy and it doesn't impact the updating process much if you know what you're doing, so I vote that it is definitely worth rooting.
I don't use a lot of root apps, but the two main ones are worth it to me. I use AdAway for ads (VPN ad blockers are slower and have several cons) and an app called Sa2ration to compensate for the screen's weak color.
I have everything working the way I want without any compromises. Very happy with my setup.
It's soooo easy to root, I'm not sure why anyone wouldn't. My main reason is viper 4 android, but adaway, pixel launcher mods (changes icons and has a system UI tuner), and sd maid pro having deeper access for cleanup as well.
I've always had an Android phone that has been able to be rooted. Adaway, V4A, Substratum, Sa2ration, Titanium Backup and removing the stock navigation buttons are the biggest things for me currently with the Pixel 3 XL.
I always recommend unlocking the bootloader right out of the box, even if you never plan to root. The sole reason for this is if at any point something goes awry and you end up in a bootloop or somehow end up soft bricked, with an unlocked bootloader you can be back up and running like new with a very quick flash-all script from the latest factory image on Google's support site. However, with a locked bootloader, if you find yourself in one of those bad situations, you're at the mercy of Google support to either get you a new device or go days without a phone while they try and fix it.
So, in my opinion, unlocking the bootloader is a no brainer on these phones, right from the get-go.
With that said, rooting is much more user preference. I found no reason to root my OnePlus 6. However, with the 3 XL my sole reason for rooting is to edit the build.prop to properly hide the nav bar at the system level, allowing me to use gesture controls without issue. You can use ADB commands to achieve this as well. But my experience in trying to hide the nav bar with ADB commands on this phone has caused some wonky things to happen, such as status bar notifications not going away and volume controls getting cut off when watching something in landscape mode. Rooting the phone and editing the build.prop was the only solution that worked for me to hide the nav bar without running into unforeseen issues.
If you are one to do other things like use Magisk modules and such, then rooting will be a no brainer for you. Also, as someone else mentioned, rooting this phone is the most straight forward/simple experience I've had rooting a phone in years.
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Guitarfreak26 said:
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Click to expand...
Click to collapse
Try this: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76 do #4 then #8 if you want root. Also, Prerequisites has a link to download SDK Platform tools r28.0.1, if it needs updating.
gettinwicked said:
It's soooo easy to root, I'm not sure why anyone wouldn't. My main reason is viper 4 android, but adaway, pixel launcher mods (changes icons and has a system UI tuner), and sd maid pro having deeper access for cleanup as well.
Click to expand...
Click to collapse
I'm perfectly happy with the stock experience on this phone. I have no need for anything that requires root. I've rooted a lot of phones in the past, but there's something about this one that I just feel no need to do so. To me that says a lot for how far Google has come.
I'm getting my pixel 3 xl in a few hours today and I've been up all night watching pixel 3 xl videos. I was just about to post a question like this, but thanks to you I don't have to! The wonders of searching.
Anyways, I agree for adway and maybe even mods.
What bothers me is if I decide to use Google pay, Pokemon go or using my bank app, because I was told rooting can stop them from allowing me to use them.
I also want to do it out the box.
Also don't know about the new gesture stuff, so if I don't like it, I'd probably want to mod it.
Guitarfreak26 said:
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Click to expand...
Click to collapse
That is exactly what I did with both a Pixel 3 and a Pixel 3 XL. Just don't do a permanent install of TWRP on the XL unless you want to lose your touch screen in TWRP with no way out of TWRP when it boots back in there. I ended up having to hold the power button down until I forced the device off. Booted back into bootloader and ran the temp TWRP (which strangely works fine for touch) and then ran Magisk again to get back to the OS. Strange, the regukar Pixel 3 took permanent TWRP after Magisk, rebooted to TWRP was still able to use touch commands and ran Magisk again to get back to the proper boot image. I can even go to TWRP normally, and touch is functioning normally. I'll have to write the stock boot image when I get home today so I can get back to stock recovery until TWRP for XL is fixed.
GunToYoMouth123 said:
What bothers me is if I decide to use Google pay, Pokemon go or using my bank app, because I was told rooting can stop them from allowing me to use them.
Click to expand...
Click to collapse
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
I've been learning to live with stock ROMS, BUT, I still need my root. Adaway, TiBu, Substratum, LMT Launcher. I can't give 'em up.
Sevael said:
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
Click to expand...
Click to collapse
Ohh okay, thanks for that input !
My pixel 3 XL just got here !
Going to see what's up !
Sevael said:
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
Click to expand...
Click to collapse
My banking apps work fine but i can't get google pay to work. Even with magisk hide still not work. "This account already exists on your device" wheni try to sign in
J32A said:
My banking apps work fine but i can't get google pay to work. Even with magisk hide still not work. "This account already exists on your device" wheni try to sign in
Click to expand...
Click to collapse
Not sure, I haven't encountered this.
I find that when an app has detected root, sometimes they retain this information even through reboots. In those situations, clearing all data from the app often fixes it.
Something else to be aware of is that if you have a widget for an app that detects root, it's not uncommon for the widget to load before Magisk finishes loading and hiding after a reboot. On my Pixel 2 I had one app where after each reboot it would load first (due to a widget being present) and would detect root and block itself. I had to remove the widget and just just use a normal shortcut to the app instead, as I would never manually open it before Magisk finished loading up fully.
I just got pixel 2 xl this thing is a beast came with 5g and unlimted data when I got tablets for kids literally no download it's all instant. every phone I have had b4 is rooted most still work. My question will I improve anything by rooting with this speed? I don't think a VPN blckr would slow it down. How hard is it to reverse root if I need warranty? Is this speed the 5g or just Google built a great product?
sn0warmy said:
I always recommend unlocking the bootloader right out of the box, even if you never plan to root. The sole reason for this is if at any point something goes awry and you end up in a bootloop or somehow end up soft bricked, with an unlocked bootloader you can be back up and running like new with a very quick flash-all script from the latest factory image on Google's support site. However, with a locked bootloader, if you find yourself in one of those bad situations, you're at the mercy of Google support to either get you a new device or go days without a phone while they try and fix it.
<snip>
Click to expand...
Click to collapse
Unlocking the bl is problematic in some instances. Detection for apps and things like that. Why would you just not check off the "allow the bootloader to be unlocked" option in OEM unlocking? Then you get to fastboot and can unlock if needed without actually being unlocked and compromised.
bobby janow said:
Unlocking the bl is problematic in some instances. Detection for apps and things like that. Why would you just not check off the "allow the bootloader to be unlocked" option in OEM unlocking? Then you get to fastboot and can unlock if needed without actually being unlocked and compromised.
Click to expand...
Click to collapse
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Sent from my Pixel 3 XL
Eudeferrer said:
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Click to expand...
Click to collapse
No I don't think so. If you bl unlock it will be detected. There are kernels that will fix that but stock unlocked is a trigger.
Eudeferrer said:
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Click to expand...
Click to collapse
Yes. As @bobby janow said, some apps treat bootloader unlock as having root. DirecTV Now is a prime example. Also, Netflix won't even appear in the app store and would have to be sideloaded. Although, all of those can be worked around it is sometimes a pain.