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.
Related
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Thanks. Looks to have worked flawlessly.
Works great! Thanks!
Chainfire said:
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Click to expand...
Click to collapse
Works great. As a thank you I used my play credit from the NP Promo to upgrade to SuperSU Pro. hopefully you see that money!
Chainfire said:
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Click to expand...
Click to collapse
Thank you. Simplest root evar I will also buy SU Pro
Worked perfectly, of course. Thanks as always.
Just saw this today but had already used the other root method here to get it. Either way, thanks for all the hard work you do on everything
Chainfire said:
http://download.chainfire.eu/631/CF-Root1/Root-Nexus-Player-fugu.zip
Click to expand...
Click to collapse
Is this assured to work with both LRX21M and LRX21V?
Worked perfectly, and now StickMount is working too. Just played a video off USB in XBMC.
Does anyone know a way to remove the su app from showing in the leanback launcher. Can't find it in the settings anywhere.
Pardon my ignorance, but what does this do exactly? ...aside from the obvious "gives you root"...I mean how, what does it do to the system?
Boblank said:
Does anyone know a way to remove the su app from showing in the leanback launcher. Can't find it in the settings anywhere.
Click to expand...
Click to collapse
Well be in next version, if you set icon to invisible, it will also disappear from leanback launcher.
Zip attachment
volwrath said:
Thank you. Simplest root evar I will also buy SU Pro
Click to expand...
Click to collapse
Do you just download to phone or PC and put the extraction on the Nexus Player to gain root?
Boblank said:
Does anyone know a way to remove the su app from showing in the leanback launcher. Cant find it in the settings anywhere.
Click to expand...
Click to collapse
Are you referring to the launcher settings or SuperSU settings there should be an option in SuperSU settings to set the SuperSU icon to invisible.
I just happened to check my system today and had the OTA update from LRX21M to LRX21V waiting. I tried installing it but Recovery stopped halfway through the install with an Error. I got back into Android with a power-cycle, so things are fine, but it's still on 21M.
I'm guessing this was due to having rooted the device. Is there a proper way to remove SuperSU to allow for a system update? I see there are 3 different options for cleaning up; does it particularly matter which one I choose? I could just pick one and try it but I'm kind of curious what the differences are between the options. Anybody know?
Update: I tried the second and third cleanup options (new superuser app and full unroot) and neither got me into a state where the OTA was successful. So I just downloaded the factory image and flashed the system.img from it, then reapplied the original root process.
xBIGREDDx said:
Update: I tried the second and third cleanup options (new superuser app and full unroot) and neither got me into a state where the OTA was successful. So I just downloaded the factory image and flashed the system.img from it, then reapplied the original root process.
Click to expand...
Click to collapse
probably a full unroot and flashing the stock boot.img would fully unroot, I wonder when LRX22C (5.0.1) will hit the nexus player
The root is fundamental in all devices for many things, and thanks to Chainfire and others independent developers we can consider Android a semi-open platform. (semi-open because not all is open source)
We don't want Android like the Apple walled garden, but we are not even against the sale of the software, we just want a common garden in which the user can choose and is not obliged.
For example with the root, it was easier to start this project:
Nexus Player with a Full Version of Android Lollipop https://plus.google.com/103019026671039069038/posts/V5XaLxK3vN8
This is just the base rom with all hardware components working, on this base that is very usable, i want add many other options. like external usb webcam and mic, improving the audio part that have fixed volume and many other things useful for the use in TV.
Nexus Player is not just Android TV, but is the first Nexus device with an intel cpu. Is a milestone in the evolution of Android.
This is just the start and I am very open to sharing and collaboration on this project.
Thanks Chainfire for the root and for your "How-To SU" guidelines.
Out of interest will rooting prevent OTA updates from installing in the future?
Chainfire said:
Well be in next version, if you set icon to invisible, it will also disappear from leanback launcher.
Click to expand...
Click to collapse
I did this, despite the warning it gave me. Now although I still get permission dialogs etc, I can not run the main program to delete apps etc from SU access. Is there anyway to go back to the main screen? I went to the apps sections of the NP and unlike other apps it didnt have an open command.
To get it back do I need to uninstall and then re-CFroot?
Thanks. I should pay better attention to dialog boxes but its not a huge deal.
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.
Hi everyone,
Let me explain, I used odin to flash the recovery, because of the encryption or whatsoever I wasn't able to transfer via MTP using TWRP in order to get super Su on the phone to root and boot because of the dm-verity thing.
So I wipe data and then I could transfer super Su, get the phone rooted, and boot it up.
Of course Knox was tripped, so i can't access private folder nor S health, but I can live without it. (Ok, if someone know how to make S health work again I take it )
After all of that I tried to setup the Iris scanner again and it scan my eyes, says everything is okay, and goes back to the menu where it is written "add your iris".
No matter how many times I try it seems that it doesn't save my iris properly, or don't save it at all.
Do someone knows something about it ? for those that are rooted do you experience the same issue ?
Thanks in advance
PS : I rooted following this tutorial : http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3458413
Hello.
I did root my sm-n9300 following the tutorial.
Only SHealth didn't work.
To put it working again is easy:
Go to playstore, and downgrade the SHealth. Never allow to upgrade it again.
About the iris scanner, I had my iris saved before rooting, and didn't have to scanner it again.
The private folder works fine.
You didn't follow exactly the tutorial.
After flashing the recovery, you can tranfer su via MTP, using the sdcard, and then flash it.
Maybe if you flash the official firmware via Kies, and do the process of rooting again, you will have the iris and private folder working.
Hoppe this will help.
Hi, thanks for the answer!
In fact I wasn't able to transfer SU via mtp, for some reason twrp wasn't able to mount anything, so I had to format data, in order to "break" the encryption.
Maybe I'll try to flash the firmware with Kies and do it all over again.
But I don't get how secure folder can be working for you if knox is tripped...
Hello.
Indeed you are right.
The private folder don't work.
i thought it did, because everytime I was seeing photos, I got an information to put them in that folder, if I wished
But never did. Now I tried, and got a message saying the Knox couldn't create it.
My mistake
Sorry. But the iris do work, indeed
I really don't have any clue about how to fix the iris scanner
Trying to use a secure feature where one side of security has been compromised, i.e the ability of any app to have root privileges. I think there is a reason for the Iris scanner to not be working... Admittedly I used to enable root I every phone as I do normally tinker at system level, but, more and more apps are doing what normally root was needed for these days, the need to root is really low now. With my corporate policy basically blocking any knox tripped device, I have kind of learnt to get by without root and luckily that is now paying off with some convenience features that you can only really use in a secure environ safely like Android pay, fingerprint and iris unlock etc. Now my phone is effectively a wallet, I really want those secure features maintained so something more sinister is somewhat blocked from making its way into there.
Sent from my SM-N930F using Tapatalk
I see your point, the fact is when trying to set up the iris scanner there is no message about compromised security like when trying to open the secure folder.
In fact it works, it just seems to not be able to save it properly.
My phone is also a wallet in China since wechat pay and alipay can be use even on rooted phone, and it also can be use everywhere. ( no need of special terminal or whatever special technology, just a bar code scanner)
Thanks for your answer, I think k I'll try a factory reset tomorrow and let you know
I remember when setting up either finger print scanner or iris, the phone brought up a message about knox environment being activated, so I think you will be out of luck.
Be careful with rooted phone in China, I connected my rooted phone to my Chinese wife's laptop, and it installed an app with root privileges unattended!! I was not impressed with that I can tell you.
Sent from my SM-N930F using Tapatalk
it is bcoz u have disabled encryption in twrp .... if u want to use iris dnt clear encryption in twrp ....
sun2sunny said:
it is bcoz u have disabled encryption in twrp .... if u want to use iris dnt clear encryption in twrp ....
Click to expand...
Click to collapse
OK!
But how can I enable the encryption then?
I can't mount anything in twrp tough....
That is what I m searching next a days
Sent from my SM-N9300 using XDA Free mobile app
sun2sunny said:
That is what I m searching next a days
Click to expand...
Click to collapse
I guess the only way is to use a custom kernel, it will disabled knox and s health last version and iris scanner will work again
SylverSun said:
I guess the only way is to use a custom kernel, it will disabled knox and s health last version and iris scanner will work again
Click to expand...
Click to collapse
Where can we find it another question
sun2sunny said:
Where can we find it another question
Click to expand...
Click to collapse
Yes, maybe on some Chinese forum
Searched already
Ok the title says it best.
I would like some opinions about which route you took and why.
I personally have rooted and then noticed lag every time.
After debloating it got a little better and almost near stock speed.
Following debloat I started having issues with ghost apps and apps really disappearing and not working.
I've also tried rooting, debloat, and then unrooting.
results were not much better.
Finally I'm going to try just debloating with package disabler pro and Beast mode (disabling animations etc) - No ROOT
I'll post my results but let me add I've never used a device that was not rooted so this is a nerve racking decision.
Not much activity going on with this model. Wish I would have bought something more popular. Lol.
Active magisk? + Bootloader
jjta said:
Ok the title says it best.
I would like some opinions about which route you took and why.
I personally have rooted and then noticed lag every time.
After debloating it got a little better and almost near stock speed.
Following debloat I started having issues with ghost apps and apps really disappearing and not working.
I've also tried rooting, debloat, and then unrooting.
results were not much better.
Finally I'm going to try just debloating with package disabler pro and Beast mode (disabling animations etc) - No ROOT
I'll post my results but let me add I've never used a device that was not rooted so this is a nerve racking decision.
Click to expand...
Click to collapse
Hi, im new to the forum, have an s7 active but i cant seem to unlock the bootloader, or find a way to install magisk mgr so i can hide my root and still play pokemon go ... please help
king2289 said:
Hi, im new to the forum, have an s7 active but i cant seem to unlock the bootloader, or find a way to install magisk mgr so i can hide my root and still play pokemon go ... please help
Click to expand...
Click to collapse
Sad to say it one of those AT&T things where they lock them and its almost impossible to unlock. Don't think its been done for this phone yet! Try to see if theirs a way to install magisk mgr using flashfire otherwise no root or no pokemon!
thanks
jjta said:
Sad to say it one of those AT&T things where they lock them and its almost impossible to unlock. Don't think its been done for this phone yet! Try to see if theirs a way to install magisk mgr using flashfire otherwise no root or no pokemon!
Click to expand...
Click to collapse
thank you
jjta said:
Sad to say it one of those AT&T things where they lock them and its almost impossible to unlock. Don't think its been done for this phone yet! Try to see if theirs a way to install magisk mgr using flashfire otherwise no root or no pokemon!
Click to expand...
Click to collapse
I cant install flashfire lol im not rooted (cries)
jjta said:
Ok the title says it best.
I would like some opinions about which route you took and why.
I personally have rooted and then noticed lag every time.
After debloating it got a little better and almost near stock speed.
Following debloat I started having issues with ghost apps and apps really disappearing and not working.
I've also tried rooting, debloat, and then unrooting.
results were not much better.
Finally I'm going to try just debloating with package disabler pro and Beast mode (disabling animations etc) - No ROOT
I'll post my results but let me add I've never used a device that was not rooted so this is a nerve racking decision.
Click to expand...
Click to collapse
See this old post:
https://forum.xda-developers.com/showpost.php?p=74551312&postcount=815
I'm wondering if its the newest update thats causing the battery to act like trash...
I've been getting screen freezes that last a few seconds and lags that got much worse after the last update. Is anyone else having this problem? Any solutions?
I had this, so at the weekend I went and completely flashed the image via adb and it's fixed most of my issues. I have noticed that Facebook is constantly slow to load(compared to my Galaxy S6) so i've left an app review - and uninstallled, now using FB lite for the time being
No issues here, but manually updated to March using the factory image followed by root via fastboot twrp.
You need to add more detail to your posts as there are lots of questions left unanswered that could be important.
Eg
Do you mean the march security update? Was it updated OTA or manually? If manually, which image and what method? Rooted? Modded? Have you checked your apps for any that might be suspicious or just really old? Have you backed up and reset? Etc etc.
Good luck
kboya said:
No issues here, but manually updated to March using the factory image followed by root via fastboot twrp.
You need to add more detail to your posts as there are lots of questions left unanswered that could be important.
Eg
Do you mean the march security update? Was it updated OTA or manually? If manually, which image and what method? Rooted? Modded? Have you checked your apps for any that might be suspicious or just really old? Have you backed up and reset? Etc etc.
Good luck
Click to expand...
Click to collapse
For me, I was on February before I flashed the latest build at the weekend.
I had various apps installed, could have been anything. Most of the experimental apps were things like the modified camera app which allows the Pixel XL 2 HDR+ etc...
Personally, I think flashing a device over ADB is a necessity sometimes - I had tried clearing the app cache, with this a/b boot partitions, there's no clear cache in bootloader - so took the plunge, glad I did because my battery and overall performance of the phone has improved.
I just forgot to lock the bootloader, which means when I came to pay for my train this morning I couldn't set up Android Pay.
droid_1989 said:
For me, I was on February before I flashed the latest build at the weekend.
I had various apps installed, could have been anything. Most of the experimental apps were things like the modified camera app which allows the Pixel XL 2 HDR+ etc...
Personally, I think flashing a device over ADB is a necessity sometimes - I had tried clearing the app cache, with this a/b boot partitions, there's no clear cache in bootloader - so took the plunge, glad I did because my battery and overall performance of the phone has improved.
I just forgot to lock the bootloader, which means when I came to pay for my train this morning I couldn't set up Android Pay.
Click to expand...
Click to collapse
GPay works with unlocked bootloader and magisk
kboya said:
GPay works with unlocked bootloader and magisk
Click to expand...
Click to collapse
Yeah, I get that, but I don't root anymore. I don't fully see the need to - and it feels like it's more hassle these days.
Maybe when I get some spare time I will consider rooting again. I'll just lock the bootloader via fastboot and adb tonight.
I only really root for adblocking, but it's entirely your call