Question No smart lock, trust agents screen shows no trust agents - Google Pixel 6 Pro

I have a rooted pixel6 pro with magisk.
the safetynet basic check passes.
My smart lock went away, and when I checked to see if it was enabled in 'trust agents', it wasn't even offered.
This occurred just before the last OTA update, 220305.
Things I've tried:
removing magisk packages installed in last week. They were NoStorageRestrict and ZeetaaTweaksApp.
I suspect one of those modules wasn't properly uninstalled and left a system setting changed.
installed OTA; it didn't help
flashed factory image with flash-all.sh modified not to wipe /sdcard
before I re-rooted the phone, I checked the trust agents and they're still blank

I guess the next step is to install the factory image, letting it wipe the storage. This is always a PITA, but migrate and titanium backup do most of the work. Google's own backup and restore has improved but still sucks.

Related

[Q] System files change asurvive after full unroot to stock T989UVLI4

Hi,
I have used this phone rooted for the last 8 months+ and after a full restore to stock and re-root, some changes seem to stick even after a complete un-root.
Long story short, been using LBE Security as a firewall and permission manager and i noticed it stopped blocking internet access for certain apps even when it showed it does but it did not. Decided to restore to stock T989UVLI4 and re-rooted and LBE is still miss behaving... tried a full factory reset, fix permissions via CWM and LBE is still refusing to work.
I am not sure what root apps could have messed up any of of the system files that could survive a full un-root, but this seems to be the case.
I s there a way to see if any system directories changed when they should have not and such directory would not fully recover on a complete un-root factory reset?
Any help would be very much appreciated.
Thanks,
744

[Q] Google account not showing phone as being used recently

I'm trying to get my phone visible on the android device manager, but it looks like Google's servers haven't seen my phone since I bought it in June.
Rather, I'm looking at my Device manager in my google account and when I look at the devices, it shows my S4, but it says "Last activity seen on: Jun..."
Incidentally, I probably rooted my phone around that time. Actually, I soft bricked it, recovered it by a Kies reflash, and then rooted it.
I've tried some of the usual stuff that's suggested to do for Android Device Manager- uncheck "allow wiping the phone" then wipe data on Play Services, reset, recheck "allow wipe" reset again. But that doesn't help.
I've also tried removing my google account from the phone then reinstalling, to no avail.
So, I'm at wit's end. How do I get my phone showing up on Google?
Incidentally, this is mostly stock ROM, except for the rooting. Admittedly, I did restore a lot of stuff via a Titanium Backup from my previous phone, that's why I figured an account wipe then reinstall should help- I just added it back- didn't use Titanium Backup to restore anything.
I'm reluctant to wipe the phone completely to get it showing up again, so what else can anyone suggest?
edit: a bit more data: it shows the phone last seen while I was on vacation- read: a week after I rooted and restored the thing, so root and Titanium Backup might not be relevant there.
Factory reset. If that doesn't work, odin back to stock.
Sent from my SGH-M919 using Tapatalk 4
Yeah, factory reset is pretty much the nuclear option. Admittedly, with a Titanium Backup, it's not that bad, but still, time consuming.
Instead, I fixed it by not only clearing the data of play services, I also uninstalled the updates for it- didn't seem to help- and cleared the data for Google Services Framework. Reset, re-allow locations, and it started working.
Hopefully this also fixes my gmail polling issue/lack of push.

[Q] Factory reset

