Related
Is there a possibility that Amazon might remove the ability to side load apps with future firmware auto update, if you are not rooted?
Thank you
Sure there is. There's a possibility they could do all sorts of bone-headed things to it.
wellersl said:
Sure there is. There's a possibility they could do all sorts of bone-headed things to it.
Click to expand...
Click to collapse
But of course they never would. Because then people wouldn't be able to test their apps on it. No people testing apps == no one releasing apps.
the probably couldn;t remove the Install from Unknown Sources since it;s part of the OS. But they could try to hide it. They could try to hide file managers like ES File manager from their app store as well. It;s more truble than it;s worth. But as long as you can use ADB to push and install apps to your device we will be fine.
I think the biggest thing we need is to unlock the bootloader because that will allow you to install a custom recovery like TWRP or CWM if you want full command and control of the unit.
rbox said:
But of course they never would.
Click to expand...
Click to collapse
But of course!
In your esteemed opinion, did they deliberately cause the eFuse/locked bootloader fiasco? IOW - Was that a conscious move on Amazon's part?
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
tekweezle said:
They could try to hide file managers like ES File manager from their app store as well.
Click to expand...
Click to collapse
They don't need to hide it. They've determined that it's not compatible.
Strange to me how the Amazon app store is so void of apps that *are* compatible with my Fire TV. :silly:
tekweezle said:
the probably couldn;t remove the Install from Unknown Sources since it;s part of the OS. But they could try to hide it. They could try to hide file managers like ES File manager from their app store as well. It;s more truble than it;s worth. But as long as you can use ADB to push and install apps to your device we will be fine.
I think the biggest thing we need is to unlock the bootloader because that will allow you to install a custom recovery like TWRP or CWM if you want full command and control of the unit.
Click to expand...
Click to collapse
They can do whatever they want. They have all of the source code.
wellersl said:
But of course!
In your esteemed opinion, did they deliberately cause the eFuse/locked bootloader fiasco? IOW - Was that a conscious move on Amazon's part?
Click to expand...
Click to collapse
Very much so. They went out of their way to write a program that blew the fuse.
rbox said:
Very much so. They went out of their way to write a program that blew the fuse.
Click to expand...
Click to collapse
Now see, IMO, if I fell victim to that, I'd have them in small claims court in a heartbeat. That's just plain bone-headed consumer product management. That is... if I could prove it.
Note to Amazon: How about a *special* Fire TV with *Special Offers"?
wellersl said:
Now see, IMO, if I fell victim to that, I'd have them in small claims court in a heartbeat. That's just plain bone-headed consumer product management. That is... if I could prove it.
Note to Amazon: How about a *special* Fire TV with *Special Offers"?
Click to expand...
Click to collapse
It's common practice. All the manufacturers do it. What would you sue them for? Protecting their product? They are patching vulnerabilities.
rbox said:
It's common practice. All the manufacturers do it. What would you sue them for? Protecting their product? They are patching vulnerabilities.
Click to expand...
Click to collapse
Well... it just occurred to me. They aren't actually disabling the device, are they? I keep seeing the term "brick." If, in fact, they're bricking these devices, wrong. There's absolutely nothing that came with or on my Fire TV that says I can't root it.
Else, in terms of vulnerability, I could see them locking me out of AVOD. But they should have any say over my access to Netflix.
wellersl said:
Well... it just occurred to me. They aren't actually disabling the device, are they? I keep seeing the term "brick." If, in fact, they're bricking these devices, wrong. There's absolutely nothing that came with or on my Fire TV that says I can't root it.
Else, in terms of vulnerability, I could see them locking me out of AVOD. But they should have any say over my access to Netflix.
Click to expand...
Click to collapse
All the efuse does is prevent you from booting an old bootloader. As long as you aren't doing the things we are doing, it's harmless. But if you try to go out of your way to screw around with the software and use an old bootloader, then it will be bricked because the old bootloader will not work with the fuse blown, and it doesn't boot. It has nothing to do with rooting, nor anything to do with avod or netflix...
rbox said:
... use an old bootloader, then it will be bricked because the old bootloader will not work with the fuse blown, and it doesn't boot.
Click to expand...
Click to collapse
Still trying to grasp this...
If you aren't trying to root, why else would you use an old bootloader?
rbox said:
They are patching vulnerabilities.
Click to expand...
Click to collapse
I was only using Netflix as an example. I don't see Amazon bricking their devices to patch a competitor's vulnerabilities. Though that is a strange relationship...
wellersl said:
Still trying to grasp this...
If you aren't trying to root, why else would you use an old bootloader?
I was only using Netflix as an example. I don't see Amazon bricking their devices to patch a competitor's vulnerabilities. Though that is a strange relationship...
Click to expand...
Click to collapse
You use the old bootloader so you can take advantage of the bug in the bootloader and load unsigned code. Custom kernels, custom roms, recovery, etc.
That makes no sense... they patched a vulnerability in the bootloader and then prevent you from using said vulnerable bootloader... It has nothing to do with apps.
rbox said:
You use the old bootloader so you can take advantage of the bug in the bootloader and load unsigned code. Custom kernels, custom roms, recovery, etc.
That makes no sense... they patched a vulnerability in the bootloader and then prevent you from using said vulnerable bootloader... It has nothing to do with apps.
Click to expand...
Click to collapse
Got the first point (I think).
On the second point, Amazon can obviously patch what they perceive as vulnerabilities -unrestricted-. But as soon as they've patched me out of an otherwise legitimate use of the box, they've gone too far. IMHO.
Some years back, I filed a claim against UPS and won. I'm sure they got the paperwork and had no clue what to do with it.
More recently, I filed a claim with the BBB against Roku for the crappy firmware they pushed out on the 2XS. Roku sent me a new 2XS and a new Roku 3. Just to shut me up.
wellersl said:
Got the first point (I think).
On the second point, Amazon can obviously patch what they perceive as vulnerabilities -unrestricted-. But as soon as they've patched me out of an otherwise legitimate use of the box, they've gone too far. IMHO.
Some years back, I filed a claim against UPS and won. I'm sure they got the paperwork and had no clue what to do with it.
More recently, I filed a claim with the BBB against Roku for the crappy firmware they pushed out on the 2XS. Roku sent me a new 2XS and a new Roku 3. Just to shut me up.
Click to expand...
Click to collapse
Bypassing their secure bootchain is not a legitimate use. Exploiting a vulnerability in the kernel to gain root is also not a legitimate use.
rbox said:
Bypassing their secure bootchain is not a legitimate use. Exploiting a vulnerability in the kernel to gain root is also not a legitimate use.
Click to expand...
Click to collapse
Obviously, I'm not getting my point across. But that's ok.
Peace.
rbox said:
But of course they never would. Because then people wouldn't be able to test their apps on it. No people testing apps == no one releasing apps.
Click to expand...
Click to collapse
Hi Rbox,
This make sense thank you for responding but can the developer just be released the app in amazon app store as free and then user would just download from amazon app, unless of course it is really painful process to get an app approved by amazon for a developer than i can understand or why go thru the process again with amazon if the app is already on google play store.
It seems there are quite a few folks out there who chose not to root there device as long as they can side load any apps they want, which is fine but if Amazon goal is to lock down user on there echosystem than allowing folks to side load any apps user wants this would seriously undermine there goal (Amazon app store, AFTV device, the whole amazon echosystem), this is Just my opinion.
Thank you
ashsha7877 said:
Hi Rbox,
This make sense thank you for responding but can the developer just be released the app in amazon app store as free and then user would just download from amazon app, unless of course it is really painful process to get an app approved by amazon for a developer than i can understand or why go thru the process again with amazon if the app is already on google play store.
It seems there are quite a few folks out there who chose not to root there device as long as they can side load any apps they want, which is fine but if Amazon goal is to lock down user on there echosystem than allowing folks to side load any apps user wants this would seriously undermine there goal (Amazon app store, AFTV device, the whole amazon echosystem), this is Just my opinion.
Thank you
Click to expand...
Click to collapse
It has nothing to do with releasing apps. If I make an app for the Fire TV. I'm going to test it on the Fire TV. And the way I do that is using adb install. They can't block that, or else no one would be able to test their apps.
rbox said:
It has nothing to do with releasing apps. If I make an app for the Fire TV. I'm going to test it on the Fire TV. And the way I do that is using adb install. They can't block that, or else no one would be able to test their apps.
Click to expand...
Click to collapse
Ahh, since you put it that way it make more sense. Thank you Sir!
Also it would be a pretty stupid move for Amazon to add "Install from unknown sources" in their latest firmware's if they did not wan't people to install 3'rd party android app's on it. As you do not have to "sideload" with adb anymore, you can just install a webbrowser and browse to a web site (kodi.tv for example) click on a installer .apk and it will immediately install. You can also copy the apk to the sdcard and click on it in a filebrowser and it will install.
Amazon put that option in 1 version ago. So beginning to remove sideloading via. adb and hiding apps seems pretty silly to me.
But ofcause in theory they still have the source and the rights to do what they like..
On the one hand, Amazon doesn't have to provide support for side loaded apps, which saves them money. On the other hand, some side loaded apps allow users to access premium content for free, so Amazon might claim they lose revenue, but those users probably would never have purchased premium content from Amazon in the first place and at least they made some money off the hardware. So I would say that they won't revoke side loading functionality.
Has anyone tried to see what works with some bloatware disabled & what doesn't work? Personally I would like the iris scanner and samsung pay to be enabled and everything else disabled.
Yeah, it's working for me quite well
XavierAD said:
Yeah, it's working for me quite well
Click to expand...
Click to collapse
Glad to hear it,arguably the best feature available for any Samsung device,short of root/ROMs.
Hopefully it'll still work once Android 7.0 rolls out.
KOLIOSIS said:
Glad to hear it,arguably the best feature available for any Samsung device,short of root/ROMs.
Hopefully it'll still work once Android 7.0 rolls out.
Click to expand...
Click to collapse
It will. They use Knox which is a product of Samsung.
Sent from my XT1528 using XDA Labs
I'm rather confused by this thread. Is the poster asking what will 'break' if you disabled all the bloatware? Or asking something else entirely? Cause you can disable everything that comes on any phone and it'll always work just fine.
And I have no idea what Android 7.0 would have to do with bloatware, or what KNOX would have to do with bloatware...
HikariNoKitsune said:
I'm rather confused by this thread. Is the poster asking what will 'break' if you disabled all the bloatware? Or asking something else entirely? Cause you can disable everything that comes on any phone and it'll always work just fine.
And I have no idea what Android 7.0 would have to do with bloatware, or what KNOX would have to do with bloatware...
Click to expand...
Click to collapse
I can't speak for the O.P.,but,my guess is, as with me, just making sure that it works before purchasing the Note 7,especially for those of us with the Snapdragon powered versions that may have no other way to disable bloat.
JMHO, but, the Q&A regarding functionality of PDP, whatever they may be, are of merit & might as well have a thread addressing the subject.
Most realize you can disable the bloat, but,not everyone, including yours truly, understand exactly how it works & why only on Samsung devices.
The Knox tie-in makes sense to me, even without a full understanding of how it works.
KOLIOSIS said:
I can't speak for the O.P.,but,my guess is, as with me, just making sure that it works before purchasing the Note 7,especially for those of us with the Snapdragon powered versions that may have no other way to disable bloat.
JMHO, but, the Q&A regarding functionality of PDP, whatever they may be, are of merit & might as well have a thread addressing the subject.
Most realize you can disable the bloat, but,not everyone, including yours truly, understand exactly how it works & why only on Samsung devices.
The Knox tie-in makes sense to me, even without a full understanding of how it works.
Click to expand...
Click to collapse
KNOX doesn't make much sense to me, because that's just a security platform. It just makes sure you protected from being 'hacked' per say. As in like, it adds an extra layer of security over your phone so someone can't just pick it up and plug it into a computer to gain access to all of your stuff. Though thats only the very loosest of analogies.
But I have to ask what you exactly mean by the "not everyone understands exactly how it works and why only on Samsung devices". Do you mean as in why disabling works? or something else. Because you can disable the bloatware on any android phone so long as the carrier and manufacturer didn't lock the option out. Which most devices will let you do it now because of the whole 'you'll get sued for forcing users to use a specific thing without giving them a way out' (an example would be microsoft getting sued over the bundling of Internet Explorer and Microsoft Office with the earlier Windows OS's).
What I'm wondering is, based on the title of the thread after thinking about it some, does the OP mean an app that disables/uninstalls bloat? Because I'm sure there are plenty of apps out there that do it. But most I think require Root in order to do it properly and reliably. I use Sprint for my service, and its Sprint ID and such are a pain in the ass, and they can't just be 'disabled' easily even though there is the option to (every time you disable it, Sprint just re-installs it the next time you reboot the phone because it thinks it got uninstalled somehow). But to get it to disable properly on my Note 5, I had to install some random app that I think was called App Quarantine. It looked like a bio-hazard symbol for the icon. I haven't re-installed it since this last wipe I was forced to do, so I can't remember exactly lol. But it was the only one that would let me actually disable the Sprint ID stuff and not have it re-install all the time.
HikariNoKitsune said:
What I'm wondering is, based on the title of the thread after thinking about it some, does the OP mean an app that disables/uninstalls bloat? Because I'm sure there are plenty of apps out there that do it.
Click to expand...
Click to collapse
Yes it's an app in the Google Play Store that has the ability to disable literally anything on Samsung devices,WITHOUT ROOT, so, care must be taken to not get carried away & I recommend only disabling, not deleting, in the event of not being able to take an update otherwise.
Not everything can be disabled natively, so, that explains the appeal of the app.
If you used it, you'd see the tie-in with Knox........
KOLIOSIS said:
Yes it's an app in the Google Play Store that has the ability to disable literally anything on Samsung devices,WITHOUT ROOT, so, care must be taken to not get carried away & I recommend only disabling, not deleting, in the event of not being able to take an update otherwise.
Not everything can be disabled natively, so, that explains the appeal of the app.
If you used it, you'd see the tie-in with Knox........
Click to expand...
Click to collapse
Then that makes alot more sense. I originally just thought they were basically asking if there was an app to disable everything instead of having to do it manually. I've always just manually disabled everything cause its not that hard to do. Just find the troublesome things and hit that disable button lol. But if this can do it all in one quick swoop, then I'm all in =O I'll definitely be looking into it later today when my phone finally arrives...
Sprint screwed up my pre-order, and is sending me the wrong device, so I have to take it into a store to get it exchanged because they refused to cancel my pre-order or change the order at all even though I legitimately ordered the dang thing 2 minutes past midnight on the 3rd. So ontop of that, they also didn't ship the phone when they said they would, AND the put restrictions on my package. I normally have to physically go to a UPS location to pick up my packages cause the dumb driver will never deliver to my house... always states that they can't find my house even though its the ONLY house down the ONLY long driveway... heck you can SEE my house above the trees! But nope, the guy wont deliver. But because of the restrictions, UPS wont let me flag the package as 'hold for pickup' like usual, so I gotta stand at the end of my drive way for hours upon hours just to catch the UPS driver. Then I gotta drive all the way into town to HOPEFULLY exchange the phone for the Black Onyx variant that I was supposed to get...
Anyway, sorry for the ramble o-o; didn't realize it was that long XD
HikariNoKitsune said:
Then that makes alot more sense. I originally just thought they were basically asking if there was an app to disable everything instead of having to do it manually. I've always just manually disabled everything cause its not that hard to do. Just find the troublesome things and hit that disable button lol. But if this can do it all in one quick swoop, then I'm all in =O I'll definitely be looking into it later today when my phone finally arrives...
Click to expand...
Click to collapse
It's a nice tool to have, a powerful one.
Just a friendly piece of advice :
Read up on it before using, check the FAQs on the developers site if need be & go conservative at 1st if you're not familiar with what is safe to disable.
The app gives color-coded guidelines per each app on what is known to be safe to disable. You can go above and beyond that, but, mainly, just disable, do not delete anything & leave the stock keyboard alone.
You might be able to disable the stock launcher, provided you have another one installed, but, I'd leave it alone until you're certain one way or the other........
KOLIOSIS said:
It's a nice tool to have, a powerful one.
Just a friendly piece of advice :
Read up on it before using, check the FAQs on the developers site if need be & go conservative at 1st if you're not familiar with what is safe to disable.
The app gives color-coded guidelines per each app on what is known to be safe to disable. You can go above and beyond that, but, mainly, just disable, do not delete anything & leave the stock keyboard alone.
You might be able to disable the stock launcher, provided you have another one installed, but, I'd leave it alone until you're certain one way or the other........
Click to expand...
Click to collapse
Lol I'd only disable the things I already know I need to disable. Like all the Sprint stuff. I leave the Samsung stuff alone cause I actually use alot of Samsung's things. But as for Sprint's stuff? All of that goes bye bye lol. Now that is assuming it doesn't somehow show things that you normally can't see from the applications manager. In which case then I wouldn't bother, cause I don't see much of a point lol.
there are a few package disabler for Samsung out there, which one the best?
amenlo9 said:
there are a few package disabler for Samsung out there, which one the best?
Click to expand...
Click to collapse
Go with either one,the Pro+ has a hardware lockdown feature,otherwise,there two are identical:
https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpremium&hl=en
https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro&hl=en
I'm guessing Samsung still has a partnership w/Cheetah Mobile,which is one of the main reasons I like having this app,Package Disabler Pro,on-board to ward off the data mining/crapware/etc...
However,I'm not seeing anything in the apps,system or otherwise,that's jumping out & identifying itself as CheetahMobile/CleanMaster/etc.......
I'm guessing it's some/all of the apps identified w/the "Smart" moniker,but,I'm not 100% certain on that.
Anyone have an idea on which,if any,of the apps are actual CheetahMobile bloatware?
Thanks In Advance!
Using EZ Disabler here. Works well, but you gotta be careful using "disable bloat" part as it will turn off many useful things. I just went through and picked what i wanted. Very Easy to use though
Thanks for recommending Package Disabler Pro. I was worried Since not rooted. In past had always used TB . This worked Great!!
Sent from my SM-N930P using Tapatalk
Why would you guys use an app for disabling stuff.
Since we're on xda, enable USB debugging and use pm (package manager) cmd from adb shell.
For instance: adb shell pm hide 'package'
There are other interesting options: list, install, uninstall.
Sent from my HTC One using Tapatalk
millicent said:
Why would you guys use an app for disabling stuff.
Since we're on xda, enable USB debugging and use pm (package manager) cmd from adb shell.
For instance: adb shell pm hide 'package'
There are other interesting options: list, install, uninstall.
Click to expand...
Click to collapse
I see your point, but i would also say there is a ease to the app though. Whatever works best for people. Im just glad there are options.
I have been finding myself only using Magisk for EmojiOne, but noticing I don't use Emoji like I used to anymore and am thinking since I only use Substratum with a Center Clock mod and have stopped using it for Dark theming, maybe going back to a stock based setup would be fine. I can use the Andromeda thing with Substratum which is an extra step but can do my center clock and possibly emoji one via substratum... not sure what else I would want root for... Updating is a touch of a pain for me. What do yo guys think, and have any of you gone back to stock?
I went back to stock just because I didn't want to have the uncertainty of being rooted.
Nothing wrong with rooting but I love this phone the way it is.
Sent from my Pixel 2 XL using Tapatalk
For myself Rooting was a necessity. The devices sold in the past had so much Crapware.
It was nice to get the latest and greatest ROM and tweak the device to run faster because at that time they were just plain old slow.
Today, depending on where you bought a device devices are very fast. It seems to me that every ROM has an issue that influences the character of the device.
If your device comes from a carrier such as Verizon you should Root it to get rid of their crapware.
It seems their attitude is you only have the right to buy their device not the ability to control, I mean really you think you own it or something? ( yes I'm a VZW hater)
What was the question?
kdkinc said:
For myself Rooting was a necessity. The devices sold in the past had so much Crapware.
It was nice to get the latest and greatest ROM and tweak the device to run faster because at that time they were just plain old slow.
Today, depending on where you bought a device devices are very fast. It seems to me that every ROM has an issue that influences the character of the device.
If your device comes from a carrier such as Verizon you should Root it to get rid of their crapware.
It seems their attitude is you only have the right to buy their device not the ability to control, I mean really you think you own it or something? ( yes I'm a VZW hater)
What was the question?
Click to expand...
Click to collapse
Lol, I agree 100%. I can simply disable gMail and Calculator, the only 2 APPs pre-installed on my Pixel 2 XL that I don't need. I use Inbox by Google for eMails and a Calculator Widget for that. Aside from the EmojiOne and CenterClock, I don't even dark-theme anymore, especially not on this device with the "black crush" all the OLEDs have an issue with. I was rooted fro KCal, but am finding the Boosted setting works just fine and oddly my Blue Tint has weakened since my first few days where it was really bad. Almost like the display is wearing in and getting better? It's still there, but just not as much as that first fresh opening, so warming up the display isn't needed much for me now either.
I like to see where people's heads are at with each device, and this is one the extra input is nice to read.
I'm actually on the fence about rooting. Just received my phone this weekend and I can't decide. Going to unlock bootloader before fully setting up, but I have been playing with it a little. I've always rooted and ran custom ROMs as well as adaway. With PureNexus on my N6 I stopped flashing for over a year except the occasional ROM update. I simply like Android in it's simplest form.
I will always root, no matter what. The only downside is like you said, having to mess with getting OTAs in an unnatural way. However, seeing as how I flash all factory images, I get them sooner than those waiting on an OTA to hit their phone. Plus once you have all the tools ready to go, it literally only takes a few minutes to flash an update.
I always root because I usually run stock. And while stock on a Pixel 2 XL is damn near close to perfection, it will never be what "I" consider perfect. Which means I have to mess with the /system files to get things "perfect." I've modded the stock launcher, which I couldn't do if I was rooted. I've switched out fonts. I've changed the navbar, status bar, and quick settings. And of course, there's always AdAway which requires root. Granted some of those things can be achieved with third party apps, but I'd rather get it done "internally" whenever possible.
I used to have it for years, then more and more companies (Google and banks) made their apps check for root, and I tired of the cat and mouse game with SuperSU and Magisk. So I unrooted over a year ago. Didn't miss it at all until yesterday, when I wanted to do something with Tasker that requires root. But what I wanted to do falls into the category of "it would be nice" as opposed to "I have/need to do this", so I remain unrooted. I haven't really missed it much.
I am stuck without root since I have the Verizon model which was given to me free from work so I cannot complain too much. I have always rooted and messed with ROMs. The only thing I would need root for with the 2 XL is ad blocking with Chrome. I am trying the Samsung browser and ABP which work pretty well together.
If I didn't have the noise cancellation mic issue on my 6P I think I would have given up root a long time ago...
I rotate between stock and rooted daily lol
Sent from my Pixel 2 XL using Tapatalk
I am sort of glad I found this thread. I'm not a XDA regular but I've been following root guides from here since my Razr Mazz HD. I chose the Pixel in part for the ease of getting root and for Project Fi. Now that I have the phone, I'm not sure I want to root. I've never had a phone with quick updates before. I LOVE AdAway, but is it really worth the tradeoff? AdGuard is just as good if you don't use your VPN slot but if you DO use a VPN and need it.... not rooting forces me to choose between PIA and AdGuard. But do I even need a VPN anymore with Project Fi? Probably... Firefox with uBlock works pretty well too but doesn't work on apps. Oh the decisions.
Ruraltech said:
I am sort of glad I found this thread. I'm not a XDA regular but I've been following root guides from here since my Razr Mazz HD. I chose the Pixel in part for the ease of getting root and for Project Fi. Now that I have the phone, I'm not sure I want to root. I've never had a phone with quick updates before. I LOVE AdAway, but is it really worth the tradeoff? AdGuard is just as good if you don't use your VPN slot but if you DO use a VPN and need it.... not rooting forces me to choose between PIA and AdGuard. But do I even need a VPN anymore with Project Fi? Probably... Firefox with uBlock works pretty well too but doesn't work on apps. Oh the decisions.
Click to expand...
Click to collapse
If you like it the way it is, then I'd just leave it. It's a great device on stock. However, having root, AdAway, TiBu, kernels, and mods, is a lot of fun as well. As long as you know adb and fastboot fairly well, rooting and flashing monthly updates is pretty easy :good:
I was rooted from the get go!!
I'm going to try to live without root for a bit but already hating not having AdAway. I just know I won't keep up with updates if I have to do them. I sure wish AdAway didn't need root
Ruraltech said:
I am sort of glad I found this thread. I'm not a XDA regular but I've been following root guides from here since my Razr Mazz HD. I chose the Pixel in part for the ease of getting root and for Project Fi. Now that I have the phone, I'm not sure I want to root. I've never had a phone with quick updates before. I LOVE AdAway, but is it really worth the tradeoff? AdGuard is just as good if you don't use your VPN slot but if you DO use a VPN and need it.... not rooting forces me to choose between PIA and AdGuard. But do I even need a VPN anymore with Project Fi? Probably... Firefox with uBlock works pretty well too but doesn't work on apps. Oh the decisions.
Click to expand...
Click to collapse
I'm not regretting going back to stock from rooted as the only things I no longer have is center clock and emojione, which I 'could' get using Andromeda / Substratum but heard you have to reconnect to the computer anytime you reboot the phone and decided that's just not worth it for me. I am interested in ad blocking if possible without Root for Chrome. Only Ads that get in my way are via "News" and articles I touch from the Google Feed. Sadly many lately are blatant click-bait, page-hopping crap and slideshows that I refuse to go past the first page on.
Edit: Well, just ran across something known as DNS66 and have that up and running without Root and sure enough, it's blocking Ads on everything, even in Chrome without issue.
sharkie405 said:
I will always root, no matter what. The only downside is like you said, having to mess with getting OTAs in an unnatural way. However, seeing as how I flash all factory images, I get them sooner than those waiting on an OTA to hit their phone. Plus once you have all the tools ready to go, it literally only takes a few minutes to flash an update.
I always root because I usually run stock. And while stock on a Pixel 2 XL is damn near close to perfection, it will never be what "I" consider perfect. Which means I have to mess with the /system files to get things "perfect." I've modded the stock launcher, which I couldn't do if I was rooted. I've switched out fonts. I've changed the navbar, status bar, and quick settings. And of course, there's always AdAway which requires root. Granted some of those things can be achieved with third party apps, but I'd rather get it done "internally" whenever possible.
Click to expand...
Click to collapse
Whats your few minute process? Do you only have a few apps to restore with data?
plisskenn said:
Whats your few minute process? Do you only have a few apps to restore with data?
Click to expand...
Click to collapse
Flash without wiping data.
plisskenn said:
Whats your few minute process? Do you only have a few apps to restore with data?
Click to expand...
Click to collapse
See below. ?
jrbxx7 said:
Flash without wiping data.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using XDA Labs
First thing I did with my unlocked XL 2 was to unlock the bootloader. I then rooted once Magisk was available. I root so I can do pain-free full TiBu of my apps and for AdAway. Even though I have corporate email on my phone, the Magisk Hide bypasses their restrictions in the email app.
I'm actually kind of shocked we don't have more ROMs for this phone, though I'm not a Dev and don't know how complex it may be. If more Devs release custom ROMs, I'll be trying some out for sure.
I never buy android phone unless it's bootloader-unlockable and root-able
Too many handicap applied without root.
I hate dns/vpn based adblock, it cluttering my status bar and notification. So, yes, i need root for adaway,
Google limit Tethering frequency option for my country (No 5Ghz) so, yes, i need root to enable it,
I like the ability to background play youtube, and see youtube without ads, so yes, i root my phone for that. Sure, no root option is available, but lot of problem with google account cant sign in, and this and that.
I like the ability to use Brevent, Edge Sense Plus, Greenify etc without the need of plugging my phone to PC and do adb command. So, yes, i rooted my phone for that.
The phone will never be 100% yours, unless you have total control over anything inside it
So,
There's no way am back to stock. Especially with xposed working so well right now.
otonieru said:
I like the ability to background play youtube, and see youtube without ads, so yes, i root my phone for that. Sure, no root option is available, but lot of problem with google account cant sign in, and this and that.
Click to expand...
Click to collapse
Assuming you are using Magisk, how did you get YouTube Red without subscribing? (You can PM me if you don't want to hijack this thread...)
Has anyone gotten g pay to work on the q beta 6 while being rooted if so how did you achieve it
This work for me on custom rom:
https://forum.xda-developers.com/showpost.php?p=79643248
lavin40 said:
Has anyone gotten g pay to work on the q beta 6 while being rooted if so how did you achieve it
Click to expand...
Click to collapse
As far as I know it won't pass. Even while rooted/unrooted as it won't pass cts
Followed this process. Uses a few modules and I have had no issues since.
https://forum.xda-developers.com/showthread.php?p=79915863
Sent from my Pixel 2 XL using Tapatalk
alershka said:
Followed this process. Uses a few modules and I have had no issues since.
https://forum.xda-developers.com/showthread.php?p=79915863
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thank you for this....I really very much appreciate it! Seems the most complicated tutorial/walkthrough than most others (simple magiskhide and/or modifying certain files...), but it seems most promising as well.
I just wanted to ask (specifically a person who has experience with this successfully and is possibly continuing doing this) if you do the monthly updates and if it resets everything and you have to edit a database file via SQL editor every single time? I, myself, imagine that if you do a Full Factory flash-all update, it would overwrite either the permissions and/or the .db file, but I wanted to confirm with someone else as I've already updated to the August security patch...
Thank you again for posting your response here and I look forward to seeing my GPay work in the stores!
simplepinoi177 said:
Thank you for this....I really very much appreciate it! Seems the most complicated tutorial/walkthrough than most others (simple magiskhide and/or modifying certain files...), but it seems most promising as well.
I just wanted to ask (specifically a person who has experience with this successfully and is possibly continuing doing this) if you do the monthly updates and if it resets everything and you have to edit a database file via SQL editor every single time? I, myself, imagine that if you do a Full Factory flash-all update, it would overwrite either the permissions and/or the .db file, but I wanted to confirm with someone else as I've already updated to the August security patch...
Thank you again for posting your response here and I look forward to seeing my GPay work in the stores!
Click to expand...
Click to collapse
I have not done any sql editing. I deleted the db file then made it read only on next reboot. When taking the monthly Q beta update, via flash-all without -w, I redid the fingerprint with magisk props module then added my card back in. I do get an error every once in awhile due to the db being only read only but Pay works.
I have no idea what will need to be done when Q is finalized.
Sent from my Pixel 2 XL using Tapatalk
simplepinoi177 said:
alershka said:
Followed this process. Uses a few modules and I have had no issues since.
https://forum.xda-developers.com/showthread.php?p=79915863
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thank you for this....I really very much appreciate it! Seems the most complicated tutorial/walkthrough than most others (simple magiskhide and/or modifying certain files...), but it seems most promising as well.
I just wanted to ask (specifically a person who has experience with this successfully and is possibly continuing doing this) if you do the monthly updates and if it resets everything and you have to edit a database file via SQL editor every single time? I, myself, imagine that if you do a Full Factory flash-all update, it would overwrite either the permissions and/or the .db file, but I wanted to confirm with someone else as I've already updated to the August security patch...
Thank you again for posting your response here and I look forward to seeing my GPay work in the stores!
Click to expand...
Click to collapse
I just wanted to come back here and give my thanks to this thread and specifically to alershka!
I was able to finally try and pay for something at a store front and was so happy (and shocked tbh) when it worked flawlessly! As I've mentioned before, I've tried many other methods and "workarounds" ranging from simple to complicated, and I have been successful from searching, finding, installing the app up to running it successfully without errors or blocks and even successfully loading credit cards and verification for "in-store purchases"! But, in the end, I would be able to get that far, but still not be able to make a purchase as the app would come out with an error; which was weird because the NFC would still detect and vibrate so the signal and data would exchange, but would be stopped on the app end...I actually ended up giving up using the app/feature for the last couple of months with the compromise of keeping rooted.
Now I can breathe easy and relax with the knowledge that this is an open option available to me when I need/want it.
Now, the only thing I'm wondering/curious about is, as I update by using the Full Factory image and the flash-all way, that this usually formats and resets system files and permissions and if I'm going to have to re-do this workaround method every single time; although, if that's the way it has to be, I'll be glad and more than willing to if it saves me this...
but GOD! sifting through the SQL trying to find "attest" and changing things to "0" is sooooo damn tedious...!!!
Anyways....this is so great and after a considerable amount of time I'm super happy for this!
simplepinoi177 said:
I just wanted to come back here and give my thanks to this thread and specifically to alershka!
I was able to finally try and pay for something at a store front and was so happy (and shocked tbh) when it worked flawlessly! As I've mentioned before, I've tried many other methods and "workarounds" ranging from simple to complicated, and I have been successful from searching, finding, installing the app up to running it successfully without errors or blocks and even successfully loading credit cards and verification for "in-store purchases"! But, in the end, I would be able to get that far, but still not be able to make a purchase as the app would come out with an error; which was weird because the NFC would still detect and vibrate so the signal and data would exchange, but would be stopped on the app end...I actually ended up giving up using the app/feature for the last couple of months with the compromise of keeping rooted.
Now I can breathe easy and relax with the knowledge that this is an open option available to me when I need/want it.
Now, the only thing I'm wondering/curious about is, as I update by using the Full Factory image and the flash-all way, that this usually formats and resets system files and permissions and if I'm going to have to re-do this workaround method every single time; although, if that's the way it has to be, I'll be glad and more than willing to if it saves me this...
but GOD! sifting through the SQL trying to find "attest" and changing things to "0" is sooooo damn tedious...!!!
Anyways....this is so great and after a considerable amount of time I'm super happy for this!
Click to expand...
Click to collapse
If you do wipe, you will have to redo this each time. I have flashed but removed the -w from the bat file and did not have to do anything other than reflash Magisk.
Sent from my Pixel 2 XL using Tapatalk
alershka said:
If you do wipe, you will have to redo this each time. I have flashed but removed the -w from the bat file and did not have to do anything other than reflash Magisk.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thank you (again)!!! I'll keep that in mind...I mean, it was very tedious when I edited the SQL....
Also, it seems you meant "you will [not] have to redo this each time; based off of your second sentence...
I was able to successfully use it at another credit card reader today! And it began because of you! So thank you again!
simplepinoi177 said:
Thank you (again)!!! I'll keep that in mind...I mean, it was very tedious when I edited the SQL....
Also, it seems you meant "you will [not] have to redo this each time; based off of your second sentence...
I was able to successfully use it at another credit card reader today! And it began because of you! So thank you again!
Click to expand...
Click to collapse
Either he means that or he's using sql modules like I am.
So it seems that you did it the long way lol, the modules have replaced the long process of editing the database...
Windroid-user said:
Either he means that or he's using sql modules like I am.
So it seems that you did it the long way lol, the modules have replaced the long process of editing the database...
Click to expand...
Click to collapse
Thanks for this! I hadn't read all of the thread and wasn't aware of the module that automates all of it by @73sydney! I'll consider utilizing it! Especially if it survives a Full Factory update and doing it manually wouldn't...
But, in the end, I don't mind that I did it manually; learned a considerable amount and, for all I know, it may be better or would work best if the module wouldn't work perfectly (maybe)...
simplepinoi177 said:
Thanks for this! I hadn't read all of the thread and wasn't aware of the module that automates all of it by @73sydney! I'll consider utilizing it! Especially if it survives a Full Factory update and doing it manually wouldn't...
But, in the end, I don't mind that I did it manually; learned a considerable amount and, for all I know, it may be better or would work best if the module wouldn't work perfectly (maybe)...
Click to expand...
Click to collapse
Sadly the modules wont be accepted into the Magisk Repo as they "dont do enough" (i.e. theyre considered no more than doing system property edits, and do not do enough to warrant adding to the repo, i did try), so theyre not easy to find unless you do read the whole thread, someone mentions them, or you see the link in my signature ...
I have never had so many issues with updating a phone with Magisk before. Today is the 2nd time I lost all my data trying to update. I feel like Magisk isn't worth the hassle anymore. It is frustrating how anti-root google is becoming.
Anyone else share the same opinion?
mkhcb said:
I have never had so many issues with updating a phone with Magisk before. Today is the 2nd time I lost all my data trying to update. I feel like Magisk isn't worth the hassle anymore. It is frustrating how anti-root google is becoming.
Anyone else share the same opinion?
Click to expand...
Click to collapse
Were you running a custom kernel and you tried to update to March? Did you get the phone is corrupt and it wouldn't boot screen? If that ever happens again, you don't have to wipe, Just go on the Android flashing tool uncheck everything flash and you'll be good to go again. At least it's worked for me every time so far.
mac796 said:
Were you running a custom kernel and you tried to update to March? Did you get the phone is corrupt and it wouldn't boot screen? If that ever happens again, you don't have to wipe, Just go on the Android flashing tool uncheck everything flash and you'll be good to go again. At least it's worked for me every time so far.
Click to expand...
Click to collapse
No custom Kernel, it came to a point where the only screen I was given was Android Recovery screen.
mkhcb said:
No custom Kernel, it came to a point where the only screen I was given was Android Recovery screen.
Click to expand...
Click to collapse
I ended up going to stable magisk
mkhcb said:
I have never had so many issues with updating a phone with Magisk before. Today is the 2nd time I lost all my data trying to update. I feel like Magisk isn't worth the hassle anymore. It is frustrating how anti-root google is becoming.
Anyone else share the same opinion?
Click to expand...
Click to collapse
I disagree with you...
Coming from the OnePlus 6T, and previous phones you can't really beat just pulling the boot.img from the factory image, patching it with magisk, then fastboot boot that img then install directly in the magisk app. It's actually that simple. Really is that black and white to be up front about it.
That's how I have been doing it for a while now...and...no problems for me! But this IS JUST ME.
mkhcb said:
I have never had so many issues with updating a phone with Magisk before. Today is the 2nd time I lost all my data trying to update. I feel like Magisk isn't worth the hassle anymore. It is frustrating how anti-root google is becoming.
Anyone else share the same opinion?
Click to expand...
Click to collapse
No. It really comes down to reading instructions and knowing what you're supposed to do when it comes to rooting. I can't tell you how many times I read folks spewing instructions that are out of date or they're patching the wrong files for their device that inevitably cause a problem.
I have not had any issues with root since the P6 came out. I have followed directions exactly as they've been written and I've been fine.
mkhcb said:
I have never had so many issues with updating a phone with Magisk before. Today is the 2nd time I lost all my data trying to update. I feel like Magisk isn't worth the hassle anymore. It is frustrating how anti-root google is becoming.
Anyone else share the same opinion?
Click to expand...
Click to collapse
Did you update magisk and then faced a bootloop?
That was a bug/is a bug introduced with the latest magisk update (monday), Magisk kind of "lost" the ability to handle a certain amount of modules/certain modules. We are all waiting for a fix. The temporary solution was/is to press down Lower Volume rocker when the Google logo appeared when booting, that way you activate safe mode and all Magisk modules get deactivated. Discord says 4 modules are max right now, some say it's "just" certain audio modules that are incompatible.
I wouldn't say it's become a pain but you really need to "do your homework" and make sure to read before attempting stuff. Same old, same old I'd say.
If you're unsure, just ask. There's plenty of people here who are willing to help out.
I was on regular A12 and tried to update from the app. The device rebooted and didn't appear to be rooted (I know that ryhmed) tried to direct install but got an error, can not remember the error.
Then I decided to update to the A13 DP2 beta and used canary magisk , updating via flashtool and fastboot flashing the patched image and voila! Couldn't be happier.
Seems like people have had some issues lately
I don't know about harder, but maybe more haphazard. February update I did the uninstall magisk method and it worked as described. Did it again for March and this time it took me three tries to get the phone to boot and at that point I lost root. Had to download the image from Google, extract boot, patch it and flash it. Not the end of the world but still no idea what happened.
There was some glitchyness at the beginning with the vbmeta nonsense, but that's all sorted out now. The tools available are so simple to use now that its hard to imagine that anyone could have any trouble with it.
FWIW: for privacy/security reasons, I run GrapheneOS. It would normally do its own update procedures, but when you need root (I need for conducting proper backups since the built-in misses a lot), it freaks out with the unmatched boot.img. The update solution then is to download the full "factory" update package, extract the boot.img, patch it with magisk, edit the "flash-all.sh" script to remove the "-w", run the flash-all.sh, then finally fastboot flash the magisk-patched boot.img.
Ghisy said:
I wouldn't say it's become a pain but you really need to "do your homework" and make sure to read before attempting stuff. Same old, same old I'd say.
If you're unsure, just ask. There's plenty of people here who are willing to help out.
Click to expand...
Click to collapse
^^^This 100%
mkhcb said:
I have never had so many issues with updating a phone with Magisk before. Today is the 2nd time I lost all my data trying to update. I feel like Magisk isn't worth the hassle anymore. It is frustrating how anti-root google is becoming.
Anyone else share the same opinion?
Click to expand...
Click to collapse
While there are many ways to skin this cat, I follow the step by step instructions in my sig every update, and haven't had an issue yet.
I will admit that rooting is loosing it's allure for me as it seems cust Rom development on the phones I prefer is waning (remember the day when every device had a dozen cust Roms to choose from). That coupled with I'm no longer the guy who tries to squeeze an extra 30 min of battery life, who over/underclocked cpu's and gpu's to get a 100 pt higher benchmark score.
Root is something I still do because I like having the OPTION of customizing beyond a cust kernel and some "root required" apps, and jumping through a few hoops to make magisk work is worth it IMHO.
Az Biker said:
Root is something I still do because I like having the OPTION of customizing beyond a cust kernel and some "root required" apps, and jumping through a few hoops to make magisk work is worth it IMHO.
Click to expand...
Click to collapse
This 100% as well!!
The stock Google ROM is perfectly fine with some tweaks!
96carboard said:
There was some glitchyness at the beginning with the vbmeta nonsense, but that's all sorted out now. The tools available are so simple to use now that its hard to imagine that anyone could have any trouble with it.
FWIW: for privacy/security reasons, I run GrapheneOS. It would normally do its own update procedures, but when you need root (I need for conducting proper backups since the built-in misses a lot), it freaks out with the unmatched boot.img. The update solution then is to download the full "factory" update package, extract the boot.img, patch it with magisk, edit the "flash-all.sh" script to remove the "-w", run the flash-all.sh, then finally fastboot flash the magisk-patched boot.img.
Click to expand...
Click to collapse
Root renders half of the purpose of grapheneos moot though... It's "security hardened". Hand a rooted "security hardened" android phone to anyone who can watch a YouTube video and has a computer that has a USB port or wifi and they could be dumping your system files in in a matter of minutes.
What sort of privacy do you imagine you gain? Are you under the assumption that Googleplayservices is the only method by which your traffic can be singled out of the background internet swarms? Hopefully you're not replying on it to not be physically tracked. Or worse, trust it to go dark and do dirt with.
I'm asking because because I generally don't understand the motivations of users such as yourself. Using a flagship device, attempting to de-google/brand it, and then openly say it's for X privacy or X security usecase. It's simply not true. To me it's like someone buying a Porsche, throwing Ford stickers on it's and saying it's because they get better traction.
erktheerk said:
Root renders half of the purpose of grapheneos moot though... It's "security hardened". Hand a rooted "security hardened" android phone to anyone who can watch a YouTube video and has a computer that has a USB port or wifi and they could be dumping your system files in in a matter of minutes.
Click to expand...
Click to collapse
Maybe in the hands of an incompetent, but no, you can't just "walk in". Said compromising individual would have to somehow unlock the device in order to authorize the USB debugging session or whatever type of compromise they're attempting.
erktheerk said:
What sort of privacy do you imagine you gain? Are you under the assumption that Googleplayservices is the only method by which your traffic can be singled out of the background internet swarms? Hopefully you're not replying on it to not be physically tracked. Or worse, trust it to go dark and do dirt with.
Click to expand...
Click to collapse
You are mistaking absolute security for mitigating known and easy to close holes. Bad mistake, which will always make you look like a fool.
erktheerk said:
I'm asking because because I generally don't understand the motivations of users such as yourself. Using a flagship device, attempting to de-google/brand it, and then openly say it's for X privacy or X security usecase. It's simply not true. To me it's like someone buying a Porsche, throwing Ford stickers on it's and saying it's because they get better traction.
Click to expand...
Click to collapse
While root control of a device can provide a high degree of access to a system, it only does so in the hands of an incompetent. Every single server running connected with the public internet has a root account. If it was so terrifyingly and absolutely dangerous, it would be pretty obvious. But the reality is that those systems are administered, in large part, by competent system administrators, who know how to safely make use of the increased access without guaranteeing that some hostile entity will walk in and take control.
Conversely, consumer electronics are assumed to be placed in the hands of nitwits who will install applications that promise to deliver jiggling lady parts that are published in hostile countries, and even worse, will hit the "ok" button when a root authorization prompt pops up. Yes, consumers, by and large, are a security DISASTER waiting to happen.
So don't you dare make the claim that root access is a violation of sane security measures. There is nothing wrong with root, as long as it is used responsibly by someone competent to make use of it.
No, you misunderstand me. I've been rooting android since day one. Literally. Rooted by Dream/G1 running Cupcake with telnet on release day in 2008. I have 3 Pixel in front of me right now. One with CalyxOS, and one with Graphene. Those are for a paying customer who values their privacy, and not walking around with a crippled 'hardened device". So no root. The other is by test device I really want to Kali running on at some point.
I'll just let the lead dev/owner of GrapheneOS say the rest, I'm not debating what you want/like, I only elaborated on you want it sounds like to others.
96carboard said:
Maybe in the hands of an incompetent, but no, you can't just "walk in". Said compromising individual would have to somehow unlock the device in order to authorize the USB debugging session or whatever type of compromise they're attempting.
You are mistaking absolute security for mitigating known and easy to close holes. Bad mistake, which will always make you look like a fool.
While root control of a device can provide a high degree of access to a system, it only does so in the hands of an incompetent. Every single server running connected with the public internet has a root account. If it was so terrifyingly and absolutely dangerous, it would be pretty obvious. But the reality is that those systems are administered, in large part, by competent system administrators, who know how to safely make use of the increased access without guaranteeing that some hostile entity will walk in and take control.
Conversely, consumer electronics are assumed to be placed in the hands of nitwits who will install applications that promise to deliver jiggling lady parts that are published in hostile countries, and even worse, will hit the "ok" button when a root authorization prompt pops up. Yes, consumers, by and large, are a security DISASTER waiting to happen.
So don't you dare make the claim that root access is a violation of sane security measures. There is nothing wrong with root, as long as it is used responsibly by someone competent to make use of it.
Click to expand...
Click to collapse
No, you misunderstand me. I've been rooting android since day one. Literally. Rooted by Dream/G1 running Cupcake with telnet on release day in 2008. I have 3 Pixel in front of me right now. One with CalyxOS, and one with Graphene. Those are for a paying customer who values their privacy, and not walking around with a crippled 'hardened device". So no root. The other is by test device I really want to Kali running on at some point.
I'll just let the lead dev/owner of GrapheneOS say the rest, I'm not debating what you want/like, I only elaborated on you want it sounds like to others.
erktheerk said:
No, you misunderstand me. I've been rooting android since day one. Literally. Rooted by Dream/G1 running Cupcake with telnet on release day in 2008. I have 3 Pixel in front of me right now. One with CalyxOS, and one with Graphene. Those are for a paying customer who values their privacy, and not walking around with a crippled 'hardened device". So no root. The other is by test device I really want to Kali running on at some point.
I'll just let the lead dev/owner of GrapheneOS say the rest, I'm not debating what you want/like, I only elaborated on you want it sounds like to others.
Click to expand...
Click to collapse
There's nothing "crippled" about it. Its just AOSP with some hardening.
Yeah briefly looking at that link, their explanations are irrelevant. The bottom line is that they don't want morons who don't know what they're doing modifying the crap out of it, and either (a) having to be supported, or failing that (b) making the project look bad.
Nothing about it makes it "less customizable" than any other AOSP. Magisk/root or anything else installs on it and works just like it does on any other AOSP distribution. It just doesn't have all the broken junk thrown in willy nilly without taking a careful look at the implementation first, i.e., is it actually a *useful* feature, and can it be implemented in a secure manner? As a clear example, take a look at the call recording feature request; https://github.com/GrapheneOS/os-issue-tracker/issues/868 -- clearly a useful feature. The "lineageos" implementation has been brought forward, not as something to pull straight in, but as a point of study and/or somewhere to start building a good implementation -- their implementation is unsatisfactory in terms of security and maintainability.
Rooting this device is so easy compared to attempting to root a z fold 3 or any other recent Samsung flagship