yashsingh1/xdaforums huggingface dataset:
[Android TV General] LUYULKMOIO:
I just tested the speed of wifi 6, it works a little better than the original (136 Mbps).
[Android TV General] LUYULKMOIO:
Just for fancy :
[Android TV General] Mauricio Pfleger:
Hi. I have 02 H96MAX S905W2 (2/16 and 4/32). If someone need this original ROM only said to me how to make this firmaware extract.

Sorry my english...
[Android TV General] LUYULKMOIO:
hello mauricio, can you say how did you do to make the firmware?
[Android TV General] LITUATUI:
Latest firmware here.

Only tested on 4/64 GB version, other versions might be problematic.
[Android TV General] UrsoDasNeve:
Hello, good afternoon, this rom already comes with root magisk, I have the original rom and wanted to make a backup, is there any way to do it with a program or twrp?
[Android TV General] najibyanouri:
Good morning,

would you like to post us the original rome of version 4.64 thank you
[Android TV General] h003:
Hello,

I have a h96max s905w2 with 4gb/32gb.

I tried yo install slimboxtv (LITUATUI link) and maybe I did something wrong, because the tv box starts with slimboxtv logo, but after that It tries do "erasing" and It fails and restart. Indeed, if I go to recovery mode, I have the same error when doing "data wipe". I suspect that It is bricked.

Has someone the original firmware for the h96max s905w2?

I tried different w2 firmware options (vontar, tanix, etc) and i have always the same error.

Any ideas?

@LITUATUI, how do you so the installation? Amlogic USB burning tool? Versión? Could yoy tell me the main steps that you apply?

Thanks in advance.
[Android TV General] LITUATUI:
According to this topic, there is no slimBOXtv rom compatible with the 4/32 GB version.

"There is no suitable Slimbox firmware for the 4/32 version of the console."

As far as I know, some devices have different internal hardware that make them incompatible.
[Android TV General] h003:
@LITUATUI thanks for the reply.

FYI

I have tested several sbx firmwares last days for h96max 4/32: vontar, tanix, t95,...

the only one that is working is sbx for x98 plus (11.17 versión). Wifi not working and led is always red. Ethernet works. Not expected result,but at least It works.

thanks!
[Android TV General] LITUATUI:
Try asking the seller for the original firmware. I tried but had no luck.
[Android TV General] LITUATUI:
New 11.18 version. Only tested on a 4/64 GB device.

Differences from official slimBOXtv firmware.

Device name fixed (H96 Max W2 instead of Vontar X2)

LED color fixed

AdAway and NeoBackup installed

Download
[Samsung Galaxy S23 Ultra] tim84us:
i am really jealous on the live real earth wallpaper on iphone (you know the one that show satellite and light/dark in real time)

is there anything remotely similar for samsung? even paid?

jeez i really wish they'd copy that
[Samsung Galaxy S23 Ultra] enij:
The most similar thing I found (with day/night cycle) is Xiaomi mountain super live wallpaper. I used it for years, it's cool.
[Samsung Galaxy S23 Ultra] tim84us:
yes but is it available for samsung too?? i know the xiami ones - the iphone one seems the best tho :)
[Samsung Galaxy S23 Ultra] ggrant3876:
I did see this the other day.

MIUI 12's latest Geometry and Snow Mountain live wallpapers are now available for download

You can now use MIUI 12's latest geometry and snow mountain live wallpapers on any Android device. Download link in the post.

www.xda-developers.com
[Samsung Galaxy S23 Ultra] enij:
Yes, from the thread the other user linked.
[Samsung Galaxy S23 Ultra] p.dixon0:
Is this just a rip off of the Pixel Marvelous Marble live wallpaper? If so, I've had this for years?

View attachment 5959817
[Samsung Galaxy S23 Ultra] Ertzu2680:
You can try the app Wallman:

„WallMan“ – IzzyOnDroid F-Droid Repository

Beautiful app to get beautiful wallpapers

apt.izzysoft.de

There you can download that wallpaper you wanted and set it even as the homescreen.

For me it works very well on my Samsung S23 Ultra.
[Windows Mobile Themes] xpressyourcell:
These are modified from the work of Greatball and Poorlyduck. All I did was change the color and change the size for VGA. The VGA Dialer is not done yet as the Diamond has a different format than previous models. I will post it as soon as I have it working.

For the Comm Manager you will need to install Greatball's M2D Comm Manager and then paste the appropriate resolution files into your Windows folder.

