Changing some permission in Privacy Guard and the android Nougat cannot start - Wileyfox Storm

I have a hard problem with my Wileyfox Storm (updated with Nougat). That phone had cyanogenmod. Now they update it to Nougat but with the Privacy Guard on it.
I was changing some permission in Privacy Guard and, after this, the phone cannot start. I thing that some permission stops the android and it cannot work…
I want to ask if I can take my data from the phone before a factory reset and if I can to reinstall Nougat, to restore this permissions. I never add a Google account to my phone…
Can I disable the privacy guard on android Nougat without android loading?
Thanks!

Related

[Q] Can I root the Nexus 7 (2012) without logging into a Google account?

I've recently upgraded to the 2013 Nexus 7 and want to give my old Nexus 7 to my nephew. It is currently unlocked and rooted (4.4.2) under my account. I want to go back to factory (basically wipe the tablet) but keep it rooted for him. Can this be done without going through the Google account set up (I don't want to tip him off with e-mails to his account about the new device)?
Google account creation or login is not mandatory after a factory reset, and performing a factory reset in either the stock or custom recovery does not need a Google account either.*
A Google account can be set up/connected any time after skipping that step by starting the Play Store app.
To do any initial customizations following a factory reset (even without a Google account credential) though, you will need to connect to a WiFi AP.**
* something to watch out for is if your root app is not installed as a system app but as a market app - a factory reset will delete app portion, so restoring the app portion will either require a sideload (of a backup of the) .apk, or a google account to download it again from the market.
** perversely, the WiFi router does not need to be connected to the internet; after the tablet is connected to a router , the WiFi setup screen on the tablet will eventually time out and let you continue. This suggests a means to partially configure a tablet following a factory reset without the tablet ever "phoning home".
good luck
Edit: From your post it is not evident whether you are planning (i) a factory stock install followed by re-rooting, or (ii) have a lightly-rooted stock that you merely want to perform a factory reset on. In either event a solution would be to make sure that SuperSU is installed as a system app. That way 100% of your root kit will survive a "factory reset" procedure in the recovery. In the case of (i) you can certainly reconnect to your own Google account to download the newest version of SuperSU, get it installed as a system app (I think that is a menu item in the SuperSU app), and then do a "factory reset" afterward.

Google account removed after a reboot

This has happend to me thrice already, after rebooting my device I lost my google account and the playstore wont launch it also wont show and option to add a google account under the accounts tab in settings until I do another reboot. I am using a stock rom with systemless root, franco r9 kernel & exposed. Im wondering what is casuing this issue so I can prevent it.

Why does my phone keep getting decrypted?

I'm very confused by the behavior of my Nexus6p right now. I would like my phone to be fully encrypted, IE, you pick up the phone and can access absolutely none of my data without typing in a password. So I've clean flashed it several times, usually whenever a new update comes out. And each time I do this, the phone behaves how I want, when it boots, I get a password screen that says "enter a password to continue boot". It goes on this way for a day or so usually, and then suddenly this password screen stops showing up and I get the "you must enter a password after restarting" screen that clearly has already decrypted my data because I can see notifications and even play music through bluetooth without entering the password.
After each clean flash, I have been installing various mods. This time around, I have the things I've flashed down to TWRP 3.1.0, Magisk 12, and ElementalX 4.08. In the security settings, the phone still reads as encrypted, so I'm very confused. Is this normal behavior for this device, or is it one of the above things I have flashed? Either way, how do I fix this so that my data actually stays encrypted when the phone boots?
I have had similar issues to fix I formated everything and then installed the rom installed newest vendor image and then kept on eye on what I allowed special access to my phone
Keeper was wanting special access so I stopped using them and switched to last pass I have not lost decryption on phone boot
Also decided to pay for esexplorer pro to get ride of any possible infected ads
Your phone data is still encrypted, but your security settings are not optimized for what you want to accomplish. Make sure your Lockscreen has a password/PIN/Gesture set. There is the password on BOOT when encrypted, a password on Lockscreen when the screen is off, and In Settings>>Notifications>>Gear Icon>>"On the lock screen"- there are three settings. Default is set to "Show ALL notification content". Set it to NOT show notifications for now until you set which ones you want to show or hide. TWRP and EX are not causing your issue. Magisk might be but I don't use it. Uninstall just to be sure and/or check in the dedicated Magisk thread. This is on the stock 7.1.2 ROM. If you are running a custom ROM, YMMV.
So if I understand the issue correctly, you clean flash and you have the prompt to enter your credentials before booting finishes. Eventually you get set up and upon a reboot you notice that the prompt is gone?
Check your apps. You're using an app that requires an accessibility service (see Settings / Accessibility / Services). Granting an app accessibility service will do away with the boot entry of your pin/pattern/password. Set up your apps again and either don't use the app in question or just don't grant it the accessibility service for whatever feature requires it.
Known issue, btw. I forget why it happens, Google may turn up the results you're looking for.
Edit: Despite it not asking for that prompt on boot, your phone is still encrypted, by the way. This also has absolutely nothing to do with TWRP, EX, Magisk or how you choose to have your notifications hidden on lock screen.
2nd: Sadly, just revoking the service won't usually restore the prompt while booting. You'll need to clean flash again and not grant it in the first place.
That makes sense, I was looking in the wrong place. That's a really irritating design decision, there's no sense in having the encryption at all if you're just going to store the material necessary to decrypt the data in the clear.
For now, changing my password seems to have returned the encryption prompt while leaving the accessibility services working to the best of my observation.
It will probably go away again shortly​, most likely after the app uses the accessibility service. If it does, revoke the service and change your password again or clean flash. I don't believe there is a way to keep both 100% of the time.

App-ops Android System caused bootloop

I accidently, in privacy guard aka app-ops, unchecked the Android System's keep awake and running background, then every app stopped working, then I'm in bootloop, is there a way to adb back into app ops and change it? I can access TWRP and don't ask me to clean flash... Any help is appreciated
Wipe data

[GUIDE] Disable OTA/system updates on Stock ROM

This will help you to enjoy clean stock smooth experience on Mi A2 without the OTA being shoved down your throat. I know you can always flash custom ROM, but in my experience there were always a few micro-stutters in the UI and some bugs here and there so I decided to stick to stock with Magisk as the ROM is almost the same as a CAF compiled ROM with no bloat except the Feedback app which I manually disabled.
WHY? Because the monthly OTA updates don't fix anything. So it was annoying to keep updating every month.
- There are some comments here and there which asks to disable just the "Apply update on reboot" in developer options.
But again, it still kept popping up in my notification bar.
- There are ppl saying just disable the notification. But it still goes ahead and downloads the 1.3 GB update zip while phone is idle.
So the final solution which seems to be working for me so far is -
1. Disable "automatic apply update on reboot" from Developer Options.
2. Remove the package named "Dynamic System Updates" using root explorer or ADB, whatever you're comfortable with.
2. Download "Servicely" app from play store (or any service blocker app, really).
3. Disable the following services -
com.google.android.gms.update.SystemUpdateService
com.google.android.gms.update.SystemUpdateGcmTaskService​4. ????
5. Profit.
How to disable updates on Android 9? I downgraded from Android 10 to Pie due to random reboot issues

Categories

Resources