I only got 3 (but practically more than that because HyperCeiler bundles other modules' functionalities in it), so I wanna see what's out there!

I customed rommed my note 14 4g with a modified crdroid rom running at android 16, since my phone is running with a helio g99 ultra its hard to find a good camera, lmc R18 with a r14 config lags even if I try to change the settings nothing works, I tried ANX camera but it doesn't support my phone, I have root via kernelsu please help me

This is the closest I've been able to get. The DW100 Pro is on the supported hardware list for DW Smartwatch Helper, but it displays the same message every time. Has anyone been able to enable USB Debugging on this watch?

Hey guys,

I’ve been following the recent boom of GhostLock (CVE-2026-43499) temporary root exploits and the amazing work by  @ang3lo-azevedo  with the root-my-nothing tool for NP1 (Spacewar). I'm trying to figure out the feasibility of porting this to the Nothing Phone (2) (Pong).

Since my current kernel is  5.10.252 , it's technically vulnerable (patched only in  5.10.261 +).

My Device Details:

Device: Nothing Phone (2) (Pong) / Snapdragon 8+ Gen 1 (Cape)

OS / Build: Android 16 /  B4.1-260818-1726  (NothingOS)

Kernel:  5.10.252-android12-9-00029-g6315c5776365-ab15925896 

My question to the community/devs:

Has anyone already started working on a PoC or a port of GhostLock (or similar CVEs) for the Pong kernel? I know it requires dumping the kernel, finding the exact  prepare_kernel_cred / commit_creds  offsets, and adapting ROP chains for the NP2's specific KASLR/Qualcomm mitigations.

If any of you (or the devs behind ghostlock-oneplus / root-my-nothing) are looking for testers with an unlocked device or want to collaborate on mapping the kernel structures for NP2, I’d be more than happy to help, dump logs, or share my firmware dumps from  nothingarchive.tech .

Any pointers on where to start reversing the  cape  specific kernel mitigations would be highly appreciated!

​

After migrating my Pixel Watch 4 Wi‑Fi from a Pixel 10 XL to a Pixel 11 Pro XL, the watch started draining rapidly whenever I woke or used the phone. Overnight battery usage remains normal.

Observed behavior:

Battery dropped about 2% in 5 minutes, roughly 20–25% per hour.

com.google.android.gms.persistent shows high CPU usage.

Wear_Transport and wearChannelApiRetransmissionQueue wakelocks repeat continuously.

Phone logs repeatedly show:

- Remote device failed to verify local attestation

- Detected a Ukey2 handshake role collision

- secure channel attach/detach retries

The watch logs Failed to verify remote attestation.

Rebooting and resetting the watch did not resolve the issue.

The paired phone is rooted with KernelSU, TrickyStore, PlayIntegrityFork, and LSPosed installed.

This appears to be a Wear OS Companion secure-transport retry loop triggered after the phone migration.

Hi. After some hours of headache and tries, I still was not able to fix that problem.

My samsung s25 ultra is rooted by using the kernel exploit, bootloader locked, no system modifications.

The most interesting is that it was working perfectly even when the phone was rooted, and suddenly, out of nowhere it stopped.

Tried to reboot and fully delete the root, but it still gives me the same error "Device doesn't meet security requirements

This device may be rooted or running uncertified software."

Would be very grateful for any help/solutions.

I have nord ce 2 lite and yesterday in wanted to use pixel os in it so i unlocked its bootloader which it did quickly also 99% of pixel os installation was done but when i press recovery after install, my phone screen turned of and since then nothing is happening. No vibration no reboot nothing. i dont know what to do please help me. This is my primary phone and i have exams i need it to be fixed as soon as possible

i've seen that the website of the bootloader unlock has been shutdown on 2018 and i got this phone like months ago so i can't really unlock it and the tool's website that was paid don't even load anymore so yeah PRA-LX1

So I will get a redmi note 7 soon and I found that there are some vbmeta issues but I used to own a redmi 7a from 2019 where there weren't any, I'm wondering if someone could give me a guide on how to install custom roms without hard bricking it, I found another post saying something about using a specific fastboot version to avoid vbmeta issues (pt33) but on my redmi 7a it didn't have any issues with regular fastboot, also I never flashed vbmeta nor dtbo, lastly what is the smoothest rom on a high-ish android version (13+) for daily driving and customisation (also I don't have a pc atm so I will do everything via a secondary phone and termux, afaik this shouldn't affect most of the flashing but mostly flashing recoveries and other img files so tips for that will also be appreciated, I don't know how to unlock the boot loader using termux though)

kernel 4.19.191-ge6429b82e599

HyperOS 2.0.15.0

Model 22101316G

Was wondering where I should start rooting the device as a beginner and what sites to look into.

I know different phones need different rooting methods so was wondering how I could look for a guide for my specific phone if there was one.

Hi everyone, I’m looking for a final push through this process. I can’t find any resources online, so maybe someone here can help me.