For the Dialer, you need to install Poorlyduck's M2D dialer and then paste the files into the Windows folder. THIS DIALER DOES NOT WORK ON THE DIAMON OR TOUCH PRO!!! I will post a VGA dialer for those phones as soon as I have it made.
[Sony Xperia 1 V] SALL666PL:
Hi, as above, I have a problem with my Xperia ... I have Ghost Touch once a day, it happens after unlock the phone, but when I lock it and unlock it again, it it never happened to me during use (browsing, etc.) has anyone had the same? I found on the internet that someone had the same problem (link) (

https://www.reddit.com/r/SonyXperia/comments/14o5md7
)

in the picture the points where the screen clicks itself (the dots are where you click, the lines I made with my finger)

View attachment 5959375
[Sony Xperia 1 V] decomposed:
Overall a lot of people are facing those issues.

Or it's other way round, ui not responding in some parts like back button or middle button....

Again they delivered half bakes software / beta device and we are testers as sony did not test it at all :/
[Sony Xperia 1 V] cpufrost:
Maybe the USA version won't have any of these issues!
[Sony Xperia 1 V] Hurt Copain:
It's likely a screen protector that's not working, I have seen this on other devices first hand with certain brands screen protectors, if not that I would wipe and see if the issue persists
[Sony Xperia 1 V] mufunyo:
I have this issue, and I use the phone completely naked (the phone, not my body) without any screen protectors. Locking and unlocking the phone fixes it when it happens. I had to disable double tap to wake because the ghost touches wake the phone in my pocket. Otherwise it's rare enough that it doesn't really bother me.
[Sony Xperia 1 V] Hurt Copain:
I was able to recreate it, if I enabled always on display, and enabled double tap to wake. Seems auto brightness causes the issue if the other settings are on too. I didn't have any issue with aod and double tap off. Logs are telling me anything as of yet..
[Sony Xperia 1 V] SALL666PL:
The problem seems to be solved, after the last update nothing happens to me anymore
[OnePlus 9] taayder:
I'm trying to pull the boot img from 9 Tmobile variant thats on 11.2.9.9 and I'm using this msm download tool I just unlocked the bootloader after receiving unlock token but got stuck with boot img. If someone can provide stock or magisk patched boot img for 11.2.9.9 that would be great as I'm facing this readback error on msmdownload tool

Please help me out if you have experience with this

View attachment 5959393

Got FIX***

Dm me if anyones needs boot img for this version
[Magisk] chiteroman:
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 /system/etc/security/otacerts.zip

If it shows "testkey", you won't pass Device verdict even with valid fingerprint.

- Your kernel localversion must not contain banned strings, run this command:

uname -r, and check here

You will need root and Zygisk, so you must choose ONE of this three setups:

- Magisk with Zygisk enabled.

- KernelSU with ZygiskNext module installed.

- APatch with ZygiskNext module installed.

After flashing and reboot your device you can check PI and SN using these apps:

- Play Integrity -> https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck

- SafetyNet -> https://play.google.com/store/apps/details?id=rikka.safetynetchecker

NOTE: if you get an error message about a limit, you need to use another app, this is because a lot of users are requesting an attestation.

NOTE: SafetyNet is

obsolete

, more info here: https://developer.android.com/privacy-and-security/safetynet/deprecation-timeline

Also, if you are using custom rom or custom kernel, be sure your kernel name isn't blacklisted, you can check it running "uname -r" command. This is a list of banned strings: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89308909 (thanks @osm0sis)

After requesting an attestation in Play Integrity API you should get this result:

- MEETS_BASIC_INTEGRITY ✅

- MEETS_DEVICE_INTEGRITY ✅

- MEETS_STRONG_INTEGRITY ❌

- MEETS_VIRTUAL_INTEGRITY ❌

You can know more about verdicts in this post: https://xdaforums.com/t/info-play-integrity-api-replacement-for-safetynet.4479337/ (thanks @V0latyle)

And in SafetyNet you should get this:

- basicIntegrity: true

- ctsProfileMatch: true

- evaluationType: BASIC

NOTE: Strong verdict is impossible to pass on unlocked bootloader devices, there are few devices and "exploits" which will allow you to pass it, but, in normal conditions, this verdict will be green only if you are using stock ROM and locked bootloader. The old posts talking about Strong pass was an "exploit" in Google servers, obviously, now it's patched.

FAQ: https://xdaforums.com/t/pif-faq.4653307/

You can download latest module version

here

