So I got to looking at settings>lock screen and security>other security settings>View security certificates there are about 159 security certificates give or take a few, their are some weird ones in this selection, my thoughts are if some of these were disabled, could we preform a successful root.
This is just a thought but may lead to something where we are able to full root.
Related
oskiny, you do not have permission to access this page. This could be due to one of several reasons:
Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Hello there,
Since I have updated my LG G4 to 6.0 MM, I get a message every time when data option reconnect. It says: "customize your phone. Download carrier's apps and content" . I know it's T-mobile customization, but I don't want it on my phone.
When I go to Setings - Apps - Show System - App updates - notifiations I have 3 options:
*Priority
*Allow Peeking
*Hide sensitive content
No matter what I try but the message keeps coming back.
When I press "Force Stop" the message dissapear. But when data connect again after losing wifi or after a restart, the message is coming back.
What can I do so the message wil never come back again. Root and download the T-mobile customization is not an option
Without root, you are screwed, and the workaround you found is the only one available.
You could take out the sim, but that would render it quite useless.
With root you can undo all their cosmetic changes (like freeze the APK).
You can root without unlocking the bootloader, which would still allow you to flash an original image (recommend you make your own backup)
But it would be a bit more cumbersome without a nice recovery on the phone itself.
If you softbrick you will need a computer.
Along with the cosmetic changes, they might optimize certain settings for their network (at least I think they could).
So unless you download the patch and study it's effects (backup, install, backup again, compare changes).
You might be missing out on channel/network changes that could affect the quality of your service.
If you root, you might be able to trick your current rom into thinking it already has the patch applied, but this would be complicated.
It's easier to just override or remove their changes after it has been applied.
Like the boot animation, ringtones, backgrounds, etc.
FreezyExp said:
Without root, you are screwed, and the workaround you found is the only one available.
You could take out the sim, but that would render it quite useless.
With root you can undo all their cosmetic changes (like freeze the APK).
You can root without unlocking the bootloader, which would still allow you to flash an original image (recommend you make your own backup)
But it would be a bit more cumbersome without a nice recovery on the phone itself.
If you softbrick you will need a computer.
Along with the cosmetic changes, they might optimize certain settings for their network (at least I think they could).
So unless you download the patch and study it's effects (backup, install, backup again, compare changes).
You might be missing out on channel/network changes that could affect the quality of your service.
If you root, you might be able to trick your current rom into thinking it already has the patch applied, but this would be complicated.
It's easier to just override or remove their changes after it has been applied.
Like the boot animation, ringtones, backgrounds, etc.
Click to expand...
Click to collapse
In that case, let's root!
Thnx
I have encrypted my data on the M9 (see settings->storage->encryption) . Every time you reboot the phone, a prompt for the password (in my case a pattern) appears before the phone proceeds and decrypts your data. A failed attempt after 50(?) tries resets the phone to factory. Currently, the encryption option in settings is checked and not modifiable but rebooting never produces a decryption password query?
This is a SPRINT phone Android Ver.: 7.0 Security Patch level: Feb 1. 2017
Don't quote me on this but I think it applies to turning the phone off and back on. Once the phone knows the key it's pointless to keep asking every time you unlock the device because if you know the pattern then it is obviously you..
I have the Strong Protection setting (previously called Secure Startup) enabled, but it recently stopped working (probably sometime since the ASI3 firmware update for N975U1). Instead of prompting for my password early in the boot process, the phone gets all the way to displaying my lock screen (showing my contact information, selected background image, etc.), which suggests that the phone's encryption has already been unlocked with no password entered yet. (It does still require my password to get past the lock screen.)
I've tried disabling and then re-enabling the Strong Protection setting, and clearing the system cache, but the phone still boots all the way to the lock screen without requiring a password.
Has anyone else encountered this problem? Alternatively, is there anyone else (with the ASI3 firmware) who is *not* encountering this problem?
It may have changed a bit in an update?
Ever since I got my note 10+ (build ASJ2 and the previous 2 updates) that is how strong protection has worked.
I published a script that can automatically resign GrapheneOS OTAs with your own keys, and also optionally apply a few modifications like enabling ADB root (without turning on ro.debuggable), ignoring allowbackup and changing the update URL.
You can use it if you like GrapheneOS (I think it's the Android OS with the best engineering, security and privacy), but would also like to have full control of your device, by controlling the verified boot keys of your device and applying modifications that make the OS do what you want regardless of what upstream OS developers, app developers, or anyone else might want.
Note that, on the other hand, GrapheneOS follows the Google Android security model which says that the OS will not perform an action you want it to perform if it may result in something that "application developers, content producers, service providers, and employers" do not consent to (which means not letting you have root, or ignore app wishes regarding backups and other settings, or send arbitrary responses to app requests, etc.), while this script will let you do what you want with your own device regardless of whether it's in anyone else's interest or not, including things that this script does not itself support since you control the verified boot keys of the device and can thus sign anything; all this while still taking advantage of all the security and privacy features in GrapheneOS, including verified boot.
You can find it at https://github.com/chriswoope/resign-android-image
Currently it's intended for people with good technical knowledge, although once you set it up (if you run Qubes a lot of steps are automated) it should continue working with no or minimal intervention.