Forwarded from KernelSU Next Bot
KernelSU_Next_v1.1.1-23-g300a13f6_12874-release.apk
16.9 MB
CI Manager (TEST BUILD)
#ci_2674
Commit
Workflow run
#ci_2674
kernel: handle throned UID change if manager is reinstall or changed
drop old UID and throne the new one when the manager is reinstalled or changed
Commit
Workflow run
KernelSU_Next_v1.1.1-23-g300a13f6-spoofed_12874-release.apk
16.9 MB
CI Manager (SPOOFED BUILD)
#ci_2674
Commit
Workflow run
#ci_2674
kernel: handle throned UID change if manager is reinstall or changed
drop old UID and throne the new one when the manager is reinstalled or changed
Commit
Workflow run
Forwarded from Nagram X CI
NagramX-v12.0.1-25f9110(1219)-arm64-v8a.apk
48.4 MB
Test version.
Commit Message:
See commit details 25f9110
Commit Message:
feat: add retry for voice transcription and better inline translation
See commit details 25f9110
https://github.com/mikropsoft/StevenBlock
🚫 Advanced Ad-Blocking Module for Android | Compatible with Magisk, KernelSU, and APatch 🔒
🚫 Advanced Ad-Blocking Module for Android | Compatible with Magisk, KernelSU, and APatch 🔒
GitHub
GitHub - mikropsoft/StevenBlock: 🚫 Advanced Ad-Blocking Module for Android | Compatible with Magisk, KernelSU, and APatch 🔒
🚫 Advanced Ad-Blocking Module for Android | Compatible with Magisk, KernelSU, and APatch 🔒 - mikropsoft/StevenBlock
No deleted account found from
87 scanned users from this group 🚫👻Forwarded from Wild Kernels Bot
Wild_KSU_v0.0.159_13964-release.apk
17.4 MB
🔧 CI Manager (TEST BUILD) #ci_3764
📝 Exclude settings SharedPreferences from Android auto backup
🔗 Commit: https://github.com/WildKernels/Wild_KSU/commit/b63528331cba441d1da4f4117eb74da628a5f9b6
🏃 Workflow: https://github.com/WildKernels/Wild_KSU/actions/runs/18190275429
📝 Exclude settings SharedPreferences from Android auto backup
🔗 Commit: https://github.com/WildKernels/Wild_KSU/commit/b63528331cba441d1da4f4117eb74da628a5f9b6
🏃 Workflow: https://github.com/WildKernels/Wild_KSU/actions/runs/18190275429
Wild_KSU_v0.0.159-spoofed_13964-release.apk
17.4 MB
🔧 Spoofed Manager (TEST BUILD) #spoofed_3764
📝 Exclude settings SharedPreferences from Android auto backup
🔗 Commit: https://github.com/WildKernels/Wild_KSU/commit/b63528331cba441d1da4f4117eb74da628a5f9b6
🏃 Workflow: https://github.com/WildKernels/Wild_KSU/actions/runs/18190275429
📝 Exclude settings SharedPreferences from Android auto backup
🔗 Commit: https://github.com/WildKernels/Wild_KSU/commit/b63528331cba441d1da4f4117eb74da628a5f9b6
🏃 Workflow: https://github.com/WildKernels/Wild_KSU/actions/runs/18190275429
Forwarded from Morgan Weedman, Wild Kernels Owner (DMs OPEN)
Hey there!
GKI Users:
Anyone of you waiting for 1.5.10 WKSU GKI, sorry for the wait, susfs added new commits that are being tested, not all branches are in sync yet. There may be problems with these commits making hiding worse, so im going to wait for fixes.
When we build we use the latest susfs commits, not the 1.5.9 tag... so in reality you are using 1.5.10 beta.
Most of the time when Simon (Susfs Dev) updates version for example 1.5.9 -> 1.5.10 all he updates is the number 9 -> 10, all of the 1.5.10 commits are already done before the tags.
If you are on my latest kernel, you are updated to the best hiding you can get so just wait!
if this doesnt make sense im sorry, tag me and i can maybe explain better!
Thanks everyone!
If you like my work and would like to support me!
Donations:
https://t.me/WildKernels/90170/90171
GKI Users:
Anyone of you waiting for 1.5.10 WKSU GKI, sorry for the wait, susfs added new commits that are being tested, not all branches are in sync yet. There may be problems with these commits making hiding worse, so im going to wait for fixes.
When we build we use the latest susfs commits, not the 1.5.9 tag... so in reality you are using 1.5.10 beta.
Most of the time when Simon (Susfs Dev) updates version for example 1.5.9 -> 1.5.10 all he updates is the number 9 -> 10, all of the 1.5.10 commits are already done before the tags.
If you are on my latest kernel, you are updated to the best hiding you can get so just wait!
if this doesnt make sense im sorry, tag me and i can maybe explain better!
Thanks everyone!
If you like my work and would like to support me!
Donations:
https://t.me/WildKernels/90170/90171
Privacy + Secure Tech Corner Channel 🛡️
I've had issues with restore my backup data, no 4g+ only for data EDGE and GSM for calling 🤪 I've tested some what I reader, but not helped me 🤷♂️ That's was the goal Reset mobile network settings and Reset Bluetooth & Wi-Fi That helped me, thx Android…
YouTube
How to Fix Calling Issues in any GSI ROM [4G/5G/LTE/NR/VoLTE/VoNR]
Guide: https://droidwin.com/how-to-fix-calling-issues-in-gsi-rom/
In this video, we will show you the steps to fix calling issues in any GSI ROM.
In this video, we will show you the steps to fix calling issues in any GSI ROM.
### 1. What is verifiedBootKey
* This is the public key used to sign the boot image (boot/recovery/system, etc.).
* It is stored in the firmware and acts as the root of trust when verifying system integrity.
* The device manufacturer “burns” it into the Trusted Execution Environment (TEE) or processor fuses (eFuse/OTP).
* If the key doesn’t match the expected one, the system considers the boot process unsafe.
In simple terms:
verifiedBootKey = who signed the firmware (root of trust).
---
### 2. What is verifiedBootHash (or boothash)
* This is a hash (SHA256, etc.) of the boot partition contents (or a set of partitions, depending on AVB).
* It is calculated at boot time and compared with the reference value from the manifest.
* If the hash is different → the partition has been modified (e.g., custom kernel or ramdisk).
In simple terms:
verifiedBootHash = what exactly was loaded (the actual boot state).
---
### 3. Connection and difference
* BootKey determines whether we trust *the signer of the firmware*.
* BootHash determines whether *the boot partition itself has been modified*.
Analogy:
* Key (verifiedBootKey) = the manufacturer’s official stamp.
* Hash (verifiedBootHash) = the fingerprint of the specific paper that has the stamp.
---
### 4. In the context of Key Attestation
In Android Key Attestation the TEE signs a report that contains:
*
*
* Together they allow external services to verify that the device is booting in a trusted and unmodified environment.
* This is the public key used to sign the boot image (boot/recovery/system, etc.).
* It is stored in the firmware and acts as the root of trust when verifying system integrity.
* The device manufacturer “burns” it into the Trusted Execution Environment (TEE) or processor fuses (eFuse/OTP).
* If the key doesn’t match the expected one, the system considers the boot process unsafe.
In simple terms:
verifiedBootKey = who signed the firmware (root of trust).
---
### 2. What is verifiedBootHash (or boothash)
* This is a hash (SHA256, etc.) of the boot partition contents (or a set of partitions, depending on AVB).
* It is calculated at boot time and compared with the reference value from the manifest.
* If the hash is different → the partition has been modified (e.g., custom kernel or ramdisk).
In simple terms:
verifiedBootHash = what exactly was loaded (the actual boot state).
---
### 3. Connection and difference
* BootKey determines whether we trust *the signer of the firmware*.
* BootHash determines whether *the boot partition itself has been modified*.
Analogy:
* Key (verifiedBootKey) = the manufacturer’s official stamp.
* Hash (verifiedBootHash) = the fingerprint of the specific paper that has the stamp.
---
### 4. In the context of Key Attestation
In Android Key Attestation the TEE signs a report that contains:
*
verifiedBootKey — shows which key the device trusts.*
verifiedBootHash — shows what was actually loaded.* Together they allow external services to verify that the device is booting in a trusted and unmodified environment.
Forwarded from GSMArena (IFTTT)
DJI’s new sub-250g drone brings a massive upgrade – the DJI Mini 5 Pro has a 1” sensor
https://ift.tt/ZWciFlq
https://ift.tt/ZWciFlq
GSMArena.com
DJI’s new sub-250g drone brings a massive upgrade – the DJI Mini 5 Pro has a 1” sensor
The new model has forward-facing LiDAR and a rotating camera gimbal. It can fly faster and further than the Mini 4 Pro too.
Forwarded from Above Phone Announcements
🔥 Above Phone's 24-hour Fall Flash Sale is LIVE!
Dive into the best deal ever on the Pixel 6a and experience premium technology at an unbeatable price. Whether it’s for personal use, business, or a gift, this is your moment to shine! ✨
What You'll Love:
* Record low pricing on the Above Phone Pixel 6a
* Easy, flexible payment options
* Free support call to ensure seamless setup
📱 But hurry—supplies are limited, and this deal is only here for 24 hours! Shop now and secure your spot in the Above Phone family. It's time to experience freedom like never before.
👉 https://above.sh/ZDwKng
Dive into the best deal ever on the Pixel 6a and experience premium technology at an unbeatable price. Whether it’s for personal use, business, or a gift, this is your moment to shine! ✨
What You'll Love:
* Record low pricing on the Above Phone Pixel 6a
* Easy, flexible payment options
* Free support call to ensure seamless setup
📱 But hurry—supplies are limited, and this deal is only here for 24 hours! Shop now and secure your spot in the Above Phone family. It's time to experience freedom like never before.
👉 https://above.sh/ZDwKng
Above Phone
Above | Privacy phones, laptops, and tablets
Above provides privacy-first phones, laptops, and tablets designed to protect your data and secure your digital freedoms.
Forwarded from XiaomiTime: Xiaomi & HyperOS News (IFTTT)
"Xiaomi is set to launch the Redmi Pad 2 Pro!- Qualcomm 7s Gen 4 processor- 12.1-inch display with 120Hz refresh rate- 6GB RAM, 128GB storage- 12,000 mAh battery with 33W fast charging- Graphite Gray color- Includes 3.5mm headphone jackStay tuned!"
🔗 Check More
🔗 Check More
XiaomiTime
REDMI Pad 2 Pro Leaked: Xiaomi’s Got Something Cooking - XiaomiTime
Xiaomi appears ready to reinforce its position in the tablet market with the imminent release of the Redmi Pad 2 Pro. Recent leaks have shared official
Forwarded from XIAOMI Fuckups
Xiaomi CEO Lei Jun redefines the meaning of 'copying' as 'benchmarking'
Xiaomi CEO Lei Jun claims that Xiaomi 17 series is created to benchmark iPhones.
Q. So how does one benchmark iPhone according to Lei Jun?
Ans. You just make a copy of iPhone
That's why the Xiaomi 17 series has:
1:1 naming scheme
1:1 wallpaper (15S Pro),
1:1 icons
1:1 browser & photos UI
1:1 menu sheet
1:1 control center/ QS tiles
1:1 dynamic island (poorly implemented)
Follow @XiaomiFuckups for more Lei Jun advice
Xiaomi CEO Lei Jun claims that Xiaomi 17 series is created to benchmark iPhones.
Q. So how does one benchmark iPhone according to Lei Jun?
Ans. You just make a copy of iPhone
That's why the Xiaomi 17 series has:
1:1 naming scheme
1:1 wallpaper (15S Pro),
1:1 icons
1:1 browser & photos UI
1:1 menu sheet
1:1 control center/ QS tiles
1:1 dynamic island (poorly implemented)
Follow @XiaomiFuckups for more Lei Jun advice
Forwarded from Hacker News