Hello spes/n communityy!! Today I am opening once again 15 slots to my test group, wanted to be a tester? It's the right time to shine! Before proceeding please do consider some stuff below. You must have spes/n inorder to join this group also.
You may not:
- Leak builds, could result in fban.
- You can share screenshots
Warning:
- We am not responsible for the damages it will cause.
Spes/n test group link: https://t.me/+-dHTurw872IzOTA1
You may not:
- Leak builds, could result in fban.
- You can share screenshots
Warning:
- We am not responsible for the damages it will cause.
Spes/n test group link: https://t.me/+-dHTurw872IzOTA1
#HyperOS #OS4 #ROMs #A17 #spes #spesn
HyperOS 4 BETA (4.0.0.17 XPACNXM)
Android 17
Released: 06/09/2026
Device: Redmi Note 11/NFC (spes/n)
By: @aaliz14 & @jesuslbr
▪️Download: Kaorios Build | Non-Kaorios | Go file | Mirror
▪️Kernel: Includes Hanbal-Gforce Base | More Kernels
▪️Screenshots: Here | More | More
▪️Channels: RN11 | Hanbal | @jesuslbr channel jesuspes_port has been hacked. Help him by reporting channel for impersonation.
▪️Support Group
▪️Notes:
-Two variants are released one is with kaorios toolbox included other is without kaorios
- Telegram full screen videoplay may not work
▪️Credits:
. Fixes:
- @BlackLizard_07,
- Bootloopgang Team
- @NikoRur_QwQRuaa and
@HuLi_Rea on coolapk
• Modded Apps: @kashis_cringey_stuffs @llionsmods PeaceMods
HyperOS 4 BETA (4.0.0.17 XPACNXM)
Android 17
Released: 06/09/2026
Device: Redmi Note 11/NFC (spes/n)
By: @aaliz14 & @jesuslbr
▪️Download: Kaorios Build | Non-Kaorios | Go file | Mirror
▪️Kernel: Includes Hanbal-Gforce Base | More Kernels
▪️Screenshots: Here | More | More
▪️Channels: RN11 | Hanbal | @jesuslbr channel jesuspes_port has been hacked. Help him by reporting channel for impersonation.
▪️Support Group
▪️Notes:
-Two variants are released one is with kaorios toolbox included other is without kaorios
- Telegram full screen videoplay may not work
▪️Credits:
. Fixes:
- @BlackLizard_07,
- Bootloopgang Team
- @NikoRur_QwQRuaa and
@HuLi_Rea on coolapk
• Modded Apps: @kashis_cringey_stuffs @llionsmods PeaceMods
Join : Channel | Cloud | Backup | Chat | Wallpapers | Boost
Important Notice For Channel Owners & Admins
There's apparently a bot that unlinks channel from groups . I don't know what kind of issues that might cause yet. But it seems malicious. Also thanks for @MOH_SH4RMA noticing.
Details : here & here
There's apparently a bot that unlinks channel from groups . I don't know what kind of issues that might cause yet. But it seems malicious. Also thanks for @MOH_SH4RMA noticing.
Details : here & here
#kernel #spes #spesn #SUSFS #KernelSU
Redmi Note 11 (spes/spesn) — Custom Kernel
KernelSU-Next v3.3.0 + SUSFS v2.2.0
Released: 06/09/2026
Device: Redmi Note 11 (spes/spesn)
By: @Sam17982
⚠️ Warning:
- Does NOT work on Murali's sources based ROMs
- For now works only on Android 16 roms
Downloads :
- Kernel: Release ksu-next-susfs-v2
- Manager: KernelSU Next v3.3.0
Credits:
@Iron_hide23
Sources :
- KernelSU-Next (Youffx)
- Lineage OS Kernel (Shaddowalker-26, prebuilt)
Support Group: Support
Redmi Note 11 (spes/spesn) — Custom Kernel
KernelSU-Next v3.3.0 + SUSFS v2.2.0
Released: 06/09/2026
Device: Redmi Note 11 (spes/spesn)
By: @Sam17982
⚠️ Warning:
- Does NOT work on Murali's sources based ROMs
- For now works only on Android 16 roms
Downloads :
- Kernel: Release ksu-next-susfs-v2
- Manager: KernelSU Next v3.3.0
Credits:
@Iron_hide23
Sources :
- KernelSU-Next (Youffx)
- Lineage OS Kernel (Shaddowalker-26, prebuilt)
Support Group: Support
Join : Channel | Cloud | Backup | Chat | Wallpapers | Boost
#crDroid #ROM #B #unofficial #OSS #spes #spesn #stable #A16
crDroid 12.11 | UNOFFICIAL | Android 16
Released: 06/09/2026
• Download : Here | Mirror
• Notes : Here
Changelog :
* ROM: Updated crdroid to version 12.11
* ROM: Applied August security patch
* Device: Removed unused camera blobs
* Device: Resolved slow fast-charging issue
* Device: Reoptimized swapiness and VFS cache for enhanced memory management
* Device: Updated and cleaned up Dalvik properties
* Device: Fixed issue where ringtones and alarms did not play when Bluetooth or wired headphones were connected
* Device: Switched to AOSP WFD
* Device: Set FCM level to 7
* Device: Removed Samsung debug tools
* Device: Resolved several SELinux denials
* Device: Switched to common AIDL IR service
* Kernel: Upstreamed BPF patches up to 4.19.325-cip135-st19
* Kernel: Implemented memory management fixes for 4GB variants
By : @muralivijay9845
crDroid 12.11 | UNOFFICIAL | Android 16
Released: 06/09/2026
• Download : Here | Mirror
• Notes : Here
Changelog :
* ROM: Updated crdroid to version 12.11
* ROM: Applied August security patch
* Device: Removed unused camera blobs
* Device: Resolved slow fast-charging issue
* Device: Reoptimized swapiness and VFS cache for enhanced memory management
* Device: Updated and cleaned up Dalvik properties
* Device: Fixed issue where ringtones and alarms did not play when Bluetooth or wired headphones were connected
* Device: Switched to AOSP WFD
* Device: Set FCM level to 7
* Device: Removed Samsung debug tools
* Device: Resolved several SELinux denials
* Device: Switched to common AIDL IR service
* Kernel: Upstreamed BPF patches up to 4.19.325-cip135-st19
* Kernel: Implemented memory management fixes for 4GB variants
By : @muralivijay9845
Join : Channel | Cloud | Backup | Chat | Wallpapers | Boost
Forwarded from Muralidharan | Redmi note 11 | Releases
Hi everyone,
i wanted to give you an official, technical update regarding our kernel strategy and our evaluation of the 5.15 kernel bringup.
Over the past few months, our developers community has made impressive progress on 5.15—including camera fixes thanks to halt for his efforts. However, after evaluating long-term stability, user safety, and hardware compatibility, i have officially decided to keep our primary/stable releases on our optimized 4.19 kernel with backported BPF support, while maintaining 5.15 as an experimental side project.
Here is a detailed breakdown of why this decision was made for the long-term health of our device:
1. Installation Complexity & Hardware Safety
Running 5.15 requires users to manually repartition their internal storage using parted commands to create a dummy init_boot partition. Requiring manual GPT partition modifications carries a high risk of hard-bricking devices for average users and permanently breaks clean Recovery and OTA update workflows.
2. Firmware Swapping & Downgrade Risks
To run 5.15, users are required to flash ADSP/DSP firmware files ported from another device. If a user ever decides to switch back to stock or 4.19-based ROMs without manually restoring the stock DSP/ADSP firmware, the device will fail to boot entirely.
3. Bootloader Limitations & Broken Root (Magisk)
Because our legacy bootloader does not natively parse the init_boot structure, the dummy init_boot partition cannot be utilized correctly during the bringup process. As a result, attempting to patch init_boot with Magisk will fail, breaking root access.
4. Upstream Kernel Lifecycle (EOL)
Linux 5.15 is nearing its official End-of-Life (EOL) status in upstream Linux. Moving our main codebase to an EOL kernel creates heavy long-term maintenance overhead for security backports without providing true mainline longevity.
5. Hardware IPC & Security Compromises
Due to underlying vendor firmware limits (ADSP / FastRPC), core hardware integrations like the virtual proximity sensor remain unstable on 5.15. Furthermore, achieving functional decryption requires forced downgrades from Keymint HAL to legacy Keymaster 4.1.
6. Peak Performance on 4.19 + eBPF
With upstream eBPF (clsact/cgroup) successfully backported to our 4.19 kernel, our builds fully meet modern Android networking requirements while retaining 100% hardware functionality, native root support, peak battery efficiency, and zero-risk installation.
Roadmap Going Forward:
• Stable ROM Releases: Will strictly use the 4.19 + eBPF kernel for complete reliability, safety, and seamless flashing.
• Experimental 5.15 Project: Will remain active on GitHub for developers and advanced testers who wish to contribute toward FastRPC,audio and sensor IPC research.
Thank you all for your continued patience, testing, and support as we prioritize daily-driver stability for our device!
i wanted to give you an official, technical update regarding our kernel strategy and our evaluation of the 5.15 kernel bringup.
Over the past few months, our developers community has made impressive progress on 5.15—including camera fixes thanks to halt for his efforts. However, after evaluating long-term stability, user safety, and hardware compatibility, i have officially decided to keep our primary/stable releases on our optimized 4.19 kernel with backported BPF support, while maintaining 5.15 as an experimental side project.
Here is a detailed breakdown of why this decision was made for the long-term health of our device:
1. Installation Complexity & Hardware Safety
Running 5.15 requires users to manually repartition their internal storage using parted commands to create a dummy init_boot partition. Requiring manual GPT partition modifications carries a high risk of hard-bricking devices for average users and permanently breaks clean Recovery and OTA update workflows.
2. Firmware Swapping & Downgrade Risks
To run 5.15, users are required to flash ADSP/DSP firmware files ported from another device. If a user ever decides to switch back to stock or 4.19-based ROMs without manually restoring the stock DSP/ADSP firmware, the device will fail to boot entirely.
3. Bootloader Limitations & Broken Root (Magisk)
Because our legacy bootloader does not natively parse the init_boot structure, the dummy init_boot partition cannot be utilized correctly during the bringup process. As a result, attempting to patch init_boot with Magisk will fail, breaking root access.
4. Upstream Kernel Lifecycle (EOL)
Linux 5.15 is nearing its official End-of-Life (EOL) status in upstream Linux. Moving our main codebase to an EOL kernel creates heavy long-term maintenance overhead for security backports without providing true mainline longevity.
5. Hardware IPC & Security Compromises
Due to underlying vendor firmware limits (ADSP / FastRPC), core hardware integrations like the virtual proximity sensor remain unstable on 5.15. Furthermore, achieving functional decryption requires forced downgrades from Keymint HAL to legacy Keymaster 4.1.
6. Peak Performance on 4.19 + eBPF
With upstream eBPF (clsact/cgroup) successfully backported to our 4.19 kernel, our builds fully meet modern Android networking requirements while retaining 100% hardware functionality, native root support, peak battery efficiency, and zero-risk installation.
Roadmap Going Forward:
• Stable ROM Releases: Will strictly use the 4.19 + eBPF kernel for complete reliability, safety, and seamless flashing.
• Experimental 5.15 Project: Will remain active on GitHub for developers and advanced testers who wish to contribute toward FastRPC,audio and sensor IPC research.
Thank you all for your continued patience, testing, and support as we prioritize daily-driver stability for our device!
Forwarded from Felix's ShitROMs
Hello there.
Some months back some people didn't like the idea of donating to me financially via the various methods of payment, and I get that.
However, I have been personally attacked and got called a selfish person over requesting help, and what doesn't help is that I got a new phone and is paying for them in installments because my company decided to not pay me anymore, and my line of credit doesn't permit me to even pay a single riyal over to fix my spes without me getting into a default, soooo I'm fucked.
If you decide to help me financially or have the necessary knowledge to help me and SCOS in mainlining the Snapdragon 680 or further fixing up the kinks in the existing Halium kernel, please message me. If you decide to not help me, either because of your own financial or knowledge constraints or because you don't feel like it, that's okay too.
Just to say again: if you don't wanna donate, just don't. I do not tolerate harassment however, and whoever does will be made sure they won't ever see Linux on this shitty phone again.
Some months back some people didn't like the idea of donating to me financially via the various methods of payment, and I get that.
However, I have been personally attacked and got called a selfish person over requesting help, and what doesn't help is that I got a new phone and is paying for them in installments because my company decided to not pay me anymore, and my line of credit doesn't permit me to even pay a single riyal over to fix my spes without me getting into a default, soooo I'm fucked.
If you decide to help me financially or have the necessary knowledge to help me and SCOS in mainlining the Snapdragon 680 or further fixing up the kinks in the existing Halium kernel, please message me. If you decide to not help me, either because of your own financial or knowledge constraints or because you don't feel like it, that's okay too.
Just to say again: if you don't wanna donate, just don't. I do not tolerate harassment however, and whoever does will be made sure they won't ever see Linux on this shitty phone again.
#Lineage #Vanilla #A16 #QPR2 #spes #spesn
Lineage 23.2 | UNOFFICIAL | Android 16
Released: 10/10/26'
▪️Download | Mirror
▪️Screenshot
▪️Gapps | MicroG
Changelog
• September 2026 Android Security Patch
• Extensive framework security hardening and fixes
• Settings and system improvements
• Twelve Music improvements and Media3 1.11.0 update
• Improved memory management and kernel optimizations
• Scheduler, BPF, binderfs and Simple LMK improvements
• Overall stability and bug fixes
Notes:
• OTA pushed
• Support group
• Dirty flash is ok
• Installation guide
• Use recommended gapps
• Report bugs with proper logs
Credits:
• All spes devs for device resources
By @Iron_hide23
Lineage 23.2 | UNOFFICIAL | Android 16
Released: 10/10/26'
▪️Download | Mirror
▪️Screenshot
▪️Gapps | MicroG
Changelog
• September 2026 Android Security Patch
• Extensive framework security hardening and fixes
• Settings and system improvements
• Twelve Music improvements and Media3 1.11.0 update
• Improved memory management and kernel optimizations
• Scheduler, BPF, binderfs and Simple LMK improvements
• Overall stability and bug fixes
Notes:
• OTA pushed
• Support group
• Dirty flash is ok
• Installation guide
• Use recommended gapps
• Report bugs with proper logs
Credits:
• All spes devs for device resources
By @Iron_hide23
Join : Channel | Cloud | Backup | Chat | Wallpapers | Boost
Forwarded from Hyper Vibes ✨🫧
✨ THE HOLY GRAIL HAS ARRIVED: HyperOS 4 Theme is OUT! 🚀💖
The wait is officially over! We are dropping our absolute best, most requested, and top-tier creation yet—the ultimate HyperOS 4 Theme! 📱💎
If you want your device to look ultra-clean, super smooth, and ridiculously aesthetic, you CANNOT miss this one! Once you apply this theme, you'll never want to change it back! 😉✨
Quick Tip: Apply the theme, reboot your device, and enjoy the magical setup! 📱✨
Drop a ❤️ if you’re applying it right now, and don't forget to share your setup screenshots in our [Discussion Group]! Enjoy the vibes! 💬💖
The wait is officially over! We are dropping our absolute best, most requested, and top-tier creation yet—the ultimate HyperOS 4 Theme! 📱💎
If you want your device to look ultra-clean, super smooth, and ridiculously aesthetic, you CANNOT miss this one! Once you apply this theme, you'll never want to change it back! 😉✨
✨ Why You MUST Try This Theme:
🎨 Next-Level Aesthetics – Ultra-clean icons & smooth visual harmony
🟡 Leica Vibrant Yellow Font – Iconic, high-contrast & ultra-stylish typography
🌀 Fluid Animations – Butter-smooth performance on every swipe
🔒 Super Dynamic Lock Screen – Fully customizable with awesome widgets
🎛️ New Control Center Vibe – Sleek, modern & pure perfection
🖼️ Screenshots
📥 [Download]
Quick Tip: Apply the theme, reboot your device, and enjoy the magical setup! 📱✨
Credit : @VK9196 ,@v1sld
Drop a ❤️ if you’re applying it right now, and don't forget to share your setup screenshots in our [Discussion Group]! Enjoy the vibes! 💬💖