Many suggest wiping the tablet before upgrading firmware but does it really make a difference? If I do it anytime, will the device be back to the state it came in the box (with the possible exception of tripped Knox bit), in other words, is the original firmware and setup on some ROM chip or reserved area or will it be the latest version of firmware installed but cleaned of apps, accounts and settings?
Does it make any difference to wipe before installing an update if it can be easily done afterwards in case of issues without the tablet returning to an earlier version?
To the best of my understanding, and someone can feel free to correct me if I'm wrong, an Android device has several partitions in its filesystem. The operating system and other files that shipped with the device, such as stock apps, are kept on /system, and anything associated with user settings and user apps is kept in /data. As I understand it, factory reset simply wipes this /data partition. Any sort of firmware update overwrites the /system partition with the new version. Thus, if you do a factory reset, your tablet should be cleared of any apps and settings you installed and changed, and the firmware will still be the latest update you have installed.
To the second question, I know that you can wipe after an update without affecting the firmware version you have, however, I'm not sure exactly howy wiping fixes problems, so I will leave it to someone who knows a bit more to explain the pros/cons of wiping before/after updating your firmware.
Might be dumb question but how do I prevent Note installing all the apps I had on it before factory reset after it boots up again and I enter my Google account info?
Co-re said:
Might be dumb question but how do I prevent Note installing all the apps I had on it before factory reset after it boots up again and I enter my Google account info?
Click to expand...
Click to collapse
When you're doing the whole Google account thing, don't check off the box to backup and restore. I checked the box yesterday when I was doing the KitKat flash, and it started downloading things onto it that I had on other devices...it was a mess. LOL So when I flashed a new ROM later in the evening, I made sure NOT to check off that box when setting up the Google account.

On 6.x, want to upgrade to 7.1.2 (update: can't restore from backup and need help)

So i'm really interested in upgrading to 7.1.2 so i can install new camera app so i can use ZSL
i've been holding off on upgrading past MM because i need my customization and control from xposed
there is an unofficial xposed, so that will help ease me over till the official gets released
my question is, what happens if i keep xposed and do the upgrade via flashfire
do i need to uninstall all my xposed modules then xposed before i upgrade?
my phone is rooted already, so i know that when i upgrade via flashfire, i will still be rooted
at the same time i want to try out magisk
if i do this, am i suppose to unroot, upgrade, then install magisk? or does it not matter
also, i will be obviously making a backup of my phone, so i should be completely safe to play around with everything right?
any advice welcomed
update
well, i messed up
everything was working, but xposed didn't play nicely, so i attempted to restore my twrp backup and now it's failing
i used adb backup twrp command and saved it directly to my pc since my 16gb didn't have enough space
i checked off everything except for the last check box efs, this created a 10gb .ab file
when i tried to restore it, it restarts the phone during/after system and boots into the google blank screen with unlock icon
the closest thing i've googled so far is this: https://github.com/omnirom/android_bootable_recovery/issues/133 which says it might have some issue because of the compression...
(note that i did not password protect the backup)
i'm wondering if this is the problem, can i uncompress the .ab file from my computer and manually install each of the components?
very tired and exhausted from this, hopefully someone has an idea of what i should do

M9 switching to Magisk

(Edit: after posting this realized I may be in the wrong forum, sorry. ADMIN, please move, or notify me to move it, if so)
First off, here's my specs:
HTC One M9 (att )ve
Build 4.27.502.7 (stock ROM-rooted)
Recovery: TWRP 3.2.1
SuperSU v2.82
S-ON
Bootloader Unlocked (HTCdev)
I'm having Play Store issues, says Device Un-certified. I can get in, but anything I try to DL or update, is very sketchy. Most of the time, I have to do the data/cache thing for PS, and PS Svcs., then to be sure, reboot to recovery wipe Cache, then reboot system. This works for a few downloads then have to go again. That I can kinda deal with, annoying as it can get, but my PayPal apps and Banking apps are giving me grief over being rooted.
I'm wanting to switch to Magisk, but when running "cleanup to switch su" in superSU, it says cleanup Failed. Even tried the "cleanup for unroot", same thing. Pretty sure it's an issue with stock boot.img. Not sure what happened to it, but I just need advice on the best route here.
Should I just lock bootloader, restore my stock backup, then start from scratch (redo TWRP, reboot, etc.) or is there a way to locate and "insert " the stock boot.img.
I'm not on most of yalls level, but I'm pretty good on a computer, and after rooting a few of my phones, I'm getting the hang of it.
Seems an issue with the account you're logging in with. Disassociate the account from that phone, clear cache and data, then reregister that account and allow everything googleplay related. Allow the find my device service in system administrators too.
If no joy you'll need to flash back to stock with a stock firmware (zip is easiest) and start the root process again but locking bootloader ISN'T necessary. Just omit that next time around. If you have s-off you can leave that as is too.
Not sure about swapping su providers, I think that will be a reflash too.

Categories

Resources