yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6a] V0latyle:
Current updates have all the updates and fixes from previous releases

Automatic OTA is troublesome when rooted. You don't need to perform a complete uninstall in Magisk; just restore images before you take the update, and make sure that you go back into Magisk and patch the inactive slot before you reboot.
[Google Pixel 6a] G5-User7080:
yes, that restore original images thing is what I meant, I'm just sticking to the OTA guide from Magisk, thats why I booted the patched boot img and then direct installed through magisk too instead of just flashing it.

Just since I've never done an OTA update before Idk if it shows that updates are available with magisk installed.

Like, if the "restore images" before OTA refers to before I even click on Settings -> System update to check if theres an upate available or if I can like let it download first and then restore it before installation or smth.

It did show it for me now but that was directly after rebooting from updating with factory images, booting rooted boot image but it was before I even direct installed root through magisk.
[Google Pixel 6a] G5-User7080:
@V0latyle

mhh alright... I'm never doing OTA's again.

restored original boot.img through magisk, let the ota do its thine, instead of restart I went to magisk again and did "install to inactive slot" then reboot from magisk.

Except that it just showed "This device is corrupted" and when I pressed continue I was staring at a google logo and nothing happened.

So in the end I had to use android flash tool and wipe my phone cause normal fastboot firmware install didn't work.

Now its working and rooted again but the "This device is corrupted" message doesn't go away.

I even relocked the bootloader through android flash tool before I unlocked it and rooted like normal, but it's still there.

Is that like an addition from the last update? Now whenever I reboot there are 2 screens I have to click away,.. the normal unlocked warning and the corrupted screen.
[Google Pixel 6a] V0latyle:
Shouldn't have had to do that. If this happens just reflash the boot image using ADB. If that doesn't work...

Try sideloading the OTA. It appears that the "patch inactive slot" method in Magisk isn't working for everyone. Nothing is actually corrupt, the OTA update engine just isn't happy about something. Either way, wiping data shouldn't be necessary.

Don't EVER do this unless everything is 100% stock and the device has been fully wiped.

Nope, both screens are part of the Android Boot Flow.

