Damm, the community is now shilling more HyperOS/MIUI ROMs nowadays
The Best Years Of Our Lives
Nevermind, more issues coming out like apps crashing whereas they previously worked in previous build Back to Lineage..
Even though every time it gets shot down with contractions from other users, still best to avoid
I'm still not home btw, running this ROM
Telegram
Redmi Note 10 Pro | Updates
#Retro #MIUI #Sweet #Sweetin
RetroGamingGodMode | Android 12.
Released: 04/06/'24
▪️ Download
▪️ Screenshots
▪️ Support
Notes:
• Base miui 12.0.15 GL
• Read Full Changelog Before Asking Anything
• First Boot Will Take Around 5-10 Minutes
• Ksu Supported…
RetroGamingGodMode | Android 12.
Released: 04/06/'24
▪️ Download
▪️ Screenshots
▪️ Support
Notes:
• Base miui 12.0.15 GL
• Read Full Changelog Before Asking Anything
• First Boot Will Take Around 5-10 Minutes
• Ksu Supported…
Forwarded from Pray Integrity Fix 🙏 (Marcos)
Google VPN requires Strong integrity 🥲
🤮1
Pray Integrity Fix 🙏
Google VPN requires Strong integrity 🥲
don't care + windscribe and mullvad exist + major goolag L
🔥1
Forwarded from not_aha
The Best Years Of Our Lives
don't care + windscribe and mullvad exist + major goolag L
Also Google said Google vpn was going to close, because almost no one was using it
👍1
Forwarded from Pray Integrity Fix 🙏 (Marcos)
This user have a device with the original keybox banned, Google revoked it. He didn't touch persist neither reprogrammed the TEE:
https://t.me/playfixnext/1/56815
https://t.me/playfixnext/1/56856
Now, using stock rom with locked bootloader, he can only pass BASIC verdict, no DEVICE neither STRONG.
What is the solution? Replacing motherboard? No, the keybox is the original one, you will need to buy a new phone.
Welcome to 1984! Google now decides what device is secure or not.
https://t.me/playfixnext/1/56815
https://t.me/playfixnext/1/56856
Now, using stock rom with locked bootloader, he can only pass BASIC verdict, no DEVICE neither STRONG.
What is the solution? Replacing motherboard? No, the keybox is the original one, you will need to buy a new phone.
Welcome to 1984! Google now decides what device is secure or not.
Pray Integrity Fix 🙏
This user have a device with the original keybox banned, Google revoked it. He didn't touch persist neither reprogrammed the TEE: https://t.me/playfixnext/1/56815 https://t.me/playfixnext/1/56856 Now, using stock rom with locked bootloader, he can only pass…
Lava is not a major OEM like Samsung, Xiaomi, Oppo, etc..
So Google doesn't give a flying fuck if bans affect non-root + lbl users
So Google doesn't give a flying fuck if bans affect non-root + lbl users
Forwarded from Sankalp K. Bhattacharya
I'm coming back to trm eu, pixel os latest build sucks ahh rn
And me happy to announce I'm back home
I can finally flash Lineage!
I can finally flash Lineage!
NVM, still Apatch will remain an exclusivity on MIUI + Stock Perf unforunately 😔
Reason: LineageOS Kernel does get patched and all, but then Apatch manager shits itself because of weird permission denials and you sort of can't do anything, making apatch completely useless
Tried flashed latest vantom, doesn't not support apatch.
Reason: LineageOS Kernel does get patched and all, but then Apatch manager shits itself because of weird permission denials and you sort of can't do anything, making apatch completely useless
Tried flashed latest vantom, doesn't not support apatch.
Tho, I can take LineageOS kernel source and complete support for apatch
After I confirm the issue is kernel-related tho
After I confirm the issue is kernel-related tho
👍1
The Best Years Of Our Lives
How to get bootloader locked spoof + device integrity without zygisk 1. Download both FrameworkPatcherGO and Reset Sensitive Props 1a. Add GMS and play store app to magiskhide/denylist if magisk 2. Install both modules 3. When you come to install FrameworkPatcherGO…
Update 4: If you want to remain without Zygisk, use Kitsune Mask
If you are going to use Zygisk anyways, use Magisk Alpha + Shamiko
KSU/Apatch users ignore this update
If you are going to use Zygisk anyways, use Magisk Alpha + Shamiko
KSU/Apatch users ignore this update
The Best Years Of Our Lives
Tho, I can take LineageOS kernel source and complete support for apatch After I confirm the issue is kernel-related tho
Actually, it's not LOSKernel fault nor ROM fault
There's an issue with Apatch and newer 4.14.* openela kernel versions, so there's nothing I can do than wait for Apatch to be updated to support
Until then: I'm using Kitsune Mask since I don't need Zygisk but do need MagiskHide + Enforce Sulist
There's an issue with Apatch and newer 4.14.* openela kernel versions, so there's nothing I can do than wait for Apatch to be updated to support
Until then: I'm using Kitsune Mask since I don't need Zygisk but do need MagiskHide + Enforce Sulist
P.s
Both Lineage (27th June Build, I haven't tried latest 5th July build) and PixelOS have GPS issues
Try spam-disabling and re-enabling "Use assisted GPS" to make GPS respond somewhat
Unsure about beta crDroid and Project Blaze
Both Lineage (27th June Build, I haven't tried latest 5th July build) and PixelOS have GPS issues
Try spam-disabling and re-enabling "Use assisted GPS" to make GPS respond somewhat
Unsure about beta crDroid and Project Blaze
The Best Years Of Our Lives
Captive portal works, it was just the free WiFi network shitty
Turns out that free WiFi hotspot doesn't play nicely with randomized MAC address 💩
The Best Years Of Our Lives
Turns out that free WiFi hotspot doesn't play nicely with randomized MAC address 💩
Can't say I'm enjoying the 500kb-1mb/s max speed 🤡