yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Official announcement from Google or just blah, blah from somebody without the knowledge about Play Integrity, PIF, etc - who then 'simplifies' stating that unlocked BL blocks RCS?

On nowadays Internet everything can be published, and then it just spreads out, specially if bombastic enough to gain likes and visits

Or from the other angle, it's ok for eg USA Today - obviously it's not expected that readers would (and the journalist) would know/be interested to read about Magisk, PIF, faking Device Integrity, etc, hence it's ok for that type of source to publish there as that
[Magisk] Wolfcity:
Everything working fine as expected.

Xiaomi mi 9T running xiaomi.eu 12.5.2, Magisk stable 27.
[Magisk] zgfg:
Yeah, if he unlocks BL but doesn't root to install PIF to spoof Play Integrity...

Then the news spread out, saying that Google blocks everything for ppl who just unlock BL😁
[Magisk] osm0sis:
Again, Invalid Uri has nothing to do with my module, it's just that your ROM file picker gave Magisk an incorrect location when you tried to choose the file to flash.

You just need to be logged into GitHub to download Actions CI builds.
[Magisk] Lughnasadh:
Yes. I explained it to you already in Post #12,437.

EDIT: Could be an LSposed problem that's causing the issue with HMA on March update.
[Magisk] osm0sis:
Any Pixel 8 Pro users in here getting OTAs normally still? I was stuck on December until I manually sideloaded February, and now I just checked for March and it said "Preparing system update..." briefly and then disappeared and checking again shows "up to date" . Wondering if they've started blocking OTAs on unlocked/rooted devices as well. 🤨🤔😕
[Magisk] Vision:
You have a point, i agree with that, is rumours or truth ?!
[Magisk] fbirraque:
GPay Checker: monitor of Google Pay availability