Since the inactive slot method didn't work, I suggest sideloading the OTA in the future. Do not interrupt the process or attempt to flash anything. Let the update complete normally and boot; you won't have root. Assuming you already have a Magisk patched boot image handy (it doesn't have to be current), you can then reboot to bootloader and live boot the patched image, then perform Direct Install in Magisk.
[Google Pixel 6a] G5-User7080:
welp.. I tried flashing matching (so newest) boot, didnt work

you mean now? like after im factory reset & rooted I should sideload the same OTA again which I'm on right now?

Isn't that what android flash tool does?

wiping my device and install stock?

either way I wasnt running a custom rom and of course I don't relock it after I'm rooted.

So right now I should leave everything as is including the corrupted message, right?

Then when the next OTA comes I do nothing, keep root, no uninstall or restore through magisk, and I just download the newest OTA from google, and do the fastboot sideload thing?

It'll work even though my boot.img is rooted?

And then the OTA will remove root, I live boot my existing (eventually outdated) magisk patchet boot.img, then direct install as usual?
[Google Pixel 6a] G5-User7080:
This is slightly frustrating,... thanks for telling my my device is corrupted and making me think its actually bricked... nice going google.

I'm gonna have so much fun doing all the device settings again, cause for some reason restoring google backup doesn't do that.

How would I not hate OTA's after this lol
[Google Pixel 6a] V0latyle:
Yes. Sorry if it's confusing. The OTA update process can be a bit...sensitive.

Yes, but only if Wipe device is checked

Just sideload the OTA. It won't wipe anything and it can't possibly hurt anything.

Yes - when you update via system, it checks images for integrity before updating. Sideloading the OTA skips this and just overwrites the images. Doesn't affect user data.

Yep.

I can definitely understand the frustration. Suggestion: before you go nuclear next time and wipe your data, post here and see if someone might have a solution. I have a strong suspicion that simply sideloading the OTA would have cleared the corrupted message, you wouldn't have had to wipe data, and you could have just re-rooted. As the great Hitchhiker's Guide to the Galaxy tells us, "Don't Panic!"
[Google Pixel 6a] G5-User7080:
Sideloading went without issue, message still there though, but at this point idec anymore, thanks for the help!
[Google Pixel 6a] V0latyle:
The corrupt message is?

Hmm. Sideload again. Reason being is the OTA always installs to the inactive slot, then switches to that slot. If you install the OTA twice, it installs to both slots. Example: you're on slot A. Install OTA -> slot B becomes active, Slot A hasn't been updated. Install OTA again, -> Slot A becomes active.

Just to make sure - you're using Magisk 25.2, yes?
[Google Pixel 6a] G5-User7080:
Latest release, yes.

No worky, was on slot a before, so it did ota and switched to b, b wasnt rooted, I rooted it through magisk, did the ota again, so it switched back to a, rebooted, a wasnt rooted as expected and the message was still there.

just to confirm that it actually switched and didnt like ota 2 times without switching, I switched back to b and it was rooted.

Can only guess it only works if the ota actually installs anything, i mean im already on february 5th on both slots.

So I'll try again next month.
[Google Pixel 6a] Lughnasadh:
The message should disappear when you update the OS next month.
[Google Pixel 6a] frank93:
what works best for me (!) is downloading the whole factory image, extracting boot.img, patching it using magisk, transferring it back to the pc, and there editing flash-all.bat so it doesn’t wipe data (!) and adding one line to flash the new boot.img directly at the end. reboot to bootloader, run flash-all, done.
[Google Pixel 6a] mike.s:
Just use PixelFlasher. It will take care of everything, including Magisk patching the boot image. Makes updates using the factory images painless, takes about 5 minutes total.
[Google Pixel 6a] V0latyle:
@G5-User7080 I'm bringing this to public as discussed in PM.

Yes, you can force a full factory flash. Yes, the flash-all script and the Android Flash Tool both do this - they flash bootloader, radio, and all OS partitions. If you want to be really thorough, you can check the "Force flash all partitions" checkbox, this also requires a data wipe.

I'm not sure why system apps would remain disabled following a data wipe.

The Google One backup isn't able to back up everything. It cannot back up application data, and it does not back up all system settings.

Regarding the screen, I've noticed the opposite with my Pixel 5. I have "Stay Awake" turned off, but despite having my screen timeout set for 1 minute, it turns off and locks after about 15 seconds.

Battery...Not sure what to tell you.

Consumer electronics are cantankerous beasts indeed and fraught with gremlins.
[Google Pixel 6a] G5-User7080:
I couldnt think of any other way that some apps retain their disabled state, as well as why would the corrupted message stay even after full stock / full OTA on both slots.

Only thing I can think of is that fastboot update does not overwrite partitions that are already the same version.

Do you think enforcing all partitions flash would get rid of the corrupted warning as well?

As for the google one backup,.. it said it would restore settings, even if its not all of them,.. i dont think it restored any.

sound, display, permissions, gestures, gboard, etc, was all different.
[Google Pixel 6a] V0latyle:
Pretty sure it does. I could be wrong.

In theory, yes. Google hasn't exactly released any in depth documentation for the Android Flash Tool. Note that force flashing all partitions will include a data wipe but it's worth a try

Only thing I can think of is you might have selected a backup that was incomplete or something. Google One takes "snapshots" every once in a while, including after you've signed into Google on your device.

Otherwise, the backup just didn't restore completely?
[Google Pixel 6a] Lughnasadh:
Fastboot does but I don't think Android Flash Tool does unless you select "Force Flash Partitions".

I'm pretty sure the information part of "Force Flash Partitions" says "Flash all partitions that are part of the build even if they are up to date (e.g. bootloader, radio) as well as force a wipe".

At least this language leaves me to believe that that Android Flash Tool won't overwrite partitions that are already up-to-date unless you select "Force Flash Partitions".
[Google Pixel 6a] G5-User7080:
mhh im trying it right now, but "force flash partitions" is checked by default, so I did that last time for sure.

Edit: used pixel flasher, set to flash to both slots, newest firmware, did go basically like android flash tool, showed in the console that it flashed all partitions, did it 2 times for slot a and b.

This corrupted message is still there, the three apps that were priviously disabled are enabled again, and google one backup still doesn't feel like restoring my settings.

what a pain really. good this is the last week before break..
[Google Pixel 6a] G5-User7080:
After googling the corrupted error message some google help site said to contact their support.

So I did, and they told me to send it in so they can repair it.

So I'm gonna do that, now I'm wondering if I should relock the bootloader before sending it back, as far as I'm aware google doesn't void your warranty by unlocking your bootloader, and I also mentioned to the support that I have already tried flashing full factory firmware, so I'd have had to unlock the bootloader for that and they didn't say anything.

I'm still don't get how this message appeared in the first place.

What does cause this message to appear normally?

I read something about when it fails to either encrypt or decrypt data, but that should be fixed after wiping data... so.

The things I did were:

1. flash factory firmware of the same version I was on to ensure system is stock, without -w option to keep data. Then live booted magisk patched boot as normal.

2. saw that OTA was available now so maybe there really was something about my system being modified, I'll post my magisk modules below.

3. Immediately paused the OTA after seeing it was available so I could do the "official OTA with magisk restore images" thing

4. direct installed root through magisk and rebooted.

5. did everything as it is in the magisk OTA guide, went to magisk -> uninstall -> restore images, then went to OTA started/continued downloading it and waited for it to complete. When completed I went back to magisk and did "install to other slot" and then clicked the reboot button in magisk.

6. I was greeted with the "your device is corrupted" screen and past it I was staring at the google logo and nothing happened.

7. googling the corrupted message I read that the only way out was a complete reset with android flash tool with wipe, so I did that and yea... so on

I didn't uninstall any magisk modules, I only clicked on "restore images" as thats what was written in the Magisk OTA guide, so I assumed restoring the images would naturally remove root and disable all modules.

That said after just flashing stock and only rooting I didn't have any modules installed, they would only explain why I didn't get the offer to OTA before flashing stock.

The modules I used were

safetynet-fix mod by displax v2.3.1 / safetynet-fix by kdrag0n v2.4.0

dss - disable app analytics / measurement / firebase (only applied to user apps with dss disable user)

Shamiko

LsPosed and HideMyApplist

Fullscreen Immersive Gestures

Advanced Charging Controller

Storage Isolation Zygisk module

Magisk own Systemless Host module

The three apps that I couldnt re-enable after accidentally copying the wrong command (pm disable-user --user 0)

com.android.sdm.plugins.diagmon

com.android.sdm.plugins.dcmo

com.android.sdm.plugins.connmo

That said, OTA doesn't even start if anything is wrong with things it needs,.. so if it needed those apps, I didn't disable them after the flash, they were already / still disabled, meaning it started while seeing they were disabled and didn't judge them as problem.
[Google Pixel 6a] absan:
I have a problem with system update. Anyone know how to solve this
[Google Pixel 6a] G5-User7080:
looks like whichever app system update is is crashing.

did you remove / disable any apps?
[Google Pixel 6a] absan:
Yes found the Font manager module block the system update
[Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe] King081:
Features are

Added MGLRU: Disabled by default

KernelSU: A magisk replacement that doesn't break safetynet

Optimized EXT4 FS

Erofs support (only used if ROMs support it)

Optimised networking

Adjusted some power stuff

Added DevFreq boosting to improve smoothness and jitter

Reduced system latency

Simple LMK added (thanks to sultanxda)

Improved GPU stuff

Optimised governors

Improved battery idle drain

Reduced memory leaks

Improved UFS

Upstreamed to .271

Only to be used on CUSTOM ROMS THAT ARE ON ANDROID 12 & 13

Telegram support

Kernel Sauce

https://github.com/XperiaBrickers/kernel_sony_sm8250
[Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe] King081:
Also this one
[Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe] King081:
Last one I promise
[Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe] Yoannjap:
Does this work with any pdx06 kyasu lineageOS A13 version?

Can we apply after any OTA?

Could you give please an step-by-step installation process?

Thanks a lot.
[Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe] King081:
OTA should work, I've never used Kyasus lineage, instructions are Fastboot flash boot_a boot.img

Fastboot flash boot_b boot.img
[Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe] Yoannjap:
Thanks for your answer !

You write Only to be used on ‘CUSTOM ROMS THAT ARE ON ANDROID 12 & 13’

Which ones, so ?

Or maybe you mean that it works with any A12/A13 ROM except stock A10/A11/A12 ones ?
[Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe] King081:
Only custom ROMs like corvus etc, it will boot fine on stock but has issues like throwing up an error and reduce the performance
[Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe] aveilleux:
Is it possible to download this without joining your Telegram group?
[Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe] King081:
Will Be closed soon since I don't have the device anymore
[Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe] 森泽黑川:
<Mod Translations>

English:

Why can't I enter Arcana?

********************

Chinese (Simplified):

怎么刷不进阿尔卡纳？
[Xiaomi 12 Pro] samanthamansa:
Hi everyone...

I've updated my phone from MIUI 13 (stable global rom) to MIUI 14 via OTA, installed Magisk via the OTA option, and then reboot the phone in Magisk.

Then, the phone keeps showing the boot up screen (black ground with a white MI icon only) for a while, and shows a screen with following options: reboot, wipe data, connect to MI assistance, and safe mode.

I tried reboot and safe mode, but both return to the screen with 4-options above.

Now my phone got stuck in the bootloop.

What should I do? :eek: Does anyone encounter the same problem and fixed?

Thank you.

My phone's details:

- Xiaomi 12 pro Chinese model

- Bootloader unlocked

- MIUI global stable rom

- Magisk v25.2 installed

- No TWRP
[Xiaomi 12 Pro] NOSS8:
Try to flash the TWRP and a recovery rom.
[Xiaomi 12 Pro] samanthamansa:
Will it wipe the data? Because I have no data backup...
[Xiaomi 12 Pro] NOSS8:
At first no, flash the same rom currently on the phone but if that does not work you will have to format the data.

Tried a backup with the TWRP on OTG key.
[Xiaomi 12 Pro] samanthamansa:
For "the rom currently on the phone", do you mean MIUI 14?
[Xiaomi 12 Pro] NOSS8:
yep..
[Xiaomi 12 Pro] samanthamansa:
Thank you for your help. At the end I flashed the recovery rom but still entered the bootloop. So I wiped that data and start over.
[Google Pixel 7] LeoPeink:
Hi everyone! I have a rooted Pixel 7, with Magisk working perfectly. The only issue i have is with Google Wallet, even SafetyNetFix and Zygisk hide list didn't work. Can anyone with a rooted A13 device pay contactless?
[Google Pixel 7] dmbardal:
Yes, it works perfectly with GPay/GWallet.

You shouldn't need to do anything else after enabling Zygisk, installing SafetyNetFix, then test if it passes the tests.

Which it should. If it doesn't, use the 2.3.1_MOD2-fix, not 2.4.0.

Had issues with 2.4.0 being inconsistent.

Download 'YASNAC' from the store, and run the test.

Does everything work?

If no, install 2.3.1_MOD2.

If yes, make sure you kill playstore and then wipe storage and buffer.

Do the same for gpay/wallet.

Reboot, and it should work.

Nothing should be added to the Zygisk hide-list.
[Google Pixel 7] efkosk:
Hi,

I also had the same problem.

Then I deleted the latest safetynetfix and used the version: v2.3.1

It works fine with this.
[Google Pixel 7] LeoPeink:
Google Wallet still no worky after installing v2.3.1. Where can i find 2.3.1_MOD2?
[Google Pixel 7] dmbardal:
https://xdaforums.com/attachments/safetynet-fix-v2-3-1-mod_2-1-zip.5795137/

Link to comment by Displax:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-87198517
[Google Pixel 7] LeoPeink:
Installed 2.3.1_mod2.

YASNAC gives me "pass" on Basic Integrity but "Fail" on CTS profile match.

Google Wallet still gives me the "your device does not meet security requirements to pay contactless".

Any further advice? :(

EDIT: Hide Props Configuration Module is configured to spoof the device as a Pixel 6.

EDIT 2: I will install the Feburary update on my rooted phone, I'll retry when it is up to date so i dont have to mess with fingerprints. Thank you who helped :)
[Google Pixel 7] salamdiab:
not work with me
[Google Pixel 7] dmbardal:
Dont use props-modules.

Can you post your setup?

Like I've posted mine here
[Google Pixel 7] salamdiab:
View attachment 5830873 View attachment 5830857 View attachment 5830863
[Google Pixel 7] seanho12345:
Here's my current Magisk hidelist and module setup. I'm using Shamiko for hiding apps from root
[Google Pixel 7] canibuz:
I've had gpay working this entire time used it yesterday around 6PM EST. This morning went to the gas station and got the error the device doesn't meet the software requirements.

Just saw the update for Shimako and Safety net fix. Just ran it and cleared Gpay and Google Play. All looks good just need to test it out now.
[Google Pixel 7] LeoPeink:
I'll try again later with Shimako.

To test Google Wallet, you can remove your credit card and add it back: if it does not give you the "unable to pay contactless on this device" you should be clear.
[Google Pixel 7] canibuz:
Just tested it out and it failed.
[Google Pixel 7] seanho12345:
Can confirm that the new 3.0 MOD from Displax works flawlessly. I just installed it and everything is working.

https://github.com/Displax/safetynet-fix/releases/download/v2.3.1-MOD_3.0/safetynet-fix-v2.3.1-MOD_3.0.zip
[Google Pixel 7] LeoPeink:
Ok it passes tests and lets me add a card to Google Wallet without warnings. I'll try to pay ASAP :)
[Google Pixel 7] Dopamin3:
If anyone else sees this thread, keep up to date here: https://github.com/Displax/safetynet-fix/releases

The latest version is v2.4.0-MOD_1.2 and works across all devices (not just Google Pixel) for passing safetynet / google pay etc...
[Google Pixel 7] drazil22:
Is there an update to fix Wallet on Pixel7? I've never gotten tap to pay to work, it has only ever worked to pay inside of apps. Whenever I open Wallet, and go to "Tap to pay setup", it says "Phone doesn't meet security requirements".

YASNAC shows Pass/Pass/BASIC.

I've tried every single Magisk module in this thread (the ones listed by fellow members, and the updated versions), Shamiko v1.0.1 (300), Zygisk - LSPosed

I've cleared the data for Google Play Store, Google Play Services, Google Wallet

Now it's forgotten the card I added and won't let me add it back :(

is there some magic part that I am missing? I'd love to finally be able to use tap to pay.
[Google Pixel 7] ldeveraux:
This thread had worked for me since it started:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[General Questions and Answers] kingofkicks:
I am trying to extract all of the old, deleted pictures and videos and I can't find any way to get the drivers necessary to start. Please help. there were irreplaceable photos and videos in that phone that could possibly be recovered.
[General Questions and Answers] alecxs:
no need to root the device. just install TWRP

https://xdaforums.com/t/recovery-golden-twrp-3-x.2748327

then pull the files from adb with platform-tools

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

drivers here

Get the Google USB Driver | Android Studio | Android Developers

The Google USB Driver is required to perform adb debugging on Windows with Google devices.

developer.android.com