You can donate me here ❤️
[Magisk] Lord Sithek:
Thanks for your great efforts, as well as @Displax, @kdrag0n and others who contributed 🫶
[Magisk] jons99:
is this a modification to the displax mod of kdrag0ns module?

what's the difference?
[Magisk] jons99:
thank you all green on asus zenfone 9 a13
[Magisk] shoey63:
Almost perfect on ROG phone 3 😋

View attachment 5959413

View attachment 5959411View attachment 5959417
[Magisk] 47here:
My bootloader still show unlock what you do to hide it?
[Magisk] shoey63:
Nothing.

It's a flaw in Rog 3.

Edit:

And yes, my bootloader is really unlocked and

I'm rooted

View attachment 5959433
[Magisk] casouzaj:
Thank you, @swer45! I uninstalled @Displax's Test4 module and installed yours. Likewise, my Xperia XZ2, running LineageOS 20.0, passes all three PI tests with your new module.
[Magisk] m0han:
Poco X3 Karna, AICP A12.1, Magisk Delta Canary, Riru. All good on TB Checker.
[Magisk] m0han:
Anyone have success on OnePlus 11 5G?

Spoiler content hidden.
[Magisk] Spartacus500:
Samsung Galaxy S7 edge Custom Pie 9.0 Rom NFE

Meets Strong integrity ✅ 👍

View attachment 5959561View attachment 5959567
[Magisk] V0latyle:
What are the differences between this and Displax module? I assume the Strong fix works the same way - spoof Pixel 2 shipped with Android 13?
[Magisk] chiteroman:
This one only spoof first api level in GMS process, so it won't affect system. Also I cleaned source code.
[Magisk] chiteroman:
I tried to spoof a fake root of trust and it worked! But only works in Key Attestation Demo because it's a very simple app, when I want to try it with a real app like CIB it crashes and in Momo it gives an error of "Service not responding". Also sometimes the

system crashes

and it's very easy to detect.

Solution? Use my Xposed module (easy to detect) or modify framework.jar and implement hook by yourself (better).

So this module won't have that option.
[Magisk] acwcanada:
Displax's 2.4.0 pass device and basic, and his "Strong" passes all 3. I got "Red" on all 3 with yours, install Shamiko doesn't make any difference. My Pixel 6 Pro is on A14 Beta 4, have no idea if this is the reason.
[Magisk] immortalwon:
Works on one plus pro 9 and passes all play integrity checks even strong. Nice work but I don't give it long b4 being patched. A device with broken T.E.E keymaster sure is hilarious passing play integrity
[Magisk] chiteroman:
Which modules are you using ?
[Magisk] chiteroman:
Try again with the new update, remember to install Shamiko and have enforce deny list disabled 👍
[Magisk] Hausemaster:
Have you tried enabling device simulation on MHPC, if not, then you might be failing due to security patch date mismatch, correct me if I'm wrong... (Enable all spoofing options in device simulation, and be sure to use a fingerprint with the same Android version as yours)

It's for hiding LIBC file, and system calls, use ruru detection app to observe changes, also, did you add the detection apps to magisk hide in magisk delta?

That might be ROM specific, and, just as said by others before me, try looking for a rom with enforcing by default...
[Magisk] Hausemaster:
Just out of curiosity, doesn't the OEM need to implement the keymaster/TEE properly for STRONG_INTEGRITY? Is it possible to pass strong integrity without any implemented keymaster/TEE? Just to be sure, I tried it on my tb_8504x with Android 8.1 (no keymaster implementation) and Google Play services crashes and fails to produce any result unless the module has been removed...

Edit: I can't pass strong integrity with stock rom and locked bootloader on my tb_8504x, that's why I was curious...

Sorry about the strange questions...
[Magisk] AnyNameYouWish:
That's exaclty what happened, even though Applist Detector still could see XPrivacyLua. I tried a few reboot before bedtime, and integrity checks were successful.

This morning however, the checks failed again, until I wiped Xlua again. What a rollercoaster

🤷‍♂️
[Magisk] pndwal:
You do realise that simply installing MagiskHide Props Config does very little until you configure some?... Nothing changing is expected!