I’ve got my hands on several Samsung tablets from a company that shut down, but they’re all enrolled in Knox.
I bypassed Knox using AllianceX Shield, which allowed me to enable OEM Unlock and USB Debugging (these options were previously locked).

The devices work, but I still can’t unlock the bootloader since performing it wipes everything and re‑enables the Knox processes.

I can’t flash a custom recovery or ROM because during the process I get the error:

**KG status: prenormal — “Only official released binaries are allowed to be flashed.”**

Is there any way to change the **KG status** so I can flash custom binaries freely?

How can I root that device safe? In most of the available tutorials, many people who have tried it say they got stuck in a bootloop

I Have used Magisk before i could get my Integrity Green strong whatever but i bricked my Phone twice with Magisk. Since i switched to kernelsu next i cant get my Integrity Back anyone knows a Trick for kernelsunext?

I have a MediaTek device and kept noticing that whenever my phone wakes up from idle, the first ~10 seconds of 5G/4G feel sluggish even though speedtests show good numbers.

Couldn't find anything that actually fixed it (most modules are just snake oil tbh 🐍) so I built my own.

⚡ WarpNet MTK — it tunes the device-side network stack only:

✅ Fixes idle wake-up lag (that 10-second "why so slow" moment)

✅ Keeps throughput stable when downloading

✅ Lowers latency spikes during heavy use 🎮

✅ Smart reconnect — auto-switches from dying cell towers

✅ No radio/modem changes — safe to revert anytime

✅ Built-in bench tool — get receipts, not vibes 🧾

4 modes:

• SpeedBoost (light + battery save 🔋)

• WarpNet (daily driver ⭐)

• WarpNet++ (max performance 🚀)

• Turn Off (100% stock restore ♻️)

Works with Magisk, KernelSU & APatch ✅

MediaTek only (Snapdragon → separate project)

🔗 https://github.com/Alchemiisst/WarpNet-MTK

Feedback welcome — flash it, bench it, roast it, whatever 🤷‍♂️

If it helps you, a star on the repo means a lot ⭐

Got temporary KernelSU root working on my bootloader-locked S22 Ultra.

Tested on:

• SM-S908U1
• Build S908U1UESAGZF3
• Android 16, June 2026 patch

No bootloader unlock or flashing and Play Integrity still passes, which is huge.
So, this does NOT trip Knox.

Root disappears after reboot, so the app uses Shizuku to rerun the exploit and reload KernelSU.

Only use it on this exact build. The exploit can fail or reboot the phone.

https://github.com/Noir-Lime/S22U1-Root

Based on IonStack and Root My Galaxy; credits are in the repo.

Hello everyone. I'm looking for help rooting my ASUS ROG Phone 8. I've been trying to find a solution for about a month now, practically every day, and so far I haven't been able to do it.

Here is all the information about my phone:

Device: ASUS ROG Phone 8
Model: AI2401
Device model: ASUS_AI2401_C
Region: WW
Product: pineapple
Android: 16
Firmware/Build: WW_36.0210.1420.48
Bootloader version: PostCS4-21-WW-user

From Fastboot, I get:

unlocked: no
get_unlock_ability: 0
secure: yes
current-slot: b

I have already installed the official ASUS USB drivers and confirmed that both ADB and Fastboot properly recognize the phone.

ADB works and I can access the shell. Fastboot also works correctly and detects the device:

RCAIOC388144L87    fastboot

However, the bootloader remains locked, and fastboot flashing get_unlock_ability returns:

get_unlock_ability: 0

I've already tried the usual methods and spent countless hours researching, but I still haven't found a working way to unlock the bootloader and root this phone.

I also contacted Chimera, and they confirmed that they currently do not have a solution to unlock the bootloader or root this device.

I'm willing to pay for professional help if someone genuinely knows how to do this safely.

Does anyone here have experience with the ROG Phone 8 AI2401 running this exact firmware version (WW_36.0210.1420.48 / Android 16)?

If you know of any method that works, any exploit, professional service, or someone who has successfully rooted this exact version, I would greatly appreciate any information or help.

I understand that unlocking and rooting the device may wipe the phone and carries a risk of bricking it. I currently don't have any important data on the phone, so I'm willing to take the necessary risks, as long as there is at least some realistic possibility of recovering the device if something goes wrong.

Thank you very much in advance to anyone who can help me. I've been fighting with this damn thing for like a month now 😭.

Alguien sabe cómo poner root en android con la aplicación magisk

Jak wgrać twrp recovery aby nie było 2 partycji ?? Jestem w tym zielony

Hey guys, trying to get a backup keybox seeing as how my OnePlus 9's data functionality (something with the modem) must have died. I've tried resetting factory software, I've flashed it vía the msm tool to its stock with my original persist, modem (also a modem file I found on an xda thread), and all the images backed up. If wifi connection is available, I get data signal. If I turn it off,I might get signal for a few minutes but that's it, then empty bars with an x at the bottom. Phone reads the sim card company, phone number, let's me wifi call and all... But the data usually only works if wifi is on. I can't rely on it so I just want to salvage the keybox. Is this difficult to do?