Google Play Protect now triggers onto app (that's honor for me), but here nothing criminal. You can safely skip warning. There is non-zero theoretical possibility, that using this app increases risk of banning your personal fingerprint. There...

xdaforums.com
[Magisk] osm0sis:
Problem with that is that by the time Wallet has caught the failure you've already been failing for at least 12 hours.

Better move would probably be to let Xiaomi.eu continue to do the heavy lifting, and just subscribe to/watch the RSS feed for their PI spoof injector app updates: https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/rss?path=/xiaomi.eu/Xiaomi.eu-app
[Magisk] Vision:
I read from a user say can't update from A13 to A14 because have unlocked BL, until now i know can update your ROM with unlocked BL from the device
[Magisk] fbirraque:
I totally agree with you.

It'll warning the FP before NFC Payment fail only if didn't use it in the past 12 hours. Otherwise the notification will happen together with the NFC Payment fail. 🤷
[Magisk] linuxares:
I always had issues with that since magisk image even if I restored (Pixel 7 Pro, haven't factory reset so might be something with my phone) but I just use Pixelflasher now days and it just works.
[Magisk] BillGoss:
Thanks for your suggestion. In the process of doing this (which didn't work) I noticed that there were some errors when I reinstalled PIFork (see screenshot).

So I re-ran autopif.sh but got the same pif.json as I was already using.

Then I remembered that @osm0sis has a long version of autopif.sh (https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89233630) and a short version (https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89233630) which I had been using.

So I ran the long version and it gave me a fuller version of pif.json and when I used this one, I'm back to passing BASIC and DEVICE integrity.

So the difference between my two phones is that the OnePlus 8T passes integrity with the short pif.json format and the Pixel 8 Pro only passes integrity with the long pif.json format.
[Magisk] zgfg:
Ok, have you previously manually downloaded a module zip file and installed from the Magisk app

Have you also manually opened the zip file to make sure it was correctly download

Try to download/manually install another module/it's zip installation file

If you would have the same probkem, maybe it's up to your file manager - we have seen similar problems with other modules and in other Magisk related threads

Magisk uses your default file manager, some do not handle zip files correctly.

You can try to install another file manager
[Magisk] zgfg:
You can always run migrate sh script that comes with the PI Fork module - it will expand the 'compact' json file to the 'full-size'

Acrually the autopif.script calls migrate sh (look to the end of the script). However, in some cases (not gouing to the details now), migrate sh does not run and you remain with 'compact' pif.json

Make sure you use the latest migrate sh
[Magisk] justdidit:
Hi, what do you mean by long and short versions? The links you provide in brackets are the same.
[Magisk] t3chg33k:
I started facing a similar issue around last October on a 6a. I think the November OTA was the last one I was able to install with Magisk. Thereafter, only once I could see the update notification that disappeared later.

Manually installed the OTA from my PC for December but didn't get the OTA on the device for Jan or Feb. Eventually restored and locked the bootloader in Feb and the March update installed fine.

So, Google is definitely clamping down on root aggressively now, in terms of updates and also apps.
[Magisk] knoedelcc:
And I thought there was something wrong with my setup.... Google Pixel 6a (Germany/D1). I've been updating manually for months now.
[Magisk] HippoMan:
I, for one, would very much prefer a no-OTA-for-modded-phones policy.

Given the level of modding that I always prefer, standard Android OTA installation can sometimes either force me to waste time in order to re-do my modding, or it might even get me into a bootloop.

And I hate having to periodically respond to the annoying pop-ups I'm getting these days which tell me that I should update my OS whenever a newer version of my OS is available.

I'm perfectly happy to download and then manually install any OTA's or OS upgrades that I might decide on.

But, of course, I'm not exactly a typical modded Android user.
[Magisk] BillGoss:
You are correct. The links are the same - my mistake ☹️

But that post has
[Magisk] Vision:
I read from a user say can't update from A13 to A14 because have unlocked BL, until now i know can update your ROM with unlocked BL from the device with OTA, now i think like you say Google make changes again, but changes for us, i think in latest Android make like Android 15 etc. want force us not have a option for unlock BL etc.
[Magisk] pndwal:
Guess it could be an app development issue... Firebase App Check uses Play Integrity API and polls deviceIntegrity labels apparently, but seems it's mainly concerned with appIntegrity labels that are part the reason SafetyNet was expanded to become (the more inclusive) Play Integrity... and your error indicates "app attestation" is failing.

I don't know much about Firebase app/integrity attestation integration, but Doc says:

https://firebase.google.com/docs/app-check

Hope some clues here. 🤠 PW
[Magisk] FrogMaster-:
In the post itself there is a preview of the script which was the initial script that osm0sis had created. Attached to that same post is an updated version of that script, which is much longer than the original due to the additional updates.
[Magisk] justdidit:
Thanks for the disclaimer. I resolved my issues by running migrate.sh after autopif.sh.
[Magisk] pndwal:
I posted about some progress with this a while back... POC discussed here:

https://xdaforums.com/t/info-play-integrity-api-replacement-for-safetynet.4479337/post-89125128

I don't recall coming accross much more on this recently... Perhaps you could take a look at that project/links and let us know about any more recent developments. 👍 PW

Edit: Seems like not much has happened in JAMBOREE (Java Android Magisk Burp Objection Root Emulator Easy) project since POC video, but it's still on wishlist:

https://github.com/freeload101/Java...bjection-Root-Emulator-Easy#features--request
[Magisk] zgfg:
FYI

https://xiaomi.eu/community/threads/miui-14-stable-release.67685/post-719998
[Magisk] Vision:
The strange is, the Netflix app and others if not pass, not show it in Google Play in real phone, but in 1 emulator i test, i show the Netflix and other apps and download normal the Netflix but after open it say not compatible but unlike real phone not even show, if not pass the check, and of course i test the emulator error getting token without modules
[Magisk] Vision:
Again with Strong 🥲
[Magisk] osm0sis:
Thanks for confirming!

Judging by size I think I recall the last OTA I received (December) appeared to be a Full OTA (i.e. had only full images inside, not an Incremental OTA that contains diffs), so I was wondering if Google had adopted a similar approach to OnePlus and were detecting unlocked/rooted to only serve Incremental OTAs to locked devices, with the Full OTAs being available only to unlocked/rooted, but fewer and far between. The other worry would be that they just stopped serving OTAs altogether to unlocked/rooted devices.

This was possible to work around with OnePlus by putting their separate OTA updater on Magisk's DenyList (either Enforced, or not, by using Shamiko), and then it'd serve the Incremental OTAs again.

I'll have to experiment with putting Google Play Services and/or Settings on my DenyList with Shamiko (since I believe GMS mediates OTAs now) and see if that brings back anything... 🤞
[Magisk] pndwal:
If you're still looking for official app reversed and with domains updated, it's now endorsed by XDA, but only for internal distribution... Working as well as original for me, but don't expect much in the way of further updates w/o source. Thanks again to @dr.ketan! 👍:

Thread '[18.01.24] [NEW] XDA Forum Apps I Official with Domain Fix + Unofficial' https://xdaforums.com/t/18-01-24-new-xda-forum-apps-i-official-with-domain-fix-unofficial.4199599/

Sorry for the (slightly less) OT (than merits of vapes for those trying to get free from tobacco habit) folks, but I love the fixed app... (Nb. I use both app and browser however since both have serious limitations)... 🤠 PW
[Magisk] Vision:
@chiteroman Again with Strong, just we want to know you're so perfect dev and you can mod your ROM and pass 3/3 for private use ? Or something else ? 🥺🤔

View attachment 6076730View attachment 6076731View attachment 6076732
[Magisk] Nergal di Cuthah:
Same
[Magisk] Vision:
Thanks for this useful info, now i have all the opinions from all the great devs. I appreciate
[Magisk] niko26:
Has been like that for ages for me... P4, P6P, P7P. It worked maybe once or twice. :(
[Magisk] zgfg:
Full OTA wtites over and does not care about the details

Incremental OTA must compare the files to make sure what to update and how

When booting with Magisk snd the modules enabled, system appears modified (although Systemless modules did not do hard changes and hard changes are not even possible if System is read-only as most-likely it is)

Hence, as you mentioned, to proceed with Incremental OTA on the live, rooted system - you must 'hide'

And not necessarily bcs they really chase the root, unlocked BL etc, but as it is called in Magisk Delta (Kitsune), you must 'Unmount modules' that the Updater can see the original, untouched System, that the files and folders look as it expects, that it can apply the proper Incremental OTA
[Magisk] Vision:
Yeah, why bother for install OTA with Magisk and problems are occuring.

For that (in past) i do the most simple thing before OTA update, i uninstall the Magisk Delta (kitsune) and download OTA, reboot phone and wait to finished the update and done, after flash again the Magisk
[Magisk] zgfg:
Probably just flashing the iriginal, not patched boot img should work.

System will boot with no systemless changes and should be able to properly apply even the Incremental OTA

Om the systems with custom recocveries it's easier, doenload the OTA zip and flash through TWR. TWRP 'sees' the iriginal, untiuched System
[Magisk] Vision:
Yeah exactly this i do, i flash the original boot.img, download OTA and wait for update all done, after i patch the boot img with Magisk Delta and flash, so simple
[Magisk] Captain_Throwback:
TWRP can't always install an OTA zip; it's dependent on the type of device setup and type of OTA zip. For example, incremental zips for Virtual AB devices cannot always be installed successfully.

It's more reliable to use whatever OEM update mechanism is in place, if available when unlocked/rooted.
[Magisk] rseiler:
If you have "Automatically resend as text (SMS/MMS)" enabled, but guess what, it's disabled by default.

Worse news: It has a spotty record of success even when it is on: I'm beginning to think that RCS is better left disabled. Two birds, one stone.

https://www.reddit.com/r/GoogleMessages/comments/12n55tl
[Magisk] Vision:
Yeah exactly this i say, Automatically resend as text (SMS/MMS) for now is disabled by default but we can enable it if we want but i think Google want force to disable this feature for ever, and for that if one user with normal phone send a RCS message to other user with unlock BL/Root and can't take it, the auto feature is gone and can't resend anymore as text (SMS/MMS)

And like this Google enforced to stop from unlock BL/Root our phone

If all this exists with the Google message and not rumour
[Magisk] osm0sis:
OTAs operate on the partitions, not the files (nowadays), so all that's necessary is to restore stock images in Magisk app and Incremental OTAs will work.
[Magisk] intel_core_i7:
Nobody will really know because it will stop working right at the time the method goes public.
[Magisk] asisandroid:
Theoretically, could not someone who has a strong integrity method (or even a device one if this one gets "patched" in future) just make a farm for passing integrity. Then we install some open source thing for proxying our integrity requests to the one with the bypass, the one with the bypass can then do the successful integrity request. (For a small fee or something)

Meaning we would pass the integrity without the whatever method existing being public.
[Magisk] Anchewei:
Got it, I can open those apps if I remove them from HMA, but still can't use some functionality because it detects root.

I guess I wait for the developer to fix this...
[Magisk] WhoIsJohnGalt1979:
Not sure if this would actually fix the issue, however, would you be able to remove HMA as in uninstall the app, delete the HMA folder entry in data/system/HMAXXXX. Disable remove lsposed from magisk and reboot phone. Then flash the official lsposed from https://github.com/LSPosed/LSPosed/releases/download/v1.9.2/LSPosed-v1.9.2-7024-zygisk-release.zip and set up HMA again and see if it works. Now that I think about it, why not start with downgrading lsposed version from whatever you have to the above official version and check. If it doesnt make a difference, uninstall HMA and set it up again. Now am bypassing a lot of variables here, how many lsposed modules you have, what version of lsposed you are on. But I did read a user on the HMA thread report that he was able to undo the damage by go back to official lsposed. No harm in trying.
[Magisk] jabennett:
Well, guess I'm glad to know I didn't do anything wrong to cause this on my P8P (aside from violating the new unwritten, "No User-Serviceable Software Inside" policy, I guess. Still stuck on December here, too. 🤨
[Magisk] jabennett:
Yeah, I had finally gotten confident in performing OTA updates right on my phone, without losing root:

Disable automatic reboot on system update

Uninstall Magisk (restore stock images) in Manager

Download OTA

Install update - DON'T reboot

Reinstall Magisk to alternate slot and reboot.

Simple and reliable enough, until Google apparently decided to stop even offering up OTAs to me anymore. 🙄
[Magisk] Nergal di Cuthah:
Ok we are really OT here, but why are pixel users trying to take ota and unroot before et al.

My pixel monthly takes 20 min. Download the updates zip to pc,

get boot image and put on phone

Run the update with google's flash tool

Restart phone let update finish (there's a notification)

Patch boot and move back to pc

Fastboot flash the modified boot.

I haven't taken a ota since nexus 6 or maybe ever.
[Magisk] osm0sis:
Exactly. And Magisk just fixed it again too (should be in the *next* canary):

Prompt users to use reboot button in System Updates · topjohnwu/Magisk@4d5510b

So the update engine can write verify info of partitions which fixes bootloop on newer Pixel devices

github.com

Anyway, I've had no luck with getting the OTA served to me from any of my DenyList + Shamiko tests so far. 🤷‍♂️

Just the having cake and eating it too of it all. 😛

Not needing a PC to update is the main attraction.
[Magisk] jabennett:
It was nice being able to do it without a PC, for one thing. 🤷🏻‍♂️
[Magisk] osm0sis:
Well, to bring it full circle and get somewhat back on topic, I would definitely be curious to know if anyone who isn't using a PIF module, but is still unlocked/rooted, is having this OTA problem. 🤔
[Magisk] Nergal di Cuthah:
@roirraW "edor" ehT might be the best to ask or @V0latyle as both have thumbs in all/most pixel boards.
[Magisk] manjaroid:
Your auto OTA description is how I remember Pixel 6 and maybe Pixel 7 in its early days. i.e. Before PIF modules replaced safetynet-fix modules. My memory is foggy and may be getting it wrong about 7, but with 6 updates over-the-air did exactly what you described. I didn't give it much thought and sideloading (or factory with fastboot) became habit. So this may not be related to PIF at all and may be more about unlocked/rooted Pixels.
[Magisk] sir_bazz:
Haven't caught up with all the new posts yet, but incase you're still looking for feedback....

No issues on Poco F5 Global running xiaomi.eu HyperOS. (None on v7 either for what it's worth).
[Magisk] zgfg:
True but incremental OTA does not flash the whole filesystem, hence it inspects what do you have in advance, before flashing

So we come to the original point. It's not that Google or somebody bans (partial) OTA on the rooted phones (one more Google's sin or plot against the hackers) but the Updater needs the original system to properly work with
[Magisk] intel_core_i7:
Did xda just went facebook today? Had some "bad gateway" screens trying to access the page an hour ago
[Magisk] Claus….:
Thanks @pndwal , I will make further research on this and see what we can do. I will update you, but it will take some time.
[Magisk] Claus….:
Yes, me too.
[Magisk] jrotaetxe:
False Alarm. Sorry
[Magisk] BillGoss:
Still ok for me.
[Magisk] markos365:
I have a Pixel 8 with the February OTA installed. I rooted it last week so I just had to disable Automatic system updates because I was getting the OTA.

I'm in Europe so the OTA ban may be a region thing? I attached my list of installed modules.

Also, I get why people want to update directly from the phone but why is people using anything but Pixel Flasher on PC? You can download, patch and flash the OTA in just a few clicks. Is there any disadvantages to PF or it's just personal preference?
[Magisk] Anchewei:
After trying this, it doesn't work.

I have also tried to downgrade LSposed to 1.9.1, but the issue is still here.

I uninstall HMA by deleting /data/system/hide_my_applist*, but also try to clean the runtime environment in its setting first, then reinstall it, which both don't work.

The weird thing is that whenever I reinstall HMA, my old configuration is still here, so I'm guessing I didn't fully clean its data.

My LSposed modules: HMA, Hide mock location and pixel xpert.
[Magisk] osm0sis:
And my point that unlocked with restored images via Magisk app is the original system, because the underlying system partitions are untouched (hence "systemless" root/mods).

I took the November Incremental OTA that way without issue before getting stuck on December after the December (Full?) OTA through whatever changed at that time.
[Magisk] Vision:
Yeah, i know for that only ask from @chiteroman if it is possible to mod the ROM and pass 3/3 or something else but without tell us what is exactly.

Just to us know and maybe someone else make this same for private use of course
[Magisk] Vision:
Yeah, this works for me, only the original boot.img and the OTA update finish and all done, flash again the patch boot.img
[Magisk] Vision:
Look in /misc and /data/adb
[Magisk] Vision:
@osm0sis I don't remember exactly, but one user report can't make OTA update with unlocked BL, first time i hear that, i think Google make some changes and if detect unlocked BL can't install the OTA, in new devices who still get new OTA, because in my Xiaomi Poco X3 NFC still get OTA (Old) and say to update to latest A11 i have do it with success, only flash the original boot.img before, and all done
[Magisk] pershoot:
@osm0sis I dont recall ever getting an OTA notification on 7a (current). On previous (4a5g), I believe I may have received, towards the beginning to mid. of owning it, but dont recall ever receiving one towards the mid to end of its life. Both devices BL unlocked promptly, after it was in my hands.
[Magisk] mindtrappergr:
@osm0sis Can I add code to kill gms and gms.unstable in your autopif script? I place it in the module folder, so the custom JSON file is downloaded there.

Edit: yes, it works. Next maybe I'll try adding code to move custom JSON to the correct folder so autopif.sh can be run from anywhere.
[Magisk] pershoot:
You can create an alias and place it in your shell interpreter's .rc file. You can then invoke it after a script runs.
[Magisk] pndwal:
Yeah, so seems things may be changing, and I wonder how pre-newOS-boot checks as well as post reboot checks are done (if partition digest calculation or other checks are made using partition blocks directly, or from filesystem as seen by update engine which apparently didn't occur before on Pixels and may reflect Magisk (systemless) modifications, etc) now, also what's changed...

Regarding @canyie's new fix (merged but only built as CI ATM), that may apparently fix OTA issues when using 'Flash to inactive slot' to retain root but I wonder if other considerations and prerequisites must be met as your findings seem to indicate...

Anyway, vv suggested some time ago (mid 2022) that the fix for bootloop after OTA using Magisk retention method for late Pixel 6+ OTAs

https://github.com/topjohnwu/Magisk/issues/5959#issuecomment-1152869296

... Seems to me that @canyie's fix comments indicate that this may not have been properly understood, and that failing to reboot via update engine (ie. verity information is absent/not written) may be the key problem with verity checks failing post-reboot rather than the verity info (digest calculation) being affected by Magisk injection... Likely simply allowing the update engine to handle the reboot may trigger pre-reboot partition digest calculation(s) at that point (which would include Magisk patch in /boot or /init_boot), and that allows post-OTA/reboot verifications and booting to succeed:

https://github.com/topjohnwu/Magisk/commit/4d5510be4fbd9755966064f7d678cad3b3dadf90

If this fix works as expected, I expect to see this step in ota.md doc:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md#devices-with-ab-partitions

ammended per the new prompt:

console.add(" Next reboot will boot to second slot!")

... I suspect further fixes/understanding may still being needed... it'll be interesting to get feedback about how this works when someone reports after rebooting via system update engine. 👀 PW
[Magisk] osm0sis:
I can confirm the Pixel behavior with the OTAs I received after unlocking, where Flash to Inactive would bootloop, but then simply fastboot flashing the patched init_boot.img and marking the slot good got it working on the updated slot. So if I could actually get it to serve me another OTA ever again, it sounds like canyie's fix might do the trick. 🤷‍♂️