Related
does the nook colors made now have a locked bootloader? or was it just the nook tablets that have that locked bootloader.
Im kind of confused cause I think i read that Older nook colors are not locked, but the newer nook colors have a locked bootloader
This would be the first time i have heard about this... I am going to say it is only the tablet; the lock is partly the hardware, wjich i dont believe has changed in the nook color..
thanks dude, im sure some people are confusing stuff about the nook "color" tablet having a locked bootloader. so yeah, definitely. thanks for the heads up, I thought the nook colors didnt have the bootloader lock on it.
You can't exactly lock a boot loader with an OTA update. Only the Nook Tablet has a locked bootloader.
Sent from my NookColor using Tapatalk
koopakid08 said:
You can't exactly lock a boot loader with an OTA update. Only the Nook Tablet has a locked bootloader.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I am very new to Android and Linux terms and operations. Would you be able to point me to a link that discusses what a bootloader actually is? Thank you.
gsutton said:
I am very new to Android and Linux terms and operations. Would you be able to point me to a link that discusses what a bootloader actually is? Thank you.
Click to expand...
Click to collapse
I just did a quick Google search:
http://www.tested.com/news/know-your-android-bootloaderwhat-it-is-and-why-it-matters/1879/
http://androidcommunity.com/android-101-bootloaders-20110527/
Sent from my NookColor using Tapatalk
Since the NC does not have a locked bootloader perhaps someone can close this thread?
gsutton said:
Would you be able to point me to a link that discusses what a bootloader actually is? Thank you.
Click to expand...
Click to collapse
No problem. A bootloader is the very first bit of code that is executed when you turn the device one, aka. if you press the power switch.
It's a static piece of code, which usually resides on a ROM chip whose sole purpose is to execute the next stage bootloader, usually on a EEPROM / Flash which in turn boots the operating system itself...
When we talk about a locked bootloader it means that this piece of static, unchangeable code, executes a check on the next-stage bootloader for validicity, usually a checksum or signature, before executing it...
Which means, that selfmade unsigned next-stage bootloader code like ours will not boot, because it doesn't pass the checks on the static first stage bootloader.
I hope this made sense...
Is it possible that the upcomming 1.4 update could put the same NT bootloader in to the NC that prevents custom rom usage?
Nope. The 1st Stage Bootloader usually is on a ROM chip, means it can't get erased / rewritten.
The only way to add a new 1st Stage Bootloader would be by replacing that ROM chip, which requires a hardware change.
Imbroglio said:
Is it possible that the upcomming 1.4 update could put the same NT bootloader in to the NC that prevents custom rom usage?
Click to expand...
Click to collapse
Did you actually read this thread? The answer was/is/always will be: NO
MrColdbird said:
Nope. The 1st Stage Bootloader usually is on a ROM chip, means it can't get erased / rewritten.
The only way to add a new 1st Stage Bootloader would be by replacing that ROM chip, which requires a hardware change.
Click to expand...
Click to collapse
Sort of, but no. The OMAP has a hardware pin which determines boot priority. The bootloader, recovery, etc, are all on the flash. MLO, uImage, etc.
I understood the question more as whether NEW Nook Color units would be locked. My two older units are safe, but if I order a NEW unit, might it be locked down?
(As a guy who nearly got burned putting alternate firmware on the Linksys WRT-54 routers, I think this is a valid concern. Nothing keeps a manufacturer from changing the innards of a product as they see fit, even if the outward appearance and description stays the same.)
Not likely. They probably are not manufacturing more Nook Colors, (don't know this for a fact), and you can bet they're not gonna crack open the existing ones and replace the boards. What is being sold now is most likely a very large back stock.
starbuckk said:
Not likely. They probably are not manufacturing more Nook Colors, (don't know this for a fact), and you can bet they're not gonna crack open the existing ones and replace the boards. What is being sold now is most likely a very large back stock.
Click to expand...
Click to collapse
I suspect they will continue to manufacture Nook Colors as long as there is a demand. It is costing them less to manufacture now which is one reason for the price decrease. And with the 1.4 update they are a very viable contender to the Kindle Fire.
I still see "Amazon" on boot, did I completely "FlashFire" my 5th gen?
The tutorial here seems to use TWRP https://www.youtube.com/watch?v=4dwguHoxTvo&feature=youtu.be
I'm on CM12.1 now, but I'm not sure if I should try to further push Amazon off of my tablet, as it still gives me "Amazon" on boot. My other concern here is privacy. Could Amazon do some telemetry through CM12.1 somehow since the bootloader still seems locked?
bobbob1016 said:
The tutorial here seems to use TWRP https://www.youtube.com/watch?v=4dwguHoxTvo&feature=youtu.be
I'm on CM12.1 now, but I'm not sure if I should try to further push Amazon off of my tablet, as it still gives me "Amazon" on boot.
Click to expand...
Click to collapse
TL;DR:
I still see "Amazon" on boot, did I completely "FlashFire" my 5th gen?
Click to expand...
Click to collapse
Yes.
My other concern here is privacy. Could Amazon do some telemetry through CM12.1 somehow since the bootloader still seems locked?
Click to expand...
Click to collapse
No.
The 'fire' logo has been replaced by the CM logo, but the initial 'amazon' logo remains. You can see it here in the video you posted:
https://www.youtube.com/watch?v=4dwguHoxTvo&t=11m
If you are concerned about Amazon privacy issues then you should avoid installing any of the Amazon apps on CM12.1:
https://play.google.com/store/apps/developer?id=Amazon+Mobile+LLC
m00head said:
TL;DR:
Yes.
No.
The 'fire' logo has been replaced by the CM logo, but the initial 'amazon' logo remains. You can see it here in the video you posted:
https://www.youtube.com/watch?v=4dwguHoxTvo&t=11m
If you are concerned about Amazon privacy issues then you should avoid installing any of the Amazon apps on CM12.1:
https://play.google.com/store/apps/developer?id=Amazon+Mobile+LLC
Click to expand...
Click to collapse
Stopped once I realized the video did TWRP, so didn't get to 11m.
Didn't install any Amazon stuff, nor do I plan to. Only CM, and FDroid. Was kinda concerned with an Amazon Kernel though. Thanks for the quick reply!
bobbob1016 said:
Stopped once I realized the video did TWRP, so didn't get to 11m.
Didn't install any Amazon stuff, nor do I plan to. Only CM, and FDroid. Was kinda concerned with an Amazon Kernel though. Thanks for the quick reply!
Click to expand...
Click to collapse
Amazon publish the source code (including the kernel) for all their tablet devices here:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720
bobbob1016 said:
Stopped once I realized the video did TWRP, so didn't get to 11m.
Didn't install any Amazon stuff, nor do I plan to. Only CM, and FDroid. Was kinda concerned with an Amazon Kernel though. Thanks for the quick reply!
Click to expand...
Click to collapse
Amazon logo is the bootloader which can't be replaced on a locked device (nor would you want to).
the amazon logo is a low-level animation contained in the bootloader. it can be replaced, but it's very tricky and not something I'd recommend. No Amazon isn't running telemetry or anything else on you at that level; but yeah, if you're privacy concerned don't reinstall kindle reader, amazon app store, or other apps like that. I do have them and I don't have any problem. Amazon has not sent me any nasty letters or remotely bricked me for rooting my fire. All it does is void the warranty.
eoraptor said:
Amazon has not sent me any nasty letters or remotely bricked me for rooting my fire. All it does is void the warranty.
Click to expand...
Click to collapse
Unless recently changed Amazon's EULA does not address rooting. Reps typically offer one time, no questions asked courtesy exchanges on rooted devices gone bad. The latter may simply represent a customer service initiative vs formal policy.
Hi all, appreciate best practice is always to read posted guides but I'm getting kinda old and too many threads are only relevant at particular points in time when the 5th Gen Fire was newer. So basically I'm lost in conflicting info on the guides and need some direction.
Starting point is i) I've got 'basic' experience of rooting and flashing roms, so my PC has got ADB drivers etc. ii) I have a stock OS 5.4.0.0 5th Gen Fire which is my elderly mothers and the intention is to get the crap OS removed and make it a simple Nexus 7'like device.
Can somebody please give me some step-by-step advice. I'm at the point where the device is developer enabled and ABD enabled. But the guides I've seen are all based on old OS's so I fear the whatever I try next will just brick the unit.
Thx in advance
As of now, 5.3.2.1 - 5.4.0.0 can not be rooted, much less have the bootloader unlocked to install a custom ROM.
aww bummer
OK second question : How should I treat the term "As of now"? Do you think there is any likelihood of a 5.4.0.0 root solution happening soon? i.e. weeks or months?
If its not gonna be a while, then I might just install the non-root google-play stuff and just shift the bloaty stuff out of sight if I can.
ebod said:
aww bummer
OK second question : How should I treat the term "As of now"? Do you think there is any likelihood of a 5.4.0.0 root solution happening soon? i.e. weeks or months?
If its not gonna be a while, then I might just install the non-root google-play stuff and just shift the bloaty stuff out of sight if I can.
Click to expand...
Click to collapse
EDIT: The usual warning: I am not responsible for any damage done to your device. If using ANY of these guides, you're doing so at your own risk.
That's about your only option at the moment. You can use the guide here, which will install the appropriate google services needed. You can then use this guide to manually 'uninstall' system/Amazon applications (you aren't really uninstalling them, just disabling them). Or use the automatic tool here, which will uninstall a significant number of the Amazon 'bloatware' and install the Google services and a few other Google related apps.
I CANNOT STRESS THIS NOTE ENOUGH: Whether you uninstall apps manually or automatically, please be aware you have to replace the Amazon apps BEFORE you uninstall them. For example, if you want to use contacts, you should install the necessary Google Contact APKs, open 'Contacts' then uninstall Amazon contacts. DO NOT UNINSTALL the Amazon Contact Storage APK or no contact applications will function properly, if at all. There is a guide here where you can install Google Contacts and get a fun little surprise as a result of doing so.
A factory reset will bring back all system apps you uninstall whether you uninstall them manually or automatically. So if anything stops working or you uninstall something that broke something else, factory resetting will fix the tablet, but you'll have to start over.
If you want to use a custom launcher like Nova Launcher, you can read this post which will describe how to do so. In this post I explain how to disable Fire Launcher without breaking the home button. Please read the WHOLE post, including the very bottom where there's a link that describes a 'fix' for the recent apps button (square button) which has a fit when you uninstall Fire Launcher (even on rooted devices). Just tap on 'hide Fire Launcher BEFORE' at the bottom which will take you to a page where you can activate widgets. Read the very bottom and it will tell you how to 'fix' the recent apps button. When you swipe closed apps using the recent apps button, swiping the last one will kick you to the lock screen or black you out for a moment. The fix is kinda cheesy, but it is a fix. I use it on my HD 8.
In this post I describe what Amazon apps I did NOT uninstall. Note this list of apps will differ slightly from the ones installed on the HD 7, but not by very much. This list MIGHT allow you to use Gmail (which doesn't work on any tablet model) and a few other apps.
Very soon, I plan to make a thread with a detailed tutorial on how to do all of this, so it's in one single spot for everyone to find.
Jake1702_ said:
As of now, 5.3.2.1 - 5.4.0.0 can not be rooted, much less have the bootloader unlocked to install a custom ROM.
Click to expand...
Click to collapse
For awareness/clarity: root and SuperSU (no other root manager) are the only prerequisites for installing a custom ROM on this device via FlashFire. The bootloader does not need to be unlocked.
Davey126 said:
For awareness/clarity: root and SuperSU (no other root manager) are the only prerequisites for installing a custom ROM on this device via FlashFire. The bootloader does not need to be unlocked.
Click to expand...
Click to collapse
Thanks Davey, yeah I'm not ultimately looking for a rooted device, I just want a clean Nexus'like rom with no bloated crap on it. As a plan-B I will follow the other guide notes that DragonFire kindly provided. But primarily if you are still staying I can get Flashfire to install a custom Nexus rom, then please can you guide me to the appropriate instructions to make Flashfire come to life.
I have Flashfire installed...but it just warns there are no permissions etc.
Thanks
ebod said:
Thanks Davey, yeah I'm not ultimately looking for a rooted device, I just want a clean Nexus'like rom with no bloated crap on it. As a plan-B I will follow the other guide notes that DragonFire kindly provided. But primarily if you are still staying I can get Flashfire to install a custom Nexus rom, then please can you guide me to the appropriate instructions to make Flashfire come to life.
I have Flashfire installed...but it just warns there are no permissions etc.
Thanks
Click to expand...
Click to collapse
A custom ROM (ie: Nexus) can not be installed on this device without root. I do not foresee that happening anytime soon with the so you're stuck with FireOS for a bit. It's not a bad skin once you get used to it.
@DragonFire1024 provided a nice summary of the available tweaks and associated caveats. I suggest going slow; start with the Google Play Store and some light visual customizations. Save the all-or-nothing 'debloat script' until have have a better idea of what to keep.
Most importantly, enjoy your new device and don't fret over what could have been.
This list MIGHT allow you to use Gmail (which doesn't work on any tablet model) and a few other apps.
Click to expand...
Click to collapse
Ummm... Gmail works fine on my Fire.
Davey126 said:
For awareness/clarity: root and SuperSU (no other root manager) are the only prerequisites for installing a custom ROM on this device via FlashFire. The bootloader does not need to be unlocked.
Click to expand...
Click to collapse
I did not know that. If that's the case, as soon as root is obtainable I'm installing the Fire Nexus ROM.
Jake1702_ said:
Ummm... Gmail works fine on my Fire.
Click to expand...
Click to collapse
You're lucky then. Many users have had issues with Gmail either force closing or not working at all. Hope the rest was somewhat helpful.
---------- Post added at 05:48 PM ---------- Previous post was at 05:47 PM ----------
Jake1702_ said:
Ummm... Gmail works fine on my Fire.
I did not know that. If that's the case, as soon as root is obtainable I'm installing the Fire Nexus ROM.
Click to expand...
Click to collapse
*IF* it becomes available. I've had my tablets almost a year, maybe a months or so under one. That's how long I've been waiting. Some have been waiting longer.
Jake1702_ said:
Ummm... Gmail works fine on my Fire.
Click to expand...
Click to collapse
Initially and for many months after the Gmail app worked fine on 5th-7th gen devices with Google Play Services/Store installed. The app started crashing on launch following a silent update (lasted about 2 months) then started working again a few weeks ago.
Davey126 said:
Jake1702_ said:
Ummm... Gmail works fine on my Fire.
Initially (and for many months after) the Gmail app worked fine on 5th-7th gen devices with Google Play Services/Store installed. The app started crashing on launch following a silent update (lasted about 2 months) then started working again a few weeks ago.
Click to expand...
Click to collapse
I read somewhere where quite a few people had put a bug report in or something to that effect. A few days later there was an update to Gmail. That's about the time I installed it and it worked perfectly for me. I'm willing to bet Google did something that that made it possible to use again. Did Amazon do something to block is from using it? In my opinion, not likely. But what caused it? Not a clue. There is some speculation it had to do to with a permission, but that's only speculation. This is something we'll likely never get the answer to.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Jake1702_ said:
... as soon as root is obtainable I'm installing the Fire Nexus ROM.
Click to expand...
Click to collapse
Don't get your hopes up. There's a reason securing root on Amazon and other manufacturer devices has become more difficult over the past 12-18 months. While I appreciate the euphemistic optimism shown by some the tightened security and legacy code cleanup initiated by Google is actually a good thing for the general Android user community. Of course, XDAers hate it (spare me the sermon on someone controlling *your* device) but they don't represent the much larger community that Amazon and other market driven companies are targeting. Business/capatolism 101.
Davey126 said:
Initially and for many months after the Gmail app worked fine on 5th-7th gen devices with Google Play Services/Store installed. The app started crashing on launch following a silent update (lasted about 2 months) then started working again a few weeks ago.
Click to expand...
Click to collapse
Might just have been the perfect period of time during when I had mine sitting and not being used. Guess I'm just lucky.
Davey126 said:
Don't get your hopes up. There's a reason securing root on Amazon and other manufacturer devices has become more difficult over the past 12-18 months. While I appreciate the euphemistic optimism shown by some the tightened security and legacy code cleanup initiated by Google is actually a good thing for the general Android user community. Of course, XDAers hate it (spare me the sermon on someone controlling *your* device) but they don't represent the much larger community that Amazon and other market driven companies are targeting. Business/capatolism 101.
Click to expand...
Click to collapse
It is definitely possible, just not enough people spending time on this device, they are all focused on more popular brands/devices.
Jake1702_ said:
Might just have been the perfect period of time during when I had mine sitting and not being used. Guess I'm just lucky.
It is definitely possible, just not enough people spending time on this device, they are all focused on more popular brands/devices.
Click to expand...
Click to collapse
This I will actually agree with. But to be honest, I really thought we'd have a good chance after Prime Day. I really thought we'd have gotten it then, but I still have hopes.
That being said, the tricks and hacks we've discovered over the last few months are pretty amazing. The method of 'uninstalling' I mentioned a few posts ago, was never intended nor expected to work on these tablets. It had sat on XDA for a couple days before I literally said out loud: "oh what the hell. I can't break anything." So gave it a shot and was incredibly surprised to see it really did disable Amazon Video.
With the tricks and hacks I also mentioned a few posts back, really does go a long way in terms of a custom ROM. Aside from the technical aspects and apps, in my opinion it's pretty much a custom systemless ROM. Though some may disagree with me very much.
Feel free to ask any question you like. We'll do our best to help.
DragonFire1024 said:
This I will actually agree with. But to be honest, I really thought we'd have a good chance after Prime Day. I really thought we'd have gotten it then, but I still have hopes.
That being said, the tricks and hacks we've discovered over the last few months are pretty amazing. The method of 'uninstalling' I mentioned a few posts ago, was never intended nor expected to work on these tablets. It had sat on XDA for a couple days before I literally said out loud: "oh what the hell. I can't break anything." So gave it a shot and was incredibly surprised to see it really did disable Amazon Video.
With the tricks and hacks I also mentioned a few posts back, really does go a long way in terms of a custom ROM. Aside from the technical aspects and apps, in my opinion it's pretty much a custom systemless ROM. Though some may disagree with me very much.
Feel free to ask any question you like. We'll do our best to help.
Click to expand...
Click to collapse
Funny how for months now this device still hasn't been rooted, yet a few days after the release of the Samsung Galaxy S8, it was already rooted. Simply, those devices have much more people willing to take time to find exploits for, whereas the Fire does not. It's a shame really.
Sent from my KFFOWI using Tapatalk
Jake1702_ said:
Funny how for months now this device still hasn't been rooted, yet a few days after the release of the Samsung Galaxy S8, it was already rooted. Simply, those devices have much more people willing to take time to find exploits for, whereas the Fire does not. It's a shame really.
Click to expand...
Click to collapse
There just may not be any at the moment. Amazon has done a lot to this OS, so much so, I've seen posts where users don't even consider it an Android base anymore. Depending on what you read, I've seen other sites where some say its too butchered.
Also keep in mind when an exploit is found, some have been around for a very long time. So one may exist, but no one has either found it yet so no method exists or as you say, may not care enough to take the time to make a method. Every Android device is different. The OS is customized and programed to a manufacturers liking who also add their own customization, then is passed off to a service provider who further customizes it. In that period exploits are patched or simply don't work because what's exploited in certain devices, may not exist in other devices. The list and possibilities really could go on.
DragonFire1024 said:
There just may not be any at the moment. Amazon has done a lot to this OS, so much so, I've seen posts where users don't even consider it an Android base anymore. Depending on what you read, I've seen other sites where some say its too butchered.
Also keep in mind when an exploit is found, some have been around for a very long time. So one may exist, but no one has either found it yet so no method exists or as you say, may not care enough to take the time to make a method. Every Android device is different. The OS is customized and programed to a manufacturers liking who also add their own customization, then is passed off to a service provider who further customizes it. In that period exploits are patched or simply don't work because what's exploited in certain devices, may not exist in other devices. The list and possibilities really could go on.
Click to expand...
Click to collapse
I wonder if it would be possible "break" the bootloader, so-to-speak, to a point where it "works" but is flawed, allowing the installation of a custom ROM.
Jake1702_ said:
I wonder if it would be possible "break" the bootloader, so-to-speak, to a point where it "works" but is flawed, allowing the installation of a custom ROM.
Click to expand...
Click to collapse
Not likely. I have a list of things to try on my head. Some simple, some outrageous. Truth is this HD 8 has been through hell. I've reset it more times than I can count. I've nearly disected it and to be honest I'm absolutely amazed I haven't broken it yet. So I'm giving her a break from that right now.
With that said, I have an HD 7 that's rooted. I have an idea to try some things using it, that could work on non rooted 7 and up tablets, that would be totally systemless that could open up the possibilities to some things. I've been disecting the HD 7 for some ideas and plan to do some testing very soon. I'm the type that will immediately look at all settings and functions and then look through every file, folder and directory I'm able to, so we can do what many of us have already achieved. Keep an eye on me
DragonFire1024 said:
Not likely. I have a list of things to try on my head. Some simple, some outrageous. Truth is this HD 8 has been through hell. I've reset it more times than I can count. I've nearly disected it and to be honest I'm absolutely amazed I haven't broken it yet. So I'm giving her a break from that right now.
With that said, I have an HD 7 that's rooted. I have an idea to try some things using it, that could work on non rooted 7 and up tablets, that would be totally systemless that could open up the possibilities to some things. I've been disecting the HD 7 for some ideas and plan to do some testing very soon. I'm the type that will immediately look at all settings and functions and then look through every file, folder and directory I'm able to, so we can do what many of us have already achieved. Keep an eye on me
Click to expand...
Click to collapse
If someone were to go so deep to a point where they took it apart, maybe it would be possible to modify the bootloader by setting up a custom one.
Sent from my KFFOWI using Tapatalk
So I just bought a new 2017 version, Fire HD 10, and a case for it. It should get delivered tomorrow, but I want to be prepared for when I get it. I fully admit that I have limited Android knowledge, and zero Fire knowledge. I would like to get it as close to stock android as possible. Guessing this means rooting?
I found a walk through to install the play store, but I am unable to find anything on how to actually root it. Easier the better!
From what I can tell, the newest version is a 5.6.0.0, but I'm unsure what it will actually come with. If it needs updated, do I do it? Is there a working root for the newest version?
Also, are there any free ways to remove the lock screen adds?
Anything else you wish you had done when you first got your fire?
Thanks for any/all help
danballa said:
So I just bought a new 2017 version, Fire HD 10, and a case for it. It should get delivered tomorrow, but I want to be prepared for when I get it. I fully admit that I have limited Android knowledge, and zero Fire knowledge. I would like to get it as close to stock android as possible. Guessing this means rooting?
I found a walk through to install the play store, but I am unable to find anything on how to actually root it. Easier the better!
From what I can tell, the newest version is a 5.6.0.0, but I'm unsure what it will actually come with. If it needs updated, do I do it? Is there a working root for the newest version?
Also, are there any free ways to remove the lock screen adds?
Anything else you wish you had done when you first got your fire?
Thanks for any/all help
Click to expand...
Click to collapse
At present there is no method for rooting FireOS 5.6. You can install the Google Play Store and essential related services. Enjoy your new device.
danballa said:
Also, are there any free ways to remove the lock screen adds?
Click to expand...
Click to collapse
Only way I'n aware of without root is to contact Amazon.
There's a thread on this but in the past I just said it was a gift and they were disappointed:
https://forum.xda-developers.com/amazon-fire/general/how-to-rid-ads-special-offers-lock-t3585863
tech3475 said:
Only way I'n aware of without root is to contact Amazon.
There's a thread on this but in the past I just said it was a gift and they were disappointed:
https://forum.xda-developers.com/amazon-fire/general/how-to-rid-ads-special-offers-lock-t3585863
Click to expand...
Click to collapse
Awesome, thanks! I followed the directions, and adds are removed
What's everyone's view of rooting the pixel unlocked version? What features won't work? I know knox for samsung trips when unlocking. Is it the same concept with Pixels? My last device similar was a nexus 6 so yeah..
jobhax said:
What's everyone's view of rooting the pixel unlocked version? What features won't work?
Click to expand...
Click to collapse
Any feature that relies on Safetynet won't work and there is simply no way around that.
With Samsung, KNOX is a "fuse" that gets tripped so after you unlock the bootloader there's no going back. It'll forever know the bootloader has been unlocked at some point which messes with certain features (depending on make/model). With the Pixel phones you can flash the stock software and then re-lock the bootloader if you want. Once re-locked the OS sees the factory state and everything works as usual. Just make sure you've got the stock software flashed before you re-lock the bootloader or you risk bricking the device.
As a side note, with biometric security, make sure you've properly logged out of your Google account and removed all stored fingerprints or faces BEFORE you unlock. The unlocking process will wipe the device but your biometrics are still stored. If that happens you have to go through the setup process without biometrics and then perform a "proper" factory reset within the Android OS in order to get biometrics working again.
Of course the Pixel 5 is a new phone, so I'm giving this info based on currently released devices. There are always risks when you alter the factory state so be warned. There's a phrase my old boss used to use: "Pioneers take the arrows, settlers take the land." Not very PC but the underlying concept is sound.
I'll root asap. These days, I use it mainly for effective Adblock. The occasional app goes wonky, but it's a game of cat and mouse with safety-net.
YMMV etc
kboya said:
I'll root asap. These days, I use it mainly for effective Adblock. The occasional app goes wonky, but it's a game of cat and mouse with safety-net.
YMMV etc
Click to expand...
Click to collapse
The cat and mouse game is over, Google won. With hardware backed encrypted key negotiation it is no longer possible or feasible to beat. TNMTV (There's No Mileage To Vary)
That doesn't mean you can't root, just that there are consequences. For me, those consequences far outweigh any perceived benefit of having root access. I won't be rooting any more phones.
SteveYoungs said:
The cat and mouse game is over, Google won. With hardware backed encrypted key negotiation it is no longer possible or feasible to beat. TNMTV (There's No Mileage To Vary)
That doesn't mean you can't root, just that there are consequences. For me, those consequences far outweigh any perceived benefit of having root access. I won't be rooting any more phones.
Click to expand...
Click to collapse
What's the best adblocker for a non-rooted phone right now?
Guys, since Android 9 you don't have to root in order to adblock. Just use the private DNS option together with something like nextdns.io . It's also battery efficient, since it's not a VPN.
SteveYoungs said:
The cat and mouse game is over, Google won. With hardware backed encrypted key negotiation it is no longer possible or feasible to beat. TNMTV (There's No Mileage To Vary)
That doesn't mean you can't root, just that there are consequences. For me, those consequences far outweigh any perceived benefit of having root access. I won't be rooting any more phones.
Click to expand...
Click to collapse
We'll see what happens because, as you make clear when you include experiences, MAV (Mileage Always Varies).
---------- Post added at 05:20 PM ---------- Previous post was at 05:15 PM ----------
Nightwish1976 said:
Guys, since Android 9 you don't have to root in order to adblock. Just use the private DNS option together with something like nextdns.io . It's also battery efficient, since it's not a VPN.
Click to expand...
Click to collapse
True, but when I tried that after 9's release it wasn't particularly effective or at least not as effective as Adaway w Magisk's systemless solution. Maybe I'll give it another go on the P5.
likepeas said:
What's the best adblocker for a non-rooted phone right now?
Click to expand...
Click to collapse
Blockada, but download the App from the developer Website (play store Version doesnt get Updates Quick)
Pixel 5 will be the first device i dont plan to unlock+root, most benefits of rooting are gone in the last years because they got baked into Android. For adblocking there is Blockada which is as good as rooted adblock. I dont need a custom rom with stock clean Android and monthly Updates anymore. For debloating you dont need root, just a PC so i am going to deactivate most Google Apps.
Adblock so has a non-root version now.
kboya said:
We'll see what happens because, as you make clear when you include experiences, MAV (Mileage Always Varies).
Click to expand...
Click to collapse
Prediction: I'll eventually die of old age and you still won't be passing Safetynet. ☺
SteveYoungs said:
The cat and mouse game is over, Google won. With hardware backed encrypted key negotiation it is no longer possible or feasible to beat. TNMTV (There's No Mileage To Vary)
That doesn't mean you can't root, just that there are consequences. For me, those consequences far outweigh any perceived benefit of having root access. I won't be rooting any more phones.
Click to expand...
Click to collapse
If you know what you are doing there is no issues with Android 11, Magisk and safety net.
I can still use Google Pay and my banking apps without modules and nonsense coding. Just use Magisk and that is it. Oh of course you will need to hide a few apps in the Magisk settings.
Sent from my Pixel 3a XL using Tapatalk
One thing to keep in mind is warranty and insurance (if you have insurance) claims.
If you have to use the warranty or insurance and you are unable to revert to factory default then warranty and insurance claims will be a huge pain.
vandyman said:
If you know what you are doing there is no issues with Android 11, Magisk and safety net.
I can still use Google Pay and my banking apps without modules and nonsense coding. Just use Magisk and that is it. Oh of course you will need to hide a few apps in the Magisk settings.
Click to expand...
Click to collapse
Sorry, but no. See: https://www.xda-developers.com/safetynet-hardware-attestation-hide-root-magisk
SteveYoungs said:
Sorry, but no. See: https://www.xda-developers.com/safetynet-hardware-attestation-hide-root-magisk
Click to expand...
Click to collapse
Anything is possible, we go through this year after year with new updates to the software.
Google has always aloud its devices to have an unlocked boot loader and to be developed.
I personally don't see Google closing down its development. If they do, they will be out of the phone business. Most peeps buy the Google device for the freedom of development. I for one would buy something different if I could not root anymore.
Now for other manufacturers, it is a lot harder for them because they have there own software for their hardware and it is not compatible with the Google OS.
Sent from my Pixel 3a XL using Tapatalk
vandyman said:
Anything is possible, we go through this year after year with new updates to the software.
Google has always aloud its devices to have an unlocked boot loader and to be developed.
I personally don't see Google closing down its development. If they do, they will be out of the phone business. Most peeps buy the Google device for the freedom of development. I for one would buy something different if I could not root anymore.
Now for other manufacturers, it is a lot harder for them because they have there own software for their hardware and it is not compatible with the Google OS.
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
The Verizon versions of the Google Pixel 3Xl were locked down. I wouldn't say Giggle always allowed phones to be rooted. However, the ones sold by Google were rootable.
Sent from my Pixel 3 XL
Eudeferrer said:
The Verizon versions of the Google Pixel 3Xl were locked down. I wouldn't say Giggle always allowed phones to be rooted. However, the ones sold by Google were rootable.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
You are right. Verizon versions of Google devices will always be locked down.
If I remember correctly the last and only time that version allowed a Google unlocked device was a Samsung/Google Galaxy Nexus.
Sent from my Pixel 3a XL using Tapatalk
SteveYoungs said:
Sorry, but no. See: https://www.xda-developers.com/safetynet-hardware-attestation-hide-root-magisk
Click to expand...
Click to collapse
You said your not rooted right? You can still force basic key attestation (only needed for some devices), change device fingerprint, etc. Lots of things to do to pass safety net at the moment. Has worked fine for me ever since topjohnwu releaased that news.
vandyman said:
Anything is possible, we go through this year after year with new updates to the software.
Google has always aloud its devices to have an unlocked boot loader and to be developed.
I personally don't see Google closing down its development. If they do, they will be out of the phone business. Most peeps buy the Google device for the freedom of development. I for one would buy something different if I could not root anymore.
Now for other manufacturers, it is a lot harder for them because they have there own software for their hardware and it is not compatible with the Google OS.
Click to expand...
Click to collapse
Hardware attestation does not prevent you from unlocking your boot loader, and it does not prevent you from rooting. What it does do is make passing Safetynet impossible if you are rooted, unlocked boot loader.
This is not something that will one day be worked around. The days of passing Safetynet on a rooted device are behind us.
SteveYoungs said:
Hardware attestation does not prevent you from unlocking your boot loader, and it does not prevent you from rooting. What it does do is make passing Safetynet impossible if you are rooted, unlocked boot loader.
This is not something that will one day be worked around. The days of passing Safetynet on a rooted device are behind us.
Click to expand...
Click to collapse
Nothing has changed yet! I still can use Gpay with Magisk and without any add on.
Sent from my Pixel 3a XL using Tapatalk