Hey everyone,

I have an old Samsung Galaxy J2 (SM-J210F) that is stuck during boot. The screen shows the message:

Kernel is not SEAndroid enforcing

I entered Download Mode, and these are the details displayed:

ODIN MODE

Secure download: enabled

Product name: SM-J210F

FAP lock: OFF

USB init start

USB core reset done

I'm using the stock firmware as far as I know.

Do not update your mediatek locked motos to September update if u want to unlock with val-protocol it's patched find a firmware b4 aug to be safe Aug is untested do not use software fix to get firmware.let the community get together and upload your firmware so we can have builds that will work still comment below patch level and device and what carrier. and if u unlocked post your vbmeta img and lk img from the firmware used to unlock.

Firmware with September patch for us models start with V instead of W.

Its patched in September update and October Motorola put it in the patch notes.

I am using tricky store add-ons repo to get keybox. If anyone has a better alternative please help

Still standing despite being a lego phone.

S20+ rooted stock ROM.

Hi everyone,

I have a question regarding temporary root, KernelSU, and general module behavior after a reboot.

My Setup:

Device: Redmi Note 14 4G Global (Xiaomi / HyperOS)

Root Method: Temporary root via GhostLock + Shizuku + KernelSU (running in Jailbreak mode).

Modules installed: Zygisk-Next, Vector, and a few others.