It used to do nothing... More recently it will adjust "MagiskHide" sensitive props (ie props that MagiskHide used to reset if values were suspicious to banks etc before 24.0+) by default (and USNF, Shamiko etc do this anyway if installed, so that will only really help/change anything for users trying to pass device integrity verdicts on devices launched pre Android 8 or later devices with broken keymaster that don't need USNF trigger to use basic attestation) etc, but fingerprint prop setting etc all require user intervention... You needed to use a terminal emulator and type props to access MHPC configuration...

Anyway, it's very doubtful you need it at all since USNF added targeted fingerprint spoofing for GMS... May help for edge cases only... 😜 PW
[Magisk] beeshyams:
@pndwal

"Yup... Works (like Shamiko) as it's proper hiding, not Magisk/root modification reversion."

So, I understand that using this module is superior. But couldn't follow the second part (the inferior way)

Could you please explain in simple terms? Sorry for the bother
[Magisk] pndwal:
No, some devices (like Asus ROG Phone 3) could pass w/ unlocked bootloader (bad OEM implementation) but Google soon fixed that by revoking keys for strongIntegrity on that device as expected...

Seems so... Apparently a flaw in Google's implementation this time... Unless they intended to allow Pixel 2 to pass without using hardware attestations at all and thought no-one would notice/take advantage!... Bound to patch it soon now however. 😜

Properly implemented it shouldn't be possible at all, but remember attestations are processed on Google's back end and if a fingerprint prop is allowed to override proper hardware backed verdicts Google can do that of course... However props, being in userspace, compromise the whole hardware backed cryptographically attested verdict concept if used this way, especially because other devices can immediately spoof properties like this to take advantage... It's almost laughable... Praps Google is just joking around with us!... They've gotta be in the know... 😂 PW
[Magisk] pndwal:
No... Since Play Integrity API we actually need a fingerprint mismatch for many devices to pass deviceIntegrity (bypass server end hardware-backed evaluationType enforcement) like the model mismatch, so USNF added spoofing an old (A6 Nexus) fingerprint targeting gms (nb. MHPC does global spoofing which used to cause many device specific issues) to ensure all devices are covered... This means with current USNF custom, China region, developer, beta etc. ROMs no longer need a seperate solution for fingerprint... Nb. @kdrag0ns USNF GitHub page is still a bit misleading on this. 😬

Further, adjusting security patch prop date value to match the fingerprint prop value used is not needed for fingerprints predating March 2018... More details here:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-88795029

🤠 PW
[Magisk] pndwal:
Denylist is inferior for hiding as that's not it's purpose despite retaining some code from old MagiskHide... The code has been repurposed as a development/testing tool and actually breaks many functions used for active hiding/spoofing as is simply does Magisk/root modification reversion in listed processes... Proper hiding modules don't break code injection etc...

Yes, DenyList Unmount is vastly superior to Denylist for hiding root, and probably superior to old MagiskHide in many respects... It's drawcard for some is open source as some have misgivings about closed source Shamiko (I don't), but Shamiko is otherwise superior to DenyList Unmount, offering Zygisk hiding (still a WIP and somewhat lacking) and other unique hiding abilities... Also, with native bridge loaded Zygisk coming (WIP also) from the same LSP team. expect Zygisk hiding improvements after Magisk 27.0...

Please see these posts also:

- https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-88468575

- https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-88738939

Hope it helps, 🙂 PW
[Magisk] beeshyams:
Thanks for your patient and informative updates... Rare to find such people!
[Magisk] chiteroman:
Updated and source code available:

GitHub - chiteroman/PlayIntegrityFix: Fix Play Integrity (and SafetyNet) verdicts.

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] zandatsu06:
Works great in kernelsu man! No need to use USNF i guess. View attachment 5964029
[Magisk] mehgancangweh:
Hello sorry to bump idk if i'm late

Modules does not work for me, displax v2.4.0-MOD_2.0 is working but cannot pass meets_strong..

Google play & play service keep looping force stop & app integrity check just loop unresponsive

I tried 2 version v4.5 and the version before that (i forget)

My device: POCO X3 NFC (surya), Android 10 API 29, Magisk official stable zygisk

Step i produce:

uninstall displax

reboot

install yours

reboot

(the problem happened)

Step i tried:

clear data & cache both play & services none of them work

But when i uninstall yours, service running normally

Im i missing something? is there any clue i can do?

Let me know if u need more information..
[Magisk] chiteroman:
Send me the output of this command: adb shell "logcat | grep 'SNFix'"
[Magisk] Displax:
Yes, some crashes present on Android 10 (reported by users).

Logs.
[Magisk] Displax:
Strange behavior on 4.5... PI passed all, but SN failed all. 4.0 works good.
[Magisk] tutibreaker:
all good
[Magisk] chiteroman:
Yep, fixed
[Magisk] chiteroman:
View attachment 5964149

