yashsingh1/xdaforums huggingface dataset:
[Redmi Note 10 Pro] meirioon:
This. What they do basically is take chinese ROMs and remove all the useless bloatware, the ads in the system apps and keep the extra features ; there's a permanent AOD, native super wallpapers and more
[Redmi Note 10 Pro] Marvin.the.Martian:
But this is with root right? I use a lot of finance and trading on my phone, how secure and safe are those roms?

Now i have stock EEA firmware, they go by GDPR and EU rules. No ads and you will need to accept a prompt on every instance where they would collect data. I like this only problems EEA gets updates a bit slower.
[Redmi Note 10 Pro] djskribbles:
You don't have to root your phone to use xiaomi.eu. it does pass safety net and my banking app works.
[Redmi Note 10 Pro] anur@g:
Actually root is not required. Only requirement is unlocked bootloader. On android devices only trusted apps should be granted root then most of your financial/trading apps will be safe. Because other user apps won't be able to access financial app's data which haven't been granted root permission.
[Moto G7 Plus Questions & Answers] makuaz:
Hello good afternoon greetings from Mexico, a pleasure to greet you from here, months ago I tried to install lineage in a new motog7 plus since the factory rom is extremely restrictive and slow; in addition to the major security flaws.

at first all fluent install twrp and activate developer permissions, likewise unlock the bootloader; When flashing the phone, there was no problem, even I installed the gapps, the problem started when restarting it simply no longer turned on, it only lit the phone's led in red, when performing some procedures I managed to start it but it does not pass the image.

I have left it charging for hours and only the lightning logo comes out (which implies that it is charging); and in very small letters it says "any key to shutdown".

when I manage to turn on it does not go beyond the android logo.

These are the specifications:

Motog7 Plus Model: XT1965-T

Black

Dual SIM

I have tried to connect it to the pc to flash it and return it to its original state but it does not detect it.

Neither does it enter the recovery mode, the keys simply do not seem to work to enter the modes that it has natively.

Currently I have another phone the same since in those months I bought two similar ones; which I have not touched at all so as not to ruin it.

Any help to revive it would be greatly appreciated, thank you very much colleagues.
[OnePlus 7 Pro Questions & Answers] xlxcrossing:
Is anyone else having this issue. Started yesterday for me after years of being rooted without fail. Is there a Google Services update that now runs root check for fingerprint login?
[OnePlus 7 Pro Questions & Answers] brigantti:
Same here did you get it to work?
[OnePlus 7 Pro Questions & Answers] EpicEddy:
Same on my OP 8 pro, Magisk hide, reboot and reinstalling etc didn't work either
[OnePlus 7 Pro Questions & Answers] Alberhasky:
Ok, I thought I was going crazy, I have the same problem since last couple of updates... Anybody figured out how to fix it? Maybe an older version of chase mobile?
[OnePlus 7 Pro Questions & Answers] brigantti:
The new chase app update fix the fingerprint started to work again i got root with magisk and edxposed instaled.try to update the app
[OnePlus 7 Pro Questions & Answers] supeRUUser:
Doesn't work for me with app version 4.262 (updated December 15, 2021).

Moto G7 Play (channel), LineageOS 18.1 20211226-NIGHTLY, Magisk v23.0.

As far as I can tell, fingerprint login is the only thing that doesn't work. edit: Quick view balances also does not work.

Just for comparison, everything works with the Bank of America app, including fingerprint login.
[OnePlus 7 Pro Questions & Answers] Cares:
I had fingerprint working with root by installing older version and then updating but now I can't get it to work anymore.
[OnePlus 7 Pro Questions & Answers] supeRUUser:
Can anyone confirm whether the fingerprint works without root (but with bootloader unlocked and custom ROM installed)?
[OnePlus 7 Pro Questions & Answers] CPngN:
I'm seeing this issue still in Feb 2022. Rest of app works. Funny how whatever it detects isn't reason enough to block access, just block fingerprint.
[OnePlus 7 Pro Questions & Answers] supeRUUser:
Yes. I just reset my device and reinstalled LineageOS. The fingerprint worked. I then flashed Magisk (and enabled Hide for the Chase app), and the fingerprint continues to work. It seems you just need to set it up *before* rooting.
[Google Pixel 6 Pro] Norma Stitz:
So now that I have a pre-order secured, I'm trying to find something equivalent to magsafe to use as a vehicle mount. Is there an established standard for this phone, or is it a choose-your-own-adventure sort of thing still?

I'm hoping to find something that sticks magnetically, charges wirelessly, and doesn't interfere with NFC.
[Google Pixel 6 Pro] rav101:
Check out Moment. They do magsafe cases for Android phones including the Pixel 6 series
[Google Pixel 6 Pro] Norma Stitz:
That looks perfect. I returned my 13pro max, but happen to still be stuck with a magsafe charger I couldn't return. I just assumed it would have to buy a different charger also, but I guess not. Thanks.
[Google Pixel 6 Pro] rav101:
It will definitely add magsafe. I guess there is a question as to whether the phone will still charge though the moment case. That I can't answer for you
[Google Pixel 6 Pro] dj24:
Can you let us know how the 6 Pro's battery life compares to the monster 13 pro max once you have time to play with it?
[Google Pixel 6 Pro] Norma Stitz:
I learned it was not user repairable after I ordered it, but before it was delivered. I only played with it for an hour or so before returning it. It's too bad because I really liked the phone, but I just won't tolerate a company treating me like that.

I'll do the same with the Pixel if it turns out to be similar. Based on the initial camera module report, I wouldn't be surprised if I just keep using my ancient V20 for even longer.

FWIW, the pro max did sit on my counter powered on idle for several days and only lost maybe 20% per the meter. I never put a SIM in it though, so that might have helped.
[General Topics] gzacharias:
My network (AT&T) has a setting which allows me to display my caller ID only to contacts. When I call a number in my address book.contact list, they can see my number but if I just dial a number not in the list, they can't.

But I've noticed that when I call people who are in my contact list from my call history, they see my number as "private". It's easier to dial someone from the call history list than to pick them from the huge contact list I have.

Is there a way to show my caller ID (a registry hack perhaps?) to people who are in my contact list, even if I dial them from my call history?

I'm using a Tilt that runs Windows Mobile 6.1, but I've seen this issue with both Windows Mobile phones I own (the other one is a Cingular 2125 smartphone with Windows mobile 6.1), so I think this is a general Windows Mobile issue than a phone issue.
[Google Pixel 5a] evnStevn:
If you haven't already, you should be receiving a notification that the Stable Android 12 or "S" Build is lurking in the shadows of your Pixel 5a handset. If you're currently on the (only) beta version we received OTA, your update won't inconvenience you for too long, as it weighs in at <4 mb, all in.🙄

Safe Journey's...evnStevn
[Google Pixel 5a] CarinaPDX:
The factory images are up on Google's developer site, and when I tickled the system update found the 12 upgrade. I'm downloading the factory image now (for rooting with Magisk) then will upgrade to 12. Then more to learn...
[Google Pixel 5a] evnStevn:
Right-On, I'm not ready for that, the Big League's (yet) as I'm still down here playing T-ball !🤮
[Google Pixel 5a] naterz:
Attempted the upgrade last night, seems there's some new things required if you want to flash the modified boot image and successfully boot. I believe you need to wipe the data partition and also pass along a few flags during install. However, temp root is an option if you want to avoid that for now (I did) by simply booting the image in fastboot vs flashing it. Just FYI!

Edit. Sounds like SafetyNet won't pass yet if you do end up going the permanent route? I could be wrong but I believe that's what's I've read. I just checked on mine and the temporary boot image does seem to so that's good.
[Google Pixel 5a] CarinaPDX:
If you read this thread you will see how to do it, as done on beta releases. https://xdaforums.com/t/guide-flash-magisk-on-android-12.4242959/ It is possible to achieve permanent root on 12 without wiping the personal data but it is a delicate dance. I have not tried it yet but as I understand it the process is to unroot 11 and at least remove Magisk modules, take the 12 update, boot into bootloader and use fastboot to remove boot verification and replace vbmeta.img, then flash patched boot.img, reboot and reinstall magisk. It seems there is a problem with just flashing the new factory image with the wipe option (-w) removed. Instead of fastboot flashing the patched boot.img it is also possible to directly patch the boot.img from Magisk while temporarily booted from the patched boot.img (via fastboot), again after removing the verification checks. It may be critical as to when the 5a is rebooted or not; it needs to have a normal reboot after the OTA upgrade in order to complete the upgrade, then boot to bootloader for fastboot operations. I am going to go back and make instructions for myself before proceeding, and will do a Titanium backup before doing anything else.

Edit: it appears that some have achieved permanent root and still passed the SafetyNet check. IIRC it was done through the OTA upgrade path but I need to check that. If you are willing to wipe your data then just installing the factory image and then doing the fastboot commands it might work but that is not clear. Too many attempts at root and SafetyNet failed while flailing so hard to know right now if there are good alternatives to OTA.
[Google Pixel 5a] michaelc5047:
Thanks for the link. I downloaded the full Android 12 image, installed it, disabled verity and wiped my data via fastboot, then flashed the magisk-patched boot. Worked like a charm and safetynet passed after hiding Magisk and installing Riru and the universal-safetynet-fix.
[Google Pixel 5a] CarinaPDX:
I am hoping to avoid wiping data by taking the OTA and then rooting - I just need to find the time to backup and write down the process first. I knew that the update could be done directly with the factory image, then rooted, but that requires the data wipe. If I encounter a problem that is the fallback approach - then restore data with Titanium.
[Google Pixel 5a] tintn00+xda:
I don't mind wiping data once. But if I have to wipe data for each update just to root, I'll stay on 11 for now until there's a better way to root
[Google Pixel 5a] BlvckSensei816:
Exactly.... I'll wait for a better way to upgrade and keep my root on 12
[Google Pixel 5a] CarinaPDX:
You don't "keep your root" on 11 updates; you unroot, take the OTA, then root again with a newly patched boot.img. And the data isn't wiped when moving to 12 if done through the OTA, just like 11 updates. If flashing a factory image the data is always wiped. What is different with 12 is that there is a verification of the boot.img and this has to be turned off (because the boot.img is patched), with a single fastboot command. It does appear to be sensitive to some details, so best to have a detailed procedure written down before starting the process. But those that have done it do not report a long or difficult process - just a finicky one.
[Google Pixel 5a] BlvckSensei816:
Ok ...have you done it yet?....can you tell me your process or elaborate more to my understanding
[Google Pixel 5a] BlvckSensei816:
I want to upgrade ota....but what do i have to do to achieve root without loosing files, setup, etc
[Google Pixel 5a] CarinaPDX:
No, I have not done it yet - oddly enough I have other things needing doing. The information needed to do it is in this thread: https://xdaforums.com/t/guide-flash-magisk-on-android-12.4242959/ Unfortunately since it started during the 12 beta program, and there was a lot of trial and error, it is necessary to work through the long thread and sort out the process - which appears to be fairly simple (if inflexible).

When updating or upgrading there are always two paths to take: 1) take the OTA that is offered (after unrooting), or 2) flashing the full factory image. Generally speaking, OTAs are designed to keep the user data untouched [edit: not untouched but just converted where needed for the new system] and the factory image is intended to put the phone to factory condition (i.e. no user data present - starts from scratch). Updates (i.e. not upgrades between Android major versions) over-the-air (OTA) are replacing blocks of the stored image, which is very efficient, but requires a pristine stored image (hence the need to unroot to pass the check). Upgrades (new Android versions) seem to download the entire image, IIUC, and then clean up any data (like config files) that are not compatible with the new system. Sometimes the result has been less than perfect, although it is mostly reliable. Ultimately a factory image is the guarantee of getting a known good system, which can then be set up to the user's taste. Backing up user data (e.g. with Titanium Backup) and restoring can make this easier but again, config files from the previous system if restored on the new system can cause problems. Some people prefer to flash the factory image and reinstall the apps as new to get the highest confidence in the result. Most of us just take the OTA and trust the process, prepared to wipe config files or even flash the full factory image if there is a problem. Your choice.

After I write a procedure for myself, and successfully upgrade, I will post it.
[Google Pixel 5a] anubis2k3:
So those of us that never rooted can just skip the unroot process and do the rest I assume?
[Google Pixel 5a] BlvckSensei816:
Ok cool and thanks....that was awesome info
[Google Pixel 5a] CarinaPDX:
That is the case. It seems that some with 12 beta got tripped up by not getting unrooting/removing Magisk and/or its modules right so that is one less thing to worry about. If you have never rooted then the OTA should work as expected. Rooting can be done in two ways, either by achieving a temporary root and using magisk to directly patch the boot.img, or by patching the boot.img and flashing it, right after removing verification and flashing the new vbmeta.img (in both cases). Of course you first have to unlock the bootloader and enable USB debug, install the Android tools on your computer (minimum version: you only need ADB and fastboot), and connect your computer to the phone with a USB cable. Again, refer to that thread or wait until I can write something up.
[Google Pixel 5a] BlvckSensei816:
How do one remove verification?🤔
[Google Pixel 5a] tintn00+xda:
I haven't been able to permanently root android 12 without wiping my data. I'm not talking about upgrading from 11 to 12. I'm talking about after installing 12, I still have my data. Any attempt to permanently root 12 causes errors unless I wipe my data. This was detailed quite a bit in the link you posted. Have you tried permanently rooting 12 and keeping your data?
[Google Pixel 5a] CarinaPDX:
As I said before, I have not had time to try the upgrade. Also, that thread has multiple conflicting posts which is why I know it will take time to go through and parse out what works and what doesn't. There are posts IIRC where root was achieved with data retained - but exactly how that was accomplished is not clear (or even if that really did happen). Since we have not had our phones for long there shouldn't be too much in data to lose, and there is always Titanium, so I will give it a go when I have time.

One of the things that I would like cleared up is if the way to 12 and root is to stop the OTA upgrade process at some point and remove verification and/or root before continuing, or possibly root fails because it is attempted before the upgrade is complete. IIRC the OTA has at least one reboot involved, with some processing after the reboot (probably fixing the data to be 12-compatible). Clearly if the upgrade can be done while retaining data and then successfully rooted then it must be done in a precise way; the lack of precise explanations of successful roots is very disappointing.

Edit: If it does turn out that data must be wiped every time 12 is rooted then that means backing up and restoring will be needed for each update, as well as unroot/root, and possibly removing verification each time. That would be a huge PITA. Let's hope that isn't so.
[Google Pixel 5a] CarinaPDX:
It is explained in the thread I linked. But at this point unless you are willing to wade through 14 [make that 16 and counting...] pages of posts it is better to wait until someone posts a good procedure. Anyone not familiar with flashing is liable to get into trouble and needing a factory flash. However good 12 is, it is not so good that we can't wait a bit.
[Google Pixel 5a] BlvckSensei816:
U right.... I'll wait
[Google Pixel 5a] CarinaPDX:
I just went back and got caught up on the thread I linked to earlier. It does appear that a wipe is necessary to root after a 5a is on 12. Ugh. But it also appears that it might be possible to do an OTA upgrade and get root without wiping data, which at least would make the upgrade to 12 easier. It seems that if the OTA image is sideloaded (adb sideload) instead of just taken OTA, the update is done and then before reboot the verification/vbmeta and root is done the system will reboot into rooted 12 with data intact. (see https://xdaforums.com/t/guide-flash-magisk-on-android-12.4242959/post-85815505) Apparently when a system is upgraded to 12 via the OTA software update, verification is installed before reboot, and after the reboot the verification doesn't allow for removal of verification without a data wipe. The key is to install first, remove verification, root, then - and only then - reboot. Perhaps someone would give that a try...
[Google Pixel 5a] BlvckSensei816:
Question?......do you know how to disable 5g and use LTE ....i have this 5g icon at the top and i think its draining battery life
[Google Pixel 5a] CarinaPDX:
Go to Settings/Network & Internet/Mobile Network. Hold your finger on your Mobile Network for a bit then release. The page that is presented will allow you to choose your connection preferences - touch that and your choices will pop up.
[Google Pixel 5a] CarinaPDX:
Duplicate removed
[Google Pixel 5a] BlvckSensei816:
Yes...but thus stupid pixel 5a 5g doesn't even have that option....this phone is weird 🤔
[Google Pixel 5a] CarinaPDX:
Is it unlocked or TMO? The unlocked phone has it. Just hold down on "Mobile Network" for a second, then on the next page look for "Preferred Network Type"
[Google Pixel 5a] BlvckSensei816:
Unlocked....bought it from google store
[Google Pixel 5a] CarinaPDX:
I edited my last comment so perhaps you didn't see it. Look again. Your phone will do this. The trick is to hold down the Mobile Network Selection enough time - tapping on it may not work.
[Google Pixel 5a] BlvckSensei816:
Yea i figured it out....i use code *#*#4636#*#* and changed my network settings to LTE....network is much better now....i ran speedtest and hell turns out LTE is faster than 5G....smh the really sold this 5G Bs.....and we bought it 😂🤦‍♂️
[Google Pixel 5a] nijel8:
Can anybody post or PM me original boot.img from Android 12 beta 5 factory image? Recent Magisk Manager canary update 23010 screwed up my root and MagiskHide as well :(. If someone has a copy of last canary Magisk.apk with MagiskHide (believe it is v. 23001?) I need that as well please. I am out of town with very limited internet and need to get root back. Not having root sucks big time!

Tnank you in advance!
[Google Pixel 5a] CarinaPDX:
You should probably post that on a 12 beta thread like the one I had linked to in post #22 - better chance of finding someone with the beta and canary versions.
[Google Pixel 5a] nijel8:
Delete
[Google Pixel 5a] nijel8:
That thread is for Pixel 5, not 5a... Different boot.img...
[Google Pixel 5a] V0latyle:
Barbet SP1A.210812.015

Magisk 23001

Be aware that you have to perform a complete uninstall of Magisk from within the app; you cannot simply uninstall it from Android and reinstall the older version, as it will not detect root.

For everyone looking for information on rooting your Barbet, please check the Pixel 5 discussions. The 5a has the same partition configuration as the 5, all the commands are exactly the same, the only difference is you need the 5a specific files.

As has been noted, we currently do not know of a way to retain data post upgrade and re root. It currently seems, for reasons yet unknown, that root on Android 12 can only be accomplished with a clean install or a data wipe.

If you are running the 12 Beta and previously wiped, you should be able to upgrade to the 12 stable release via ADB sideload and reroot without a wipe. However, if you are on Android 11, you currently have two options:

- Take the upgrade, retain data, use temporary root by keeping your /vbmeta and /boot stock, and boot the patched image via fastboot - meaning you lose root if you reboot

- Take the upgrade, wipe data (or perform a clean factory install), gain permanent root.
[Google Pixel 5a] BlvckSensei816:
Thanks for the clarification 🤝
[Google Pixel 5a] nijel8:
Thank you.

But I already got root back. Got a friend to go to my house, turn my PC on and run TeamViewer. Rest was a piece of cake. But yeah, I have read your experienc with Magisk downgrade. Mine was the same but I fixed it by patching boot.img with 23010 and then downgrading to 23001. Didn't have to completely uninstall and clean all Magisk traces. 23001 patched boot do not work anymore once you've gone through update to 23010.

Next when get home going to OTA update to 12 release retaining root and data.
[Google Pixel 5a] nijel8:
No luck with OTA sideload-vbmeta-boot update from 12b5 to 12 retaining data and root, had to wipe data to get the phone load Android. I think I should have flashed vbmeta and boot in bootloader, not in fastboot mode as the instructions say. Oh well... Next time...
[Google Pixel 5a] V0latyle:
If you disable /vbmeta after it was enabled, you have to wipe data. Booting the kernel seems to "lock" the status, so if you disabled vbmeta + wiped, then performed an update but didn't disable vbmeta, and rebooted - you'd have to wipe when you disable it again. So it wouldn't have made a difference, you would have had to wipe anyway.

For future updates, you can update either via OTA sideload or the factory image. DO NOT USE AUTOMATIC UPDATE.

For OTA, you would sideload the OTA, then IMMEDIATELY reboot into bootloader and reflash vbmeta, disabling verity and verification.

For the factory image, you would just perform the usual "fastboot update" but add the same --disable flags as you would for vbmeta.

In both cases, after the update is complete, you can patch and flash the boot image.
[Google Pixel 5a] nijel8:
I know all that and I did exactly what @HumorBaby did in this post https://xdaforums.com/t/guide-flash-magisk-on-android-12.4242959/page-15#post-85815505 and still got the recovery massage for corrupted data. My guess is vbmeta with disable verity and verify did not flash correctly in fastboot mode per his instructions. Should've done it in bootloader mode after sideloded OTA. And I was rooted on 12b5 so verity and verify was disabled before the upgrade to 12 release...

Edit: Just read your instructions and you say after sideloded OTA boot to bootloader for vbmeta and boot flash as I thought too... Not in fastboot mode as per @HumorBaby instructions!