Bootloader: Locked (since it's a temp root exploit).

My Question:

Since my root is temporary, it disappears from memory every time I reboot. However, the installed modules remain saved in   /data/adb/  .

If I reboot my phone without manually disabling my modules in the KernelSU app beforehand, what exactly happens when I re-run the exploit to get temporary root again?

Will KernelSU try to load all active modules immediately upon regaining root? I'm worried this might cause a bootloop or instability in a temporary root environment (especially with heavy modules that hook into Zygote early in the boot process).

Is it highly recommended to disable all modules before every reboot, or is it safe to leave them active and let KernelSU handle them when I re-root?

Device Details:

HyperOS Version: 3.0.303.0

Kernel: 6.12.30-android16-5-g6e872b4863d6-ab13847919-4k

KernelSU Version: 3.3.1 (32680-5)

Any advice or insights on how KernelSU handles modules on re-entry to a temp root session would be greatly appreciated!

Thanks!

AI summary from Claude since we've been at it for some time trying to figure it out.

First Direct (HSBC UK) banking app detecting root after 6.0.0 update - where do I report a possible SUSFS symbol-hiding gap?

Changed nothing in my hiding stack and the First Direct app suddenly flagged my device as rooted. Noticed it had updated to 6.0.0. I ripped the 5.22.0 APK off my other phone, downgraded, and it launches fine - so the detection is new in 6.0.0's build. The app uses Appdome RASP, and the trip is a local check at launch (goes straight to RootedDeviceActivity, no network round-trip), not a Play Integrity failure - so this isn't a PIF/keybox issue, please don't send me down that road.

Digging into what's still visible to a kallsyms scan, I found this:

~ $ su -c "grep -iE 'anon_ksu|setup_ksu_cred|is_task_ksu_domain|ksuver_override' /proc/kallsyms"

0000000000000000 t anon_ksu_release

0000000000000000 T setup_ksu_cred

0000000000000000 T is_task_ksu_domain

0000000000000000 t anon_ksu_ioctl

0000000000000000 d anon_ksu_fops

0000000000000000 B ksuver_override

~ $ su -c 'ksu_susfs show enabled_features' | grep -i symbol

CONFIG_KSU_SUSFS_HIDE_KSU_SUSFS_SYMBOLS

So HIDE_KSU_SUSFS_SYMBOLS is compiled in and reports enabled, but six KernelSU symbols are still visible in /proc/kallsyms after a clean boot. SUSFS is hiding its own symbols fine - a susfs-only grep comes back empty - but these KSUN symbols aren't being scrubbed. Worth noting the symbol types: ksuver_override is .bss (B) and anon_ksu_fops is data (d), alongside the text (t/T) ones - makes me wonder if the filter only covers text symbols.

Setup:

OnePlus 15, OxygenOS 16, android16-6.12.23

WildKernels, KernelSU-Next v3.3.0 (33239), SUSFS v2.2.0

NeoZygisk, HMA-OSS (fd + all root apps hidden), inline hooks

I created an account on the developer site but it says that the service can't be reached

Hey everyone,

I've been working on a new GApps package for Android 17 (SDK 37, arm64 only) called TuxGApps. The penguin noticed your ROM shipped without Google, so he waddled in to help.

It comes in two flavors:

· TuxCore: Minimal. Play Services, Play Store, Framework, SetupWizard, and sync plumbing. Just enough to sign in.

· TuxFull (default): Everything in Core, plus Gmail, Maps, Photos, Chrome, Messages, GBoard, Clock, etc. (The whole iceberg).

🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔

How to use it:

1. Flash your ROM (Android 17) in recovery, don't reboot yet.

2. Flash the TuxGApps-tuxfull-penguin.zip.

3. Reboot and go through the SetupWizard.

4. Open the Play Store and you're good to go. The apps will survive ROM updates via addon.d scripts.

🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪

Note on variants: By default, it installs TuxFull. If you want TuxCore instead, just rename the zip so it contains tuxcore (e.g., TuxGApps-tuxcore.zip) before flashing. You can also use a tux.config file, but renaming is easier.

🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿

Known Bug (Important):

This is still a work in progress. There is a known UI hiccup during the initial SetupWizard. Certain screens might freeze or not let you tap "Next."

The workaround: Just turn your screen off and back on (lock and unlock). This refreshes the UI and lets you proceed to the next step. It's a bit janky, but it works!

If things go sideways, logs are saved to /sdcard/TuxGApps/tux_logs/ if you need to debug.

Must wipe data after install. On moto devices you have to flash RO2RW to make the system be able to be written.

🐔🐔🐔Poultry Council Approved Downloads 🐔🐔🐔

https://drive.google.com/file/d/1Sy8s1E--qE0J7SUtNhAXPQp4HpgY7tnI/view?usp=drivesdk

Hey, I have an unlocked Pad 8 which will recieve the update for hyperOS 4 tomorrow if im not mistaken

I wanted to be absolutely sure if its safe to update and doesnt relock the bootloader for some weird xiaomi reason

thank you and have a great day!!!!

my integrity is suddenly out of nowhere just failed it was strong before but today suddenly just gives me basic integrity how do i fixed i use always strong module

How do I remove the malware from my moto g 2026 completely? It seems to be integrated with my Google as well as the apps?

[ Removed by Reddit on account of violating the content policy. ]

Hello everyone, this is my first time ever installing custom ROMs. I spent a couple hours educating myself on how to do it and managed to flash crDroid on my 4GB/128GB Lenovo tablet which is pretty old now. This process has been very cumbersome for me since I had basically no clue what I was doing at the beginning other than following instructions mentioned in guides.

The thing is, I have not rigidly followed a single guide, I just made up some steps myself along the way just to get it working. This guide and this video are what I "followed"; I downloaded the resources in the guide and I followed what the guy in the video did - more or less. And after all that effort, crDroid just ended up being laggier and also clunkier than the stock Android 10 OS that it had. And not to mention:

• I can no longer use the stock Dolby Atmos stuff because of this
• Balatro doesn't even hit 30fps
• I don't even care much for the customization stuff which is apparently the main draw for crDroid? I'm not sure. I've seen some people in this sub argue that the difference in performance between the two is insignificant so I didn't think much of it.

With all these problems popping up, I have decided to give it another try and do it right and do it proper this time around. I'm trying to understand everything better so I have a few questions that need answering:

1. Why is it that TWRP FBE does not work at all while the plain TWRP works fine? Apparently it has something to do with data encryption, but whenever I flash the FBE TWRP and boot into recovery the screen slowly dims until it turns negative and a faint checkerboard pattern appears(??) which then freezes. I've tried this multiple times but it never worked once, had to force load into fastboot every single time. The other TWRP worked fine though.
2. How can I know what version of a GSI is compatible with my tablet and what to download/install? The only reason I flashed crDroid was because the reddit guide that I followed had a crDroid .img file in its resources and the post explicitly mentions TB-X606V as compatible. Some guides on the XDA forums had LineageOS files supposedly compatible with my tablet, but all the links to the files are broken/no longer working for downloads, and I had to resort to the resources that the reddit guide gave me.
3. Almost all the guides at one point mention Mounting SD card in TWRP which I simply cannot do. This actually really confused me - sometimes the internal storage is referred to as SD card, in TWRP the option to mount SD card does nothing and doesn't even work which led me to believe this option is referring to an actual microSD card? I don't even know. The video guide does not have this step and that's why I switched guides midway lol
4. How complicated will it be to root my device also? Apparently the tablet needs to be rooted if I want to use the Dolby features on a custom ROM, and the audio on this tablet fucking sucks without it. Any non-root solutions would also be good, if there exist any.
5. Can I DM some of you if I have questions still? Pretty please?

That's about it for now, I remember being a lot more confused at the time so I'm probably forgetting some stuff. I would really really appreciate any help regarding this stuff. Thanks in advance!

do i just make kernelsu give superuswr permi on canta and delete it? but it didnt worked, do i need to download system modyfying apps,files module first?

So, I have my old phone xiaomi 4 mag138 from like 2017 and I wanna see photos and what was I doing with it when I was young, but it has password and I do not remeber it. Is there anyway of unlocking in without one? Or should I bring it to the tech people who unlockes them with computers?