As you can see there is a bug in hook. Maybe due old Dobby version, try the new update.
[Magisk] mehgancangweh:
idk if this a correct way to attach an image on this forum

ss 1 is the logcat, ss2 is the problem, and the last one that module properly installed

Step i produce:

install module

reboot

plug my phone into pc, yes for all asking usb

do adb logcat command

trying to use the phone like normal
[Magisk] chiteroman:
Yep, try new version from OP.
[Magisk] makeyourself:
Well

Yeah bizarrely Google Wallet shows "You're ready to pay contactless" and "Your phone meets security requirements". Even though my device is now failing Device Integrity! Does Wallet only check Play Integrity now and again? I suspect it's going to stop working soon.
[Magisk] zgfg:
Not bcs the way how is it designed. You cannot cash old or steal from another device

It's about digitally signing by private keys where the signature is hashed over the content, time-stamp and a temporary token that was generated at the time when an app requests the verdict.

Hence if you use the old timestamp and token - it doesn't correspond to the new request.

If you update timestamp and token, the old signature is no more valid.

And you cannot spoof signature since you don't know the private key

It's been discussed here how and why and there wad documentaion showing the details
[Magisk] immortalwon:
Negative, still failing on a11
[Magisk] DanGLES3:
Sadly, no
[Magisk] HippoMan:
Well, again, I'd like to believe that this is the road that the Googlefrinchian management would take, but I still won't bet on it.

I'd bet on the opposite ... but I'd be glad to lose that bet.
[Magisk] zgfg:
It won't last long

Last time I was able to pay about half a day after Device started to fail (for the whole afternoon)

Intentionally I didn't open Wallet myself, I just used NFC.

But next morning it stopped paying
[Magisk] makeyourself:
That doesn't work for me, tried multiple reboots and clearing all caches.
[Magisk] yoongdeer:
nop still failing
[Magisk] d8390:
But version 12.3, installed few days ago, worked for me today. Now release removed from github.

Galaxy A73
[Magisk] zgfg:
It worked until Google fixed on their side. Now, no more

And see the announcement at:

GitHub - chiteroman/PlayIntegrityFix: Fix Play Integrity (and SafetyNet) verdicts.

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] Dehumanizer77:
I don't have much to say, but keep up the good work, @chiteroman ! I've sent you some spare cash :-) Looking forward for working version :)
[Magisk] sawdoctor:
Exactly. The amount of people running play integrity check apps started to cause the servers to time out, not exactly discrete.

If Google actually wanted to stop us modding our phones they just make pixel bootloaders unlockable
[Magisk] HippoMan:
I think you mean "un-unlockable". But your point is clear.
[Magisk] DanGLES3:
They weren't timing out the Play Integrity servers, they were exhausting the free API quota of apps like Play Integrity checker
[Magisk] CaptainFedora:
OnePlus 8T

Android 13 (OxygenOS 13.1)

Magisk 26300

PIF 12.3

Zygisk Next 4.0.8.1

GPay doesn't work.
[Magisk] sawdoctor:
My wording was wrong i know but you still get my point it must have caught Google's attention
[Magisk] immortalwon:
please read the previous comments and the github of chiteroman.

Everyone else should read as well.

I think its funny one man chiteroman managed to ellicit a response from Google like this. It just goes to show one man can make a difference in the world.
[Magisk] Reynald0:
Yeah bro, tags are from now only Private, as expected: https://github.com/chiteroman/PlayIntegrityFix/tags
[Magisk] bigknowz:
Able to use at ATM with device integrity failing. V 12
[Magisk] fede2782:
Not working anymore. I can only pass baaic_integrity. Certification doesn't work too.
[Magisk] ShaDisNX255:
Does it really take that much of an effort to just take a few minutes to read the most recent posts and confirm that it's not working for anyone at the moment?
[Magisk] zgfg:
Not. That's totally different. Then you get error, not Basic green and Device red

Btw, test with Play store app, Settings, Dev options or from TB Checker

But of course, now so man ppl are testing that you can expect that Pai API Checkers would again run out of qouta and showing error instead - but that doesn't mean that Google did not fix on their side
[Magisk] DanGLES3:
I've did, I didn't imply Google didn't fix it on their end, I meant to simply correct them on the quota issue being an app thing not an general Play Integrity thing
[Magisk] xSnowLeopardx:
Read the past 3-4 pages. Sucks, but what can ya do...

I am not happy that I am not the only one, but at the same time, it's nice to not try 10 things and see how it works for others, but not yourself :')

Good luck @chiteroman - we believe in you and we're grateful